From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Dave Airlie <airlied@gmail.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Dave Jones <davej@redhat.com>,
x86@kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Fix apparent cut-n-paste mistake in Dell reboot workaround.
Date: Mon, 30 Sep 2013 05:32:13 +0100 [thread overview]
Message-ID: <20130930043213.GA22194@srcf.ucam.org> (raw)
In-Reply-To: <CAPM=9txNWRKPzE=FNz63fi-7mwQq5DvNkVHik4gNodD9WBP9mw@mail.gmail.com>
On Mon, Sep 30, 2013 at 01:15:02PM +1000, Dave Airlie wrote:
> On Mon, Sep 30, 2013 at 1:06 PM, Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> > Likely indicates that our ACPI reboot handling still isn't bug
> > compatible with Windows. We'd do better fixing that than adding more DMI
> > entries.
>
> are these only with VTd enabled? I have some Dells that won't reboot
> with VTd turned on, I remember you though it was an acpi bug we
> couldn't do much with.
Oh, that's true - the ACPI reboot vector on the Dell tables I have to
hand appears to be via the keyboard controller, so there's probably some
SMM involved. I don't know if the VTd thing is still a problem (David
Woodhouse was looking into that at one point), but that would be a
reasonable point to start from.
--
Matthew Garrett | mjg59@srcf.ucam.org
prev parent reply other threads:[~2013-09-30 4:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 0:13 Fix apparent cut-n-paste mistake in Dell reboot workaround Dave Jones
2013-09-25 7:42 ` [tip:x86/urgent] x86/reboot: " tip-bot for Dave Jones
2013-09-27 20:16 ` H. Peter Anvin
2013-09-27 20:19 ` Dave Jones
2013-09-27 20:34 ` H. Peter Anvin
2013-09-30 2:57 ` Matthew Garrett
2013-09-30 2:58 ` H. Peter Anvin
2013-09-30 3:06 ` Matthew Garrett
2013-09-30 3:15 ` Dave Airlie
2013-09-30 4:23 ` H. Peter Anvin
2013-09-30 4:32 ` Matthew Garrett [this message]
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=20130930043213.GA22194@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=airlied@gmail.com \
--cc=davej@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--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