[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180118030448.GA7124@dhcp-128-65.nay.redhat.com>
Date: Thu, 18 Jan 2018 11:04:48 +0800
From: Dave Young <dyoung@...hat.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Arjan van de Ven <arjan@...ux.intel.com>,
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 07:00pm, Linus Torvalds wrote:
> On Wed, Jan 17, 2018 at 6:57 PM, Dave Young <dyoung@...hat.com> wrote:
> >
> > Could you say more about how to check this? My .config disabled
> > CONFIG_X86_MCE, should this be enabled?
>
> By all means, try it.
>
> Some pending machine check exception that we have *not* reacted to,
> and that is pending around kexec boot could very possibly be relevant.
>
> I forget your exact symptoms. Was it that the _first_ kexec works, but
> the second one hangs? Or was that the other unrelated issue? Or have I
> confused this with some other report entirely?
Yes, 1st kexec works, 2nd hangs.
Rebuilding with MCE enabled now.
Thanks
Dave
>
> Linus
Powered by blists - more mailing lists