https://bugzilla.novell.com/show_bug.cgi?id=349170 Summary: system hardlocks related to yast Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: amr.el.sharnoby@gmail.com QAContact: jsrain@novell.com CC: amr.el.sharnoby@gmail.com Found By: --- Hello, This is the 1nd time I submit this bug as I didn't find the one Ive reported few hours ago .. I've a strange problem on my openSuSE 10.3 x86_64 system ... which I couldn't find any clear reason of it or a proof that it's related to some specific thing .. My Hardware: CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ MB: K9N Ultra RAM: 1 GB Kingstone 800 x 2 Graphic Crad: Nvidia 6200 TurboCache Harddisk: Seagate 250GB ST3250820AS Summary: Since my I've moved to openSuSE 10.3 x86_64, I'm using suse since 9.1, with a fresh system installation my OS get frozen every now and then ... Symptoms: 1- when it freezes it doesn't respond to any thing, the Num Lock cannot be turned on and off .. it doesn't respond to acpi shutdown ... and I cannot ping the IP either using ping or arping ... 2- It doesn't even show a kernel panic message 3- Although I a give the kernel panic=10 parameter at boot time and I can see that "cat /proc/sys/kernel/panic" gives 10 , it does never restart like it would in a normal kernel panic ... 4- It's not related to high CPU or memory usage and not related to how long the system has been up .. it can occur after very few minutes to few days ... 5- This problem never happened on opensuse 10.2 x86_64 and also never occur with my secondary CentOS 5 x86_64 system ... Investigations I've made and other notes: 1-This problem occurs with all kernel-default versions since the 1st version that came with system out of the box and until the current version 2.6.22.13-0.3-default passing by all updated in between ... 2-I doubted that it maybe due to a buggy proprietary kernel module .. so I've uninstalled the nvidia commercial module and used the opensource one but the problem continued to happen ... 3- I thought it might be due to swap partition for somehow so I've disbaled the swap completely but it continue to happen .. 4- I doubted that it maybe due to compiz fusion or xgl so I've disabled them but continued to happen ... 5- I doubted that it can be related to CPU temperature, memory problem or harddisk problem ... so I've ran stress testing for all of those, causing the CPU temperature to reach 54 C degree for around 12 hours with very heavy memory test with high read and write I/O load using stress software but everything wnet fine ... I've even tested the memory using memtest for some hours but it didn't show any problem ... I've ran a smartctl long test on the harddisk many times and it didn't show any problem ... 6- I doubted that it can be a graphic card problem so I've changed the graphic card with another one, nvidia 6600 LE, which I know for sure that it's working so fine for about two years but the problem continue to occur ... I've tested even my original card on another PC with 3D benchmarking for some hours and it didn't show any problem .. 7- The only thing I could notice is that it's related to yast ... I can remember very well that yast was running when all those crashes occurred and when I noted that I tried to wait for some days to make sure and I'm now sure .. The problem isn't related to any specific yast module, not every related to the GUI version of yast as it occurred once when I ran sax2 on the console on runlevel 3 ... it can be related to yast checking some kernel modules or making some hardware investigations like sax2 checking modules when changing configuration or opening the hardware information module but not always, as it can occur with simple software installation too and none of these is reproducible ... once I've just booted the system then directly switched it to runlevel 3 and ran sax2 to change some configuration then the system crashed, on the next reboot I've done the same but no problem occurred ... 8- I've disabled apparmor as I didn't really made use of it but the problem continue to occur .. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.