Messages in this thread | | | From | Daniel Exner <> | Subject | Re: Kernel Panic on 2.6.23-rc5 (solved) | Date | Wed, 12 Sep 2007 09:17:12 +0200 |
| |
Hi!
Michal Piotrowski: > On 06/09/07, Daniel Exner <dex@dragonslave.de> wrote: > > I'm not really sure if this is a regression or if I simply hit a hardware > > problem. > > After some time of work (mostly hours sometimes minutes) my system will > > freeze including Blinking LED's and unresponsiveness on SysRQ, but I > > finally got this using netconsole: > > > > CPU 0: Machine Check Exception: 0000000000000004 > > Bank 4: b200000000070f0f > > Kernel panic - not syncing: CPU context corrupt > It is a hardware problem. You where right. I switched the power suply (first guess of hardware guy ;) The Box is now up 2 days 9hrs and no kp so far :)
I really should use sensord to show undervoltages in syslog..
> You may want to use mcelog ftp://ftp.x86-64.org/pub/linux/tools/mcelog/ This is a nice tool, but why is it only available for x86_64 ? The MCE reporting facility is in place in x86, too.
Anyway I only send this mail to say: Not Kernel's fault.
-- Greetings Daniel Exner - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |