[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180118025702.GA2242@dhcp-128-65.nay.redhat.com>
Date: Thu, 18 Jan 2018 10:57:02 +0800
From: Dave Young <dyoung@...hat.com>
To: Arjan van de Ven <arjan@...ux.intel.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Yu Chen <yu.c.chen@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
Juergen Gross <jgross@...e.com>,
Tony Luck <tony.luck@...el.com>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
Borislav Petkov <bp@...en8.de>,
Rui Zhang <rui.zhang@...el.com>,
Dan Williams <dan.j.williams@...el.com>,
Ingo Molnar <mingo@...nel.org>,
Kexec Mailing List <kexec@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
ebiederm@...hat.com, Tom Lendacky <thomas.lendacky@....com>,
Baoquan He <bhe@...hat.com>
Subject: Re: kexec reboot fails with extra wbinvd introduced for AME SME
On 01/17/18 at 06:53pm, Arjan van de Ven wrote:
> >
> > Does anybody have any other ideas?
>
> wbinvd is thankfully not common, but also not rare (MTRR setup and a bunch of other cases)
> and in some other operating systems it happens even more than on Linux.. it's generally not totally broken like this.
>
> I can only imagine a machine check case where a write back to a bad cell causes some parity error
> or something... but it's odd that no other machine checks are reported?
> (can the user check for this please)
Could you say more about how to check this? My .config disabled
CONFIG_X86_MCE, should this be enabled?
Thanks
Dave
Powered by blists - more mailing lists