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: Ingo Molnar <mingo@xxxxxxx>
- Date: Mon, 17 Aug 2009 11:20:47 +0200
- 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: <4A891E17.1090901@xxxxxxxxxxxxxx>
- References: <tip-4efc0670baf4b14bc95502e54a83ccf639146125@xxxxxxxxxxxxxx> <20090812113652.GA19632@xxxxxxx> <4A88E3E4.40506@xxxxxxxxxxxxxx> <20090817083544.GC15390@xxxxxxx> <4A891E17.1090901@xxxxxxxxxxxxxx>
- User-agent: Mutt/1.5.18 (2008-05-17)
* Hidetoshi Seto <seto.hidetoshi@xxxxxxxxxxxxxx> wrote:
> 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)
btw., that reminds me: mce_rdmsrl() needs to be fixed to use
rdmsrl_safe() and it should emit a WARN_ONCE() if it ever hits an
error while trying to access registers.
Ingo
--
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]
