[Bug 839301] New: Crash updating udev
https://bugzilla.novell.com/show_bug.cgi?id=839301 https://bugzilla.novell.com/show_bug.cgi?id=839301#c0 Summary: Crash updating udev Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: volker3204@paradise.net.nz QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) konqueror/4.10.5 Safari/534.34 With today's updates there is a new udev package. Installing with yast online_update over ssh. kdebase4-runtime-4.10.5-1.104.5.x86_64 is installed first, libudev is attempted next, but yast hangs. ps aux and pstree hang too, it's not possible to find out which process hangs because all process listing deadlock. ls -l /proc/* does too. There is a kernel crash on the screen, see attached photo. Rebooting hangs, sysrq-s -u -b are required. On reboot, system hangs just after grub when loading mkinitrd. Power-cycling required, dead inodes removed, system boots fine. Reproducible: Didn't try Steps to Reproduce: 1. Current oS 12.1 as of last week. 2. Run yast online update. 3. Actual Results: Kernel crash. Selecting major severity because of kernel crash. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=839301 https://bugzilla.novell.com/show_bug.cgi?id=839301#c1 --- Comment #1 from Volker Kuhlmann <volker3204@paradise.net.nz> 2013-09-10 16:10:39 NZST --- Created an attachment (id=556548) --> (http://bugzilla.novell.com/attachment.cgi?id=556548) Kernel crash screen photo. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=839301 https://bugzilla.novell.com/show_bug.cgi?id=839301#c Alberto Planas Dominguez <aplanas@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| | SILVER -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=839301 https://bugzilla.novell.com/show_bug.cgi?id=839301#c Jeff Mahoney <jeffm@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |mgorman@suse.com |ovo.novell.com | Severity|Major |Critical -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=839301 https://bugzilla.novell.com/show_bug.cgi?id=839301#c2 --- Comment #2 from Mel Gorman <mgorman@suse.com> 2013-09-30 09:31:06 UTC --- The area this bug occurred in is very heavily executed and bugs in the area tend to hit almost immediately and universally. The only time I've seen a big resembling this in the last 2-3 years was due to hardware failure in a blade system and it was intermittent. Moving the blade to a different chassis magically fixed it. Can the memory, CPU and motherboard of this system be tested please? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=839301 https://bugzilla.novell.com/show_bug.cgi?id=839301#c3 Volker Kuhlmann <volker3204@paradise.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |volker3204@paradise.net.nz --- Comment #3 from Volker Kuhlmann <volker3204@paradise.net.nz> 2013-10-01 11:20:15 NZDT --- I had already run memtest86 through once, and it passed, but of course that's no total proof. I am not silly enough to start overclocking. What are the hardware test program(s) you would like me to run? I've been wanting a program that reliably tells me which hardware part is munted for a long time and I'd be very grateful if you shared your program names. TIA -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=839301 https://bugzilla.novell.com/show_bug.cgi?id=839301#c4 Volker Kuhlmann <volker3204@paradise.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mgorman@suse.com --- Comment #4 from Volker Kuhlmann <volker3204@paradise.net.nz> 2013-10-25 13:02:19 NZDT --- I am more than happy to run hardware test programs for CPU, mobo, etc. but can you please give me their names? Thanks! -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=839301 https://bugzilla.novell.com/show_bug.cgi?id=839301#c5 --- Comment #5 from Mel Gorman <mgorman@suse.com> 2013-10-26 09:01:01 UTC --- (In reply to comment #4)
I am more than happy to run hardware test programs for CPU, mobo, etc. but can you please give me their names? Thanks!
Sorry, I do not have a specific recommendation. In most cases I've been in the position where I was able to test with a workload that reproduced a particular problem and then switch out components until the faulty one was identified. In other cases the motherboard diagnostics were able to identify the faulty component. When deploying servers I usually load test the machine for a few days to see if anything unexpected shows up -- fstest or tiobench with increasing numbers of clients for IO, NAS with openmpi for testing CPU and memory, ping-pong benchmarks like pipetest and hackbench again for CPU, artificially generating whatever the target workload is etc. Google shows up a number of possibilities of stress testing components but I have never had need to check them out myself. -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=839301 Mel Gorman <mgorman@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |NORESPONSE --- Comment #6 from Mel Gorman <mgorman@suse.com> --- Closing. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com