| 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
| ||
|
Message-Id: <201103112318.19678.rjw@sisk.pl> Date: Fri, 11 Mar 2011 23:18:19 +0100 From: "Rafael J. Wysocki" <rjw@...k.pl> To: Matthew Garrett <mjg59@...f.ucam.org> Cc: linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org, x86@...nel.org Subject: Re: [PATCH 1/4] X86: Revamp reboot behaviour to match Windows more closely On Friday, March 11, 2011, Matthew Garrett wrote: > On Fri, Mar 11, 2011 at 11:08:18PM +0100, Rafael J. Wysocki wrote: > > On Friday, March 11, 2011, Matthew Garrett wrote: > > > Windows reboots by hitting the ACPI reboot vector (if available), trying > > > the keyboard controller, hitting the ACPI reboot vector again and then > > > giving the keyboard controller one last go. Rework our reboot process a > > > little to default to matching this behaviour, although we'll fall through > > > to attempting a triple fault if nothing else works. > > > > Does this fix a particular problem observed in practice? > > Yup. We're seeing an increasing number of machines that don't implement > the legacy keyboard controller at all and fail to reboot if you poke it. > The expectation appears to be that you use the ACPI reboot vector on > these machines. So perhaps you can put a pointer or two into the changelog? That would show precisely that it's not just for pure Windows compatibility. Thanks, Rafael -- 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