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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 03 Apr 2014 14:30:50 +0800
From:	"Li, Aubrey" <>
To:	Steven Rostedt <>,
	Ingo Molnar <>,
	Linus Torvalds <>,
	LKML <>,
	"H. Peter Anvin" <>,
	Thomas Gleixner <>,
	Matthew Garrett <>
Subject: Re: FW: [BUG] x86: reboot doesn't reboot

> From: Steven Rostedt []
> Sent: Thursday, April 03, 2014 2:14 PM
> To: Linus Torvalds; LKML
> Cc: Ingo Molnar; H. Peter Anvin; Thomas Gleixner; Li, Aubrey; Matthew Garrett
> 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.

May I know if "reboot=t" make any difference on your system with the change?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists