From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Thomas Renninger <trenn@suse.de>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
linux-acpi@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH] X86: Solve Dell Latitudes do not reboot on x86_64 more generally
Date: Mon, 7 Nov 2011 14:27:40 +0000 [thread overview]
Message-ID: <20111107142740.GA17686@srcf.ucam.org> (raw)
In-Reply-To: <201111071525.14255.trenn@suse.de>
On Mon, Nov 07, 2011 at 03:25:13PM +0100, Thomas Renninger wrote:
> On Monday, November 07, 2011 02:59:24 PM Matthew Garrett wrote:
> > On Sat, Nov 05, 2011 at 01:44:03AM +0100, Thomas Renninger wrote:
> > > There are quite some reports that those do not reboot:
> > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/833705
> > > ->E6520, E6220
> > > http://www.linux-club.de/viewtopic.php?f=29&t=114459&start=20
> > > ->E5520
> > > and some more already are blacklisted
> >
> > It's a bug in the SMM code on these machines, and it goes away if you
> > disable VT-D. Let's try to actually fix it
> How do you intend to fix that?
> From description above it sounds as if this problem is not
> fixable from OS side.
Tear down VT-D state before reboot.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2011-11-07 14:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 2:29 [PATCH] x86: Fix reboot issue for Dell Optiplex 990 V2 Thomas Renninger
2011-11-04 7:16 ` Ismail Donmez
2011-11-05 0:44 ` [PATCH] X86: Solve Dell Latitudes do not reboot on x86_64 more generally Thomas Renninger
2011-11-07 1:54 ` Len Brown
2011-11-07 13:59 ` Matthew Garrett
2011-11-07 14:25 ` Thomas Renninger
2011-11-07 14:27 ` Matthew Garrett [this message]
2011-11-07 15:09 ` Thomas Renninger
2011-11-07 15:12 ` Matthew Garrett
2011-11-07 17:40 ` Len Brown
2011-11-06 19:48 ` [PATCH] x86: Fix reboot issue for Dell Optiplex 990 V2 Valdis.Kletnieks
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=20111107142740.GA17686@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=trenn@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.