linux-kernel - Re: Kernel Panic on 2.6.23-rc5

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 7 Sep 2007 00:14:08 +0200
From:	Daniel Exner <dex@...gonslave.de>
To:	"Michal Piotrowski" <michal.k.k.piotrowski@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Kernel Panic on 2.6.23-rc5

06 September 2007 Michal Piotrowski wrote:
[..]
> > 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 :)
-- 
Greetings
Daniel Exner
-- 
Mit freundlichen Grüßen
Daniel Exner
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/