linux-kernel - Re: [BUG] x86: reboot doesn't reboot

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:	Fri, 4 Apr 2014 12:01:06 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Matthew Garrett <mjg59@...f.ucam.org>,
	"Li, Aubrey" <aubrey.li@...ux.intel.com>,
	Ingo Molnar <mingo@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [BUG] x86: reboot doesn't reboot

On Fri, 04 Apr 2014 08:39:51 -0700
"H. Peter Anvin" <hpa@...or.com> wrote:

> There are several platforms where the default boot method invokes an SMM
> handler which blithly assumes that the hardware is in whatever state
> Windows leaves it in, and hangs otherwise.  This seems to include nearly
> all Dell systems.  So it isn't really quite that simple...

Just an update. I pulled out of my closet an old Pentium III and got it
to finally boot the new kernel. It reboots fine, but as I left the
printk patch in, it didn't get to the cf9 usage. I take it, it can
detect the level. And perhaps the issues is only with x86_64?

I have no problem with sticking in reboot=b in my development box. I
just wanted people to know that I had issues.

Maybe keep the current way and on reboot, have a pr_info() stating, if
your system doesn't reboot try "reboot=b" on the kernel command line?

-- Steve

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