All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastien ROUCARIES <roucaries.bastien@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>, Ingo Molnar <mingo@elte.hu>,
	Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	x86@kernel.org
Subject: Re: [PATCH] x86 / reboot: Blacklist Dell OptiPlex 990 known to require PCI reboot
Date: Mon, 23 Jan 2012 11:28:11 +0100	[thread overview]
Message-ID: <CAE2SPAak9xnN8Tbjru3eLN79_JGTGaPWi7w+t=7peN-Nd9f+Bw@mail.gmail.com> (raw)
In-Reply-To: <4F1478B0.6080200@zytor.com>

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 ?

Bastien

>        -hpa
>

  reply	other threads:[~2012-01-23 10:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-15 23:19 [PATCH] x86 / reboot: Blacklist Dell OptiPlex 990 known to require PCI reboot Rafael J. Wysocki
2011-12-05 13:25 ` [tip:x86/urgent] x86/reboot: " tip-bot for Rafael J. Wysocki
2012-01-09 16:00 ` [PATCH] x86 / reboot: " bastien ROUCARIES
2012-01-09 21:53   ` Rafael J. Wysocki
2012-01-10 16:28     ` Bastien ROUCARIES
2012-01-16  0:41   ` Matthew Garrett
2012-01-16 11:27     ` Bastien ROUCARIES
2012-01-16 11:35       ` Bastien ROUCARIES
2012-01-16 19:21       ` H. Peter Anvin
2012-01-23 10:28         ` Bastien ROUCARIES [this message]
2012-01-31  9:49           ` Bastien ROUCARIES
2012-01-31 12:15             ` [VT-d reboot problems] " Ingo Molnar
2012-02-14 18:17               ` 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='CAE2SPAak9xnN8Tbjru3eLN79_JGTGaPWi7w+t=7peN-Nd9f+Bw@mail.gmail.com' \
    --to=roucaries.bastien@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mjg59@srcf.ucam.org \
    --cc=rjw@sisk.pl \
    --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 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.