linux-kernel - Re: reboot via bios on X86

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

Date:	Tue, 10 Apr 2012 13:26:43 -0400
From:	Miles Fidelman <mfidelman@...tinghouse.net>
To:	Matthew Garrett <mjg@...hat.com>
CC:	linux-kernel@...r.kernel.org, tglx@...utronix.de, mingo@...hat.com,
	hpa@...or.com, x86@...nel.org, peter.chubb@...ta.com.au,
	michael.d.labriola@...il.com
Subject: Re: reboot via bios on X86_64?

Matthew Garrett wrote:
> The default behaviour is now to use the ACPI reboot vector, and the
> behaviour was tweaked somewhat to make it work better with a variety of
> machines. If 3.3 doesn't work then we've got a problem, but I could
> absolutely believe that 2.6.32 would fail to work.
>
Interesting.  The comments still indicate that kbd is the default vector.

In any case:
- just booted with a gentoo liveCD (3.3.0 kernel)
- tried the default reboot - hangs (last console message: "Remounting / 
read only ..")
- tried with reboot=a - hangs (same last console message)

For what it's worth, creating a path for X86_64 mode to reboot through 
the bios seems like
a good thing to put on the wish list.






-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


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