linux-kernel - [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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20140403021411.6236996f@gandalf.local.home>
Date:	Thu, 3 Apr 2014 02:14:11 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Cc:	Ingo Molnar <mingo@...nel.org>, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Aubrey Li <aubrey.li@...el.com>,
	Matthew Garrett <mjg59@...f.ucam.org>
Subject: [BUG] x86: reboot doesn't reboot

I noticed that one of my test boxes no longer does a reboot with the
latest kernel. It goes down and shows:

[   51.589896] reboot: Restarting system
[   51.593567] reboot: machine restart

And the system sounds like it turns off (the fans stop), but then I
just sit there and wait, and wait and wait. The system never starts up
again.

I did a bisect and it landed on: a4f1987e4c54 "x86, reboot: Add EFI and
CF9 reboot methods into the default list" which looks like a very
likely suspect. I removed that and fb3bd7b19b2b, as the second commit
was just a fix up of the first, recompiled, installed and rebooted to
that kernel. I tried to reboot again and sure enough after posting the
"machine restart" I started getting those "Press any key to continue."
messages again. That's a good sign.

Linus mentioned to me to use "reboot=pci" on the kernel command line,
but no dice. That doesn't seem to make a difference.

I see in the merge commit:

    Pull x86 reboot changes from Ingo Molnar:
     "Refine the reboot logic around the CF9 and EFI reboot methods, to make
      it more robust.  The expectation is for no working system to break,
      and for a couple of reboot-force systems to start rebooting
      automatically again"

Unfortunately, the expectation of no working system to break, didn't
quite stand up to expectations :-/

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