linux-kernel - Re: Fix apparent cut-n-paste mistake in Dell reboot workaround.

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 27 Sep 2013 16:19:51 -0400
From:	Dave Jones <davej@...hat.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	x86@...nel.org, Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: Fix apparent cut-n-paste mistake in Dell reboot workaround.

On Fri, Sep 27, 2013 at 03:16:49PM -0500, H. Peter Anvin wrote:
 > On 09/24/2013 07:13 PM, Dave Jones wrote:
 > > This seems to have been copied from the Optiplex 990 entry above, but somoene
 > > forgot to change the ident text.
 > > 
 > > Signed-off-by: Dave Jones <davej@...oraproject.org>
 > > 
 > > diff --git a/arch/x86/kernel/reboot.c b/arch/x86/kernel/reboot.c
 > > index f6835d8..ea2aaca 100644
 > > --- a/arch/x86/kernel/reboot.c
 > > +++ b/arch/x86/kernel/reboot.c
 > > @@ -360,7 +360,7 @@ static struct dmi_system_id __initdata reboot_dmi_table[] = {
 > >  	},
 > >  	{	/* Handle problems with rebooting on the Precision M6600. */
 > >  		.callback = set_pci_reboot,
 > > -		.ident = "Dell OptiPlex 990",
 > > +		.ident = "Dell Precision M6600",
 > >  		.matches = {
 > >  			DMI_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
 > >  			DMI_MATCH(DMI_PRODUCT_NAME, "Precision M6600"),
 > > 
 > 
 > It really is starting to feel like *ALL* Dell machines need reboot=pci?

Either that or 'bios'.  The question I have is, of those marked 'bios', does =pci
work too ?  If we knew that was true, I'd probably say yes.

	Dave

--
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/