From: Dave Young <dyoung@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Juergen Gross <jgross@suse.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Tony Luck <tony.luck@intel.com>, Yu Chen <yu.c.chen@intel.com>,
Baoquan He <bhe@redhat.com>,
Kexec Mailing List <kexec@lists.infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rui Zhang <rui.zhang@intel.com>,
ebiederm@redhat.com, Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
Arjan van de Ven <arjan@linux.intel.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: kexec reboot fails with extra wbinvd introduced for AME SME
Date: Thu, 18 Jan 2018 11:31:18 +0800 [thread overview]
Message-ID: <20180118033118.GA1838@dhcp-128-65.nay.redhat.com> (raw)
In-Reply-To: <20180118030448.GA7124@dhcp-128-65.nay.redhat.com>
On 01/18/18 at 11:04am, Dave Young wrote:
> On 01/17/18 at 07:00pm, Linus Torvalds wrote:
> > On Wed, Jan 17, 2018 at 6:57 PM, Dave Young <dyoung@redhat.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.
dmesg only shows "mce: CPU supports 7 MCE banks"
Nothing special happens with MCE enabled , anyway thank all for
the hints, I will continue to think about this and maybe try more experiments.
>
> Thanks
> Dave
> >
> > Linus
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2018-01-18 3:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 2:52 Regression: kexec/kdump boot hangs with x86/vector commits Dave Young
2017-12-13 15:57 ` Yu Chen
2017-12-14 9:24 ` Dave Young
2018-01-04 3:15 ` Dave Young
2018-01-17 7:22 ` kexec reboot fails with extra wbinvd introduced for AME SME Dave Young
2018-01-17 15:06 ` Tom Lendacky
2018-01-18 1:50 ` Dave Young
2018-01-17 19:42 ` Linus Torvalds
2018-01-17 20:01 ` Tom Lendacky
2018-01-17 22:53 ` Tom Lendacky
2018-01-17 20:10 ` Linus Torvalds
2018-01-18 1:47 ` Dave Young
2018-01-18 2:14 ` Linus Torvalds
2018-01-18 2:29 ` Dave Young
2018-01-18 5:14 ` Tom Lendacky
2018-01-18 2:47 ` Dave Young
2018-01-18 2:56 ` Linus Torvalds
2018-01-18 2:53 ` Arjan van de Ven
2018-01-18 2:57 ` Dave Young
2018-01-18 3:00 ` Linus Torvalds
2018-01-18 3:04 ` Dave Young
2018-01-18 3:31 ` Dave Young [this message]
2018-01-18 3:00 ` Arjan van de Ven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180118033118.GA1838@dhcp-128-65.nay.redhat.com \
--to=dyoung@redhat.com \
--cc=arjan@linux.intel.com \
--cc=bhe@redhat.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=ebiederm@redhat.com \
--cc=jgross@suse.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rui.zhang@intel.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=yu.c.chen@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).