Skip to contentSkip to conversation

Kernel Panic on 2.6.23-rc5

DISCUSSION Daniel Exner 2 participants 4 messages Sep 6, 2007 – Sep 12, 2007

lore
Share & tools
lore
#0 lore raw

Hi!

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

I Also keep getting ext3 errors about reading or writing in wrong zones. Will now have a - this means many - run of memtest.

Signature · 2 lines
Greetings
Daniel Exner
#1 lore raw

Hi Daniel,

Quoted 11 lines · Daniel Exner

Hi!

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 may want to use mcelog ftp://ftp.x86-64.org/pub/linux/tools/mcelog/

Quoted 7 lines

I Also keep getting ext3 errors about reading or writing in wrong zones. Will now have a - this means many - run of memtest.

--
Greetings
Daniel Exner

Regards,
Michal

Signature · 2 lines
LOG
http://www.stardust.webpages.pl/log/
#2 lore raw

06 September 2007 Michal Piotrowski wrote:
[..]

Quoted 7 lines
Quoted 3 lines

CPU 0: Machine Check Exception: 0000000000000004
Bank 4: b200000000070f0f

Kernel panic - not syncing: CPU context corrupt

It is a hardware problem.

You may want to use mcelog ftp://ftp.x86-64.org/pub/linux/tools/mcelog/

Tried this on grml64 (cause I'm normaly on x86)
Results:

--
WARNING: with --dmi mcelog --ascii must run on the same machine with the
same BIOS/memory configuration as where the machine check occurred.
HARDWARE ERROR. This is *NOT* a software problem!
Please contact your hardware vendor
CPU 0 0 data cache STATUS 0 MCGSTATUS 4
Bank 4: b200000000070f0f

Kernel panic - not syncing: CPU context corrupt

---

This really doesnt say me anything the above didn't. Next thing I tried was:

parsemce-e 0 -b 4 -s b200000000070f0f -a 0
Output:
Status: (0) Restart IP invalid.
parsebank(4): b200000000070f0f @ 0
External tag parity error
CPU state corrupt. Restart not possible
Error enabled in control register
Error not corrected.
Bus and interconnect error
Participation: Generic
Timeout:
Request: Generic error
Transaction type : Invalid
Memory/IO : Other

Wich doesnt tell me anything either :(

Google suggest anything from broken CPU(bad), broken RAM(even more bad) to broken mainboard(Ouch..)

I'm going to let memtest run overnight. This is the easiest test I guess :)

Signature · 5 lines
Greetings
Daniel Exner
-- 
Mit freundlichen Grüßen
Daniel Exner
#3 lore raw

Re: Kernel Panic on 2.6.23-rc5 (solved)

In reply to Michal Piotrowski

Hi!

Michal Piotrowski:

Quoted 11 lines · Daniel Exner
Quoted 9 lines

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..

Quoted 1 line

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.

Signature · 2 lines
Greetings
Daniel Exner