Bug 698239 - [Sandybridge] System does not complete reboot
Summary: [Sandybridge] System does not complete reboot
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 731114
TreeView+ depends on / blocked
 
Reported: 2011-04-20 14:02 UTC by Mark Watts
Modified: 2013-08-23 15:16 UTC (History)
16 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-02-28 19:02:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mark Watts 2011-04-20 14:02:22 UTC
Smolt system profile:
http://www.smolts.org/client/show/?uuid=pub_50841318-5957-4363-92df-e0716623ea47

When instructing the laptop to reboot, the kernel will 'hang' with the message about "rebooting system" but never actually reboot.

Shutdowns are not affected - the laptop will correctly power off.

Comment 1 Mark Watts 2011-04-20 21:32:49 UTC
Issue also seen with Fedora 15 Beta LiveCD.

Comment 2 Mark Watts 2011-05-06 08:28:28 UTC
Updating this to "Sandybridge" since I have the exact same problem on a Dell Optiplex 990 with an Intel i5 Sandybridge processor.

Comment 3 Chuck Ebbert 2011-05-08 17:57:36 UTC
Is your machine using EFI to boot? Can you try booting with the kernel boot option "noefi" and see if that makes a difference?

Comment 4 Mark Watts 2011-05-10 09:14:31 UTC
I can't honestly say if I'm using EFI on any of these machines - the BIOS doesn't make it clear.

Setting "noefi" doesn't make a difference, however.

Comment 5 Mark Watts 2011-05-10 16:19:43 UTC
As an aside, "echo b > /proc/sysrq-trigger" doesn't reboot either.

Comment 6 jacob.greenstein 2011-06-16 23:48:37 UTC
I have exactly the same problem on Dell Latitude E6520 (CPU i7-2720QM,
Fedora 15, kernel 2.6.38.8, nVidia): when instructing laptop to reboot, the system 'hangs' with the message "rebooting the system" (after all processes are stopped).

Comment 7 Alan 2011-07-05 14:02:21 UTC
I see this exact same issue on a Dell Precision T1600 (Xeon 1225 3.10GHz) with FC13, 14 & 15.

Comment 8 jacob.greenstein 2011-07-05 14:46:17 UTC
On my system the issue was resolved once I added reboot=pci to the kernel command line (following a suggestion of jlshelby)

Comment 9 Alan 2011-07-05 15:11:21 UTC
Perfect, Thank you very much :)

Comment 10 Dave Jones 2011-09-01 18:05:20 UTC
Mark, is this still occurring with the 2.6.40.3 update ?
There was some work done on the reboot code to make it match the same behaviour that Microsoft windows expects.

Comment 11 Mark Watts 2011-09-06 15:05:19 UTC
2.6.40.3 still hangs on reboot with "Rebooting system..." as the last thing displayed.

I can try the reboot=pci workaround, but I'd prefer a 'correct' fix.

Comment 12 Tim Wegener 2011-09-09 02:50:44 UTC
I had the same problem:

Dell Latitude E6520
Intel® Core™ i7-2720QM CPU

kernel-2.6.40.4-5.fc15.x86_64

The reboot=pci workaround did the trick in my case.

Comment 13 Jeff Bastian 2011-09-22 19:26:38 UTC
Try disabling VT-d (Virtualization Technology for Directed I/O) in your BIOS and remove reboot=pci and see if the system will reboot.

See bug 731114 comment 20

Comment 14 Mark Watts 2011-09-30 10:31:49 UTC
I'm still seeing reboots hang on F16 Alpha.
Kernel 3.1.0-0rc8.git0.0.x86_64

I do not have an option to disable VT-d on my laptop, its just a virtualisation on/off switch.

Comment 15 robin orr 2011-10-24 20:22:34 UTC
Dell Optiflex 990.
Removed  "VT for Direct I/O" from the bios did the trick.

Comment 16 Alan 2011-10-25 09:47:58 UTC
Dell Precision T1600 - Xeon 1225 3.10GHz
FC-13 + CentOS-6.0

Un-ticking  "VT for Direct I/O" under Virtualization support in the bios menu fixes the reboot hang.

Comment 17 Josh Boyer 2012-02-28 19:02:29 UTC
F16 has the intel iommu disabled by default.  For those of you still having this issue, it should be resolved with kernels using 3.1.5 or newer.  If you're still seeing this problem on 3.2.7 or newer, please reopen.

Comment 18 Bert DeKnuydt 2012-03-21 10:39:03 UTC
I still see this on a Dell E6520, with F16 kernel 3.2.10-3.  reboot=pci still does the trick.

Comment 19 Celso Santos 2013-08-23 15:16:12 UTC
Well.. I already had this problems with Fedora 18 and I still get it with Fedora 19.

My machine is a Dell Latitude E5520, 2nd gen Intel i5 and I did try adding "reboot=pci" (which didn't solve the problem) and alternatively add "reboot=a,b,k,c" with which I did manage to successfuly reboot once, but not anymore.

So, any thought on additional solutions?


Note You need to log in before you can comment on or make changes to this bug.