linux-kernel - Re: [HW PROBLEM] Intel I7 MCE. Erratum or not?

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]

Message-ID: <12bfabe40812080226h13b8d52bia39cc20b404ba910@mail.gmail.com>
Date:	Mon, 8 Dec 2008 11:26:19 +0100
From:	"Giangiacomo Mariotti" <gg.mariotti@...il.com>
To:	"Hidetoshi Seto" <seto.hidetoshi@...fujitsu.com>
Cc:	"Arjan van de Ven" <arjan@...radead.org>,
	"Robert Hancock" <hancockr@...w.ca>, linux-kernel@...r.kernel.org,
	"Andi Kleen" <ak@...ux.intel.com>
Subject: Re: [HW PROBLEM] Intel I7 MCE. Erratum or not?

On 12/8/08, Hidetoshi Seto <seto.hidetoshi@...fujitsu.com> wrote:
>
> IIRC, this error is not what happen on the time [301.7320xx] during
> boot, but happen before the boot.  Since the record says "Processor
> context corrupt," MCE handler should call panic(or do something stop
> the system) if the context actually corrupted during the boot.
>
> In other words, it seems that 1) the error was recorded at last time
> when your machine crashed unexpectedly(by cosmic-ray etc.) and not cleared
> yet, or 2) your machine is doing something wrong in every reset/poweroff.
>
> Could you try "mce=nobootlog" boot option?
>
> Thanks,
> H.Seto
>
>
I tried "mce=nobootlog" and the mce log seems to have disappeared :

[  183.276037] kjournald starting.  Commit interval 5 seconds
[  183.276462] EXT3 FS on sdb7, internal journal
[  183.276470] EXT3-fs: mounted filesystem with ordered data mode.
[  183.298408] kjournald starting.  Commit interval 5 seconds
[  183.299343] EXT3 FS on sdb8, internal journal
[  183.299351] EXT3-fs: mounted filesystem with ordered data mode.
[  374.273215] kobject: '11:0:0:0' (ffff8801279c4448): kobject_uevent_env
[  374.273231] kobject: '11:0:0:0' (ffff8801279c4448): fill_kobj_path:
path = '/devices/pci0000:00/0000:00:1c.1/0000:07:00.1/host11/target11:0:0/11:0:0:0'
[  374.274167] kobject: 'sr0' (ffff880127127608): kobject_uevent_env
[  374.274194] kobject: 'sr0' (ffff880127127608): fill_kobj_path: path
= '/devices/pci0000:00/0000:00:1c.1/0000:07:00.1/host11/target11:0:0/11:0:0:0/block/sr0'
[  376.119589] kobject: '65534' (ffff88011c4c8060):
kobject_add_internal: parent: 'uids', set: 'uids'
[  376.119618] kobject: '65534' (ffff88011c4c8060): kobject_uevent_env
[  376.119640] kobject: '65534' (ffff88011c4c8060): fill_kobj_path:
path = '/kernel/uids/65534'

Now that you mention it, I always shut down the system from Linux,
because reboot doesn't work(from windows vista 32bit it works). If I
reboot the system from Linux it goes down, but then it enters a cycle
of automatic power down power up(with a beep) and it never stops until
I switch off the power supply.
--
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/