From: Daniel Exner <dex@dragonslave.de>
To: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Panic on 2.6.23-rc5 (solved)
Date: Wed, 12 Sep 2007 09:17:12 +0200 [thread overview]
Message-ID: <200709120917.12815.dex@dragonslave.de> (raw)
In-Reply-To: <6bffcb0e0709061206n4146da2anf11f15218e8e0091@mail.gmail.com>
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
prev parent reply other threads:[~2007-09-12 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 18:44 Kernel Panic on 2.6.23-rc5 Daniel Exner
2007-09-06 19:06 ` Michal Piotrowski
2007-09-06 22:14 ` Daniel Exner
2007-09-12 7:17 ` Daniel Exner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200709120917.12815.dex@dragonslave.de \
--to=dex@dragonslave.de \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=webmaster@dragonslave.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.