From: bastien ROUCARIES <roucaries.bastien@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "H. Peter Anvin" <hpa@zytor.com>, 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, 9 Jan 2012 17:00:08 +0100 [thread overview]
Message-ID: <201201091700.09318.roucaries.bastien@gmail.com> (raw)
In-Reply-To: <201111160019.51303.rjw@sisk.pl>
Le Wednesday 16 November 2011 00:19:51, Rafael J. Wysocki a écrit :
> From: Rafael J. Wysocki <rjw@sisk.pl>
>
> Dell OptiPlex 990 is known to require PCI reboot, so add it to the reboot
> blacklist in pci_reboot_dmi_table[].
Sorry to hi jack this thread but it seems that dell made the same crap with my precision T1600. See
http://www.centos.org/modules/newbb/print.php?form=1&topic_id=32948&forum=55&order=ASC&start=0
or
https://bugzilla.redhat.com/show_bug.cgi?id=698239
Thanks
Bastien
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> ---
> arch/x86/kernel/reboot.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> Index: linux/arch/x86/kernel/reboot.c
> ===================================================================
> --- linux.orig/arch/x86/kernel/reboot.c
> +++ linux/arch/x86/kernel/reboot.c
> @@ -443,6 +443,14 @@ static struct dmi_system_id __initdata p
> DMI_MATCH(DMI_PRODUCT_NAME, "Latitude E6420"),
> },
> },
> + { /* Handle problems with rebooting on the OptiPlex 990. */
> + .callback = set_pci_reboot,
> + .ident = "Dell OptiPlex 990",
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
> + DMI_MATCH(DMI_PRODUCT_NAME, "OptiPlex 990"),
> + },
> + },
> { }
> };
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2012-01-09 20:37 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 ` bastien ROUCARIES [this message]
2012-01-09 21:53 ` [PATCH] x86 / reboot: " 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
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=201201091700.09318.roucaries.bastien@gmail.com \
--to=roucaries.bastien@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 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).