From: Ingo Molnar <mingo@elte.hu>
To: Bastien ROUCARIES <roucaries.bastien@gmail.com>,
Avi Kivity <avi@redhat.com>, Sheng Yang <sheng@linux.intel.com>,
KVM devel mailing list <kvm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: [VT-d reboot problems] Re: [PATCH] x86 / reboot: Blacklist Dell OptiPlex 990 known to require PCI reboot
Date: Tue, 31 Jan 2012 13:15:13 +0100 [thread overview]
Message-ID: <20120131121513.GE32010@elte.hu> (raw)
In-Reply-To: <CAE2SPAbHxjQm3-z+LRXYBJAVnrwjMn=u=9RFLmZ6hkc8XtNy+w@mail.gmail.com>
(added KVM folks to the Cc:)
* Bastien ROUCARIES <roucaries.bastien@gmail.com> wrote:
> Ping^2
>
> Bastien
> On Mon, Jan 23, 2012 at 11:28 AM, Bastien ROUCARIES
> <roucaries.bastien@gmail.com> wrote:
> > On Mon, Jan 16, 2012 at 8:21 PM, H. Peter Anvin <hpa@zytor.com> wrote:
> >> On 01/16/2012 03:27 AM, Bastien ROUCARIES wrote:
> >>>>
> >>>> Does it work if you disable VT-d in the firmware? If so, then adding it
> >>>> to the reboot method blacklist is the wrong fix - we need to figure out
> >>>> why VT-d interferes with Dell's reboot code.
> >>>
> >>> Yes it work
> >>>
> >>
> >> This is particularly so since we are very close to having a full Dell
> >> model catalogue in the kernel...
> >
> > Ping ? Do you need some dump ? testing ?
So disabling VT-d in the BIOS fixes the reboot problem and
Matthew Garrett suggests we should figure out why and how VT-d
on this Dell box interferes with the reboot method.
Thanks,
Ingo
next parent reply other threads:[~2012-01-31 12:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201111160019.51303.rjw@sisk.pl>
[not found] ` <201201091700.09318.roucaries.bastien@gmail.com>
[not found] ` <20120116004110.GA21240@srcf.ucam.org>
[not found] ` <CAE2SPAZH9vQ=7mTxaCGY6DHdf5Yvv-0SWCwUobUY3tTD5caLow@mail.gmail.com>
[not found] ` <4F1478B0.6080200@zytor.com>
[not found] ` <CAE2SPAak9xnN8Tbjru3eLN79_JGTGaPWi7w+t=7peN-Nd9f+Bw@mail.gmail.com>
[not found] ` <CAE2SPAbHxjQm3-z+LRXYBJAVnrwjMn=u=9RFLmZ6hkc8XtNy+w@mail.gmail.com>
2012-01-31 12:15 ` Ingo Molnar [this message]
2012-02-14 18:17 ` [VT-d reboot problems] Re: [PATCH] x86 / reboot: Blacklist Dell OptiPlex 990 known to require PCI reboot Bastien ROUCARIES
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=20120131121513.GE32010@elte.hu \
--to=mingo@elte.hu \
--cc=avi@redhat.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=rjw@sisk.pl \
--cc=roucaries.bastien@gmail.com \
--cc=sheng@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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).