lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-id: <4664B306.5000107@shaw.ca>
Date:	Mon, 04 Jun 2007 18:49:10 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	James Jarvis <James.Jarvis@...ac.uk>
Cc:	Riley@...liams.Name, Linux-Kernel@...r.kernel.org,
	graham.newton@...ac.uk, kenneth.macdonald@...ac.uk
Subject: Re: DMI_MATCH patch in reboot.c for SFF Dell OptiPlex 745 - fixes hang
 on reboot

James Jarvis wrote:
> I trust this is the right list...
> 
> The following patch enables reboot through BIOS on the Dell Optiplex 745 
> Small Form Factor base, on which reboot hangs. The larger form factor 
> does not require this, hence the match on DMI_BOARD_NAME.
> 
> --- arch/i386/kernel/reboot.c.orig      2007-06-01 12:22:53.000000000 +0100
> +++ arch/i386/kernel/reboot.c   2007-06-04 16:53:36.000000000 +0100
> @@ -104,6 +104,15 @@
>                        DMI_MATCH(DMI_PRODUCT_NAME, "PowerEdge 300/"),
>                },
>        },
> +       {       /* Handle problems with rebooting on Dell Optiplex 745's 
> SFF*/
> +               .callback = set_bios_reboot,
> +               .ident = "Dell OptiPlex 745",
> +               .matches = {
> +                       DMI_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
> +                       DMI_MATCH(DMI_PRODUCT_NAME, "OptiPlex 745"),
> +                       DMI_MATCH(DMI_BOARD_NAME, "0WF810"),
> +               },
> +       },
>        {       /* Handle problems with rebooting on Dell 2400's */
>                .callback = set_bios_reboot,
>                .ident = "Dell PowerEdge 2400",

This blacklist seems to be growing. Isn't there something better we can 
do here? Can we just reboot through the BIOS by default, is that really 
broken on some systems?

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@...pamshaw.ca
Home Page: http://www.roberthancock.com/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ