http://bugzilla.novell.com/show_bug.cgi?id=590468 http://bugzilla.novell.com/show_bug.cgi?id=590468#c2 Jon Schewe changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jpschewe@mtu.net | --- Comment #2 from Jon Schewe 2010-03-23 17:54:34 UTC --- It's empty and it's old. My guess is that the system didn't boot far enough to be able to write out a log. jpschewe@jon:/var/log

ls -l mc* -rw-r--r-- 1 root root 0 2009-11-22 08:30 mcelog

-- Configure bugmail: http://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=590468 http://bugzilla.novell.com/show_bug.cgi?id=590468#c4 Jon Schewe changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jpschewe@mtu.net | --- Comment #4 from Jon Schewe 2010-03-23 18:00:19 UTC --- Yes, that's what this bug is for and why it's marked critical. The system does not boot with the 2.6.31.12.0.2 kernel. -- Configure bugmail: http://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=590468 http://bugzilla.novell.com/show_bug.cgi?id=590468#c6 --- Comment #6 from Jon Schewe 2010-03-27 14:10:37 UTC --- With a reboot this morning it locked up with the same mce using kernel 2.6.31.12-0.1.1, which had been booting fine. I've had problems with the nvidia driver for sata causing bus resets, is it possible the mce is from something in the filesystem getting corrupted from the bus resets? I ran "rpm --verify" on my installed kernel packages and got back no differences. Summary of what does and does not work: knoppix - boots fine suse 11.1 64-bit rescue disc - boots fine 2.6.31.12-0.1.1 - boots 80% of the time (although that percentage is going down) 2.6.31.12-0.2.1 - never boots -- Configure bugmail: http://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=590468 http://bugzilla.novell.com/show_bug.cgi?id=590468#c8 --- Comment #8 from Jeff Mahoney 2010-03-27 15:15:32 UTC --- You probably just have bad memory. I'm don't know why the previous kernel worked and this one didn't or why the Knoppix kernel works. It could just be that they've allocated memory differently. The MCE message tells you that bank 4 is bad. If you have removable memory modules in your notebook, this boot failure will be a pretty reliable way to tell you when you've found the right one. You can disable the MCE checker by booting with mce=off, but I wouldn't recommend it. It's catching hardware problems that would otherwise manifest themselves as random crashes or corrupted memory. -- Configure bugmail: http://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=590468 http://bugzilla.novell.com/show_bug.cgi?id=590468#c10 --- Comment #10 from Jon Schewe 2010-03-27 21:39:33 UTC --- Hmm, if it's memory, then removing the memory in bank 4 should remove the exception, right? I just removed said memory and I still get the exception. -- Configure bugmail: http://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=590468 http://bugzilla.novell.com/show_bug.cgi?id=590468#c12 --- Comment #12 from Jon Schewe 2010-03-28 03:59:56 UTC --- Rebooted and I'm back to the MCE again. No other changes. -- Configure bugmail: http://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=590468 http://bugzilla.novell.com/show_bug.cgi?id=590468#c14 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Status|NEW |NEEDINFO CC| |rjw@novell.com InfoProvider| |jpschewe@mtu.net --- Comment #14 from Jeff Mahoney 2010-04-02 15:04:36 UTC --- Can you boot the old image and then start initiating activity on the disk that isn't working correctly? I'm not convinced this isn't bad hardware yet, but the MCE log seems to be pointing in the wrong direction. -- Configure bugmail: http://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=590468 http://bugzilla.novell.com/show_bug.cgi?id=590468#c16 Jon Schewe changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |FIXED --- Comment #16 from Jon Schewe 2010-04-18 20:59:10 UTC --- I got the latest kernel update (2.6.31.12-0.2) and booted it without error. Changes I made: 1) switched to a Promise SATA 150 TX4 card for my drives and disabled the onboard nvidia SATA controller. After this I hadn't see a drive error in over a week. 2) I fscked all filesystems now that the SATA drives weren't getting reset so often. I found that /boot had a corrupted filesystem. I corrected all errors and reinstalled grub and the old kernel. After this things started booting better. 3) I just installed the latest kernel update and the system booted ok. As a fallback, between each change I would sync up my mirror and then boot with only 1 drive. That way if something failed I could quickly go back. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.