Re: [boot crash] Re: [tip:x86/mce3] x86, mce: use 64bit machine check code on 32bit
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [boot crash] Re: [tip:x86/mce3] x86, mce: use 64bit machine check code on 32bit
- From: Hidetoshi Seto <seto.hidetoshi@xxxxxxxxxxxxxx>
- Date: Mon, 17 Aug 2009 18:08:39 +0900
- Cc: linux-kernel@xxxxxxxxxxxxxxx, mingo@xxxxxxxxxx, hpa@xxxxxxxxx, ak@xxxxxxxxxxxxxxx, tglx@xxxxxxxxxxxxx, Yinghai Lu <yinghai@xxxxxxxxxx>, Huang Ying <ying.huang@xxxxxxxxx>, "Rafael J. Wysocki" <rjw@xxxxxxx>, linux-tip-commits@xxxxxxxxxxxxxxx
- In-reply-to: <20090817083544.GC15390@xxxxxxx>
- References: <tip-4efc0670baf4b14bc95502e54a83ccf639146125@xxxxxxxxxxxxxx> <20090812113652.GA19632@xxxxxxx> <4A88E3E4.40506@xxxxxxxxxxxxxx> <20090817083544.GC15390@xxxxxxx>
- User-agent: Thunderbird 2.0.0.22 (Windows/20090605)
Ingo Molnar wrote:
> * Hidetoshi Seto <seto.hidetoshi@xxxxxxxxxxxxxx> wrote:
>> Could you try boot your laptop with mce=nobootlog?
>
> Hm, why should that make any difference? mce=nobootlog only
> influences whether we pass records into the mcelog buffer but does
> not affect whether we touch the hardware.
Old mce codes doesn't take bootlog.
One possibility is: if the BIOS doesn't clear status in banks,
new mce codes will try to log such junks.
If the junk is totally junk but can be decoded as a valid log with
MISCV or ADDRV bit, and if the cpu try to access register which is
not implemented (e.g. IA32_MCi_MISC/ADDR), then such access might
cause a general protection exception. (ref. ASDM 3A 15.3.2.3)
I'm just guessing...
Thanks,
H.Seto
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]