linux-kernel - Re: [PATCH] x86: Dell Precision WorkStation 690 reboot quirk

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 9 Dec 2010 15:27:06 +0000
From:	Matthew Garrett <mjg@...hat.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Edouard Gomez <ed.gomez@...e.fr>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
	Thomas Backlund <tmb@...driva.org>,
	Leann Ogasawara <leann.ogasawara@...onical.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: Dell Precision WorkStation 690 reboot quirk

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 | mjg59@...f.ucam.org
--
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/