From: "tip-bot for Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
tglx@linutronix.de, rjw@sisk.pl, mingo@elte.hu
Subject: [tip:x86/urgent] x86/reboot: Blacklist Dell OptiPlex 990 known to require PCI reboot
Date: Mon, 5 Dec 2011 05:25:32 -0800 [thread overview]
Message-ID: <tip-6be30bb7d7504ec687a65c9bbdae8d1d2f8eaa19@git.kernel.org> (raw)
In-Reply-To: <201111160019.51303.rjw@sisk.pl>
Commit-ID: 6be30bb7d7504ec687a65c9bbdae8d1d2f8eaa19
Gitweb: http://git.kernel.org/tip/6be30bb7d7504ec687a65c9bbdae8d1d2f8eaa19
Author: Rafael J. Wysocki <rjw@sisk.pl>
AuthorDate: Wed, 16 Nov 2011 00:19:51 +0100
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Mon, 5 Dec 2011 12:20:43 +0100
x86/reboot: Blacklist Dell OptiPlex 990 known to require PCI reboot
Dell OptiPlex 990 is known to require PCI reboot, so add it to
the reboot blacklist in pci_reboot_dmi_table[].
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Link: http://lkml.kernel.org/r/201111160019.51303.rjw@sisk.pl
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
arch/x86/kernel/reboot.c | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/arch/x86/kernel/reboot.c b/arch/x86/kernel/reboot.c
index e334be1..4463d2f 100644
--- a/arch/x86/kernel/reboot.c
+++ b/arch/x86/kernel/reboot.c
@@ -443,6 +443,14 @@ static struct dmi_system_id __initdata pci_reboot_dmi_table[] = {
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"),
+ },
+ },
{ }
};
next prev parent reply other threads:[~2011-12-05 13:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 23:19 [PATCH] x86 / reboot: " Rafael J. Wysocki
2011-12-05 13:25 ` tip-bot for Rafael J. Wysocki [this message]
2012-01-09 16:00 ` 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
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=tip-6be30bb7d7504ec687a65c9bbdae8d1d2f8eaa19@git.kernel.org \
--to=rjw@sisk.pl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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
Powered by JetHome