From: Arjan van de Ven <arjan@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Dave Young <dyoung@redhat.com>
Cc: Yu Chen <yu.c.chen@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Juergen Gross <jgross@suse.com>, Tony Luck <tony.luck@intel.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Borislav Petkov <bp@alien8.de>, Rui Zhang <rui.zhang@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Ingo Molnar <mingo@kernel.org>,
Kexec Mailing List <kexec@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ebiederm@redhat.com, Tom Lendacky <thomas.lendacky@amd.com>,
Baoquan He <bhe@redhat.com>
Subject: Re: kexec reboot fails with extra wbinvd introduced for AME SME
Date: Wed, 17 Jan 2018 18:53:34 -0800 [thread overview]
Message-ID: <47fe0d37-93d9-1394-062a-f973a38daa16@linux.intel.com> (raw)
In-Reply-To: <CA+55aFzc9eXKOdhS-ygQPbr0_N84d8iE8WbSGOWmpJXr1rvDjQ@mail.gmail.com>
>
> 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)
next prev parent reply other threads:[~2018-01-18 2:53 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 [this message]
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
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=47fe0d37-93d9-1394-062a-f973a38daa16@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=bhe@redhat.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dyoung@redhat.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
all inboxes | Powered by JetHome®