# HG changeset patch
# User Edouard Gomez <[email protected]>
# Date 1291821505 -3600
# Node ID 4d8b4b3a1d3c6034b86889fac38dd53e6579bb42
# Parent 53e51000d59963c8ca408db4db619d2c82374c5e
x86: Dell Precision WorkStation 690 reboot quirk
This Dell workstation gets stuck on reboot unless booted with
the paremeter reboot=bios.
This patch has been submitted 3 times already to X86 ARCHITECTURE
maintainers w/o any feedback so far. Trying my chance on the LKML.
Patch is against 2.6.36.1
Signed-off-by: Edouard Gomez <[email protected]>
diff --git a/arch/x86/kernel/reboot.c b/arch/x86/kernel/reboot.c
--- a/arch/x86/kernel/reboot.c
+++ b/arch/x86/kernel/reboot.c
@@ -236,6 +236,15 @@
DMI_MATCH(DMI_PRODUCT_NAME, "Precision WorkStation T7400"),
},
},
+ { /* Handle problems with rebooting on Dell 690's */
+ .callback = set_bios_reboot,
+ .ident = "Dell Precision 690",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
+ DMI_MATCH(DMI_PRODUCT_NAME, "Precision WorkStation 690"),
+ DMI_MATCH(DMI_BOARD_NAME, "0MY171"),
+ },
+ },
{ /* Handle problems with rebooting on HP laptops */
.callback = set_bios_reboot,
.ident = "HP Compaq Laptop",
On Wed, 8 Dec 2010, Edouard Gomez wrote:
> # HG changeset patch
> # User Edouard Gomez <[email protected]>
> # Date 1291821505 -3600
> # Node ID 4d8b4b3a1d3c6034b86889fac38dd53e6579bb42
> # Parent 53e51000d59963c8ca408db4db619d2c82374c5e
> x86: Dell Precision WorkStation 690 reboot quirk
>
> This Dell workstation gets stuck on reboot unless booted with
> the paremeter reboot=bios.
>
> This patch has been submitted 3 times already to X86 ARCHITECTURE
> maintainers w/o any feedback so far. Trying my chance on the LKML.
Sorry, but I haven't seen this patch in my inbox and my mail server
log has only a single connection attempt to deliver mail from you on
Dec. 8 which ended up in one of my spam traps.
Cc'ing LKML (or some other relevant mailinglist) is recommended for
sending patches anyway. Documentation/SubmittingPatches says:
Unless you have a reason NOT to do so, CC [email protected].
Thanks,
tglx
My testing suggests that Windows never uses the BIOS-style reboot
approach, so this seems wrong. Does reboot=acpi work for you?
--
Matthew Garrett | [email protected]
On 12/09/2010 07:16 AM, Matthew Garrett wrote:
> My testing suggests that Windows never uses the BIOS-style reboot
> approach, so this seems wrong. Does reboot=acpi work for you?
We have talked about switching to reboot=acpi by default for machines
newer than <some date>... this would be good to do.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
On Thu, Dec 09, 2010 at 07:19:44AM -0800, H. Peter Anvin wrote:
> On 12/09/2010 07:16 AM, Matthew Garrett wrote:
> > My testing suggests that Windows never uses the BIOS-style reboot
> > approach, so this seems wrong. Does reboot=acpi work for you?
>
> We have talked about switching to reboot=acpi by default for machines
> newer than <some date>... this would be good to do.
The majority of systems with valid ACPI reboot vectors appear to just be
pointing at the PCI reset port, which makes sense. My testing suggests
that Windows calls the ACPI reboot vector, then tries to use the i8042,
then tries the ACPI reboot vector again and finally tries the i8042
again before giving up and spinning. I'll recheck this behaviour today
and then send a patch.
--
Matthew Garrett | [email protected]