Created attachment 669638 [details]
Output of lspci -vvv on a Lenovo B590
Description of problem:
When "Power Off" is selected from Gnome Shell, the system does a restart instead.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start Gnome Shell session in F18
2. "Power Off"
The machine exhibiting the bug is a Lenovo B590 laptop. I'm attaching the output of lspci -vvv. The machine uses UEFI firmware with Secure Boot disabled. The bug is not completely reproducible, but it does occur on about 3 out of 4 shutdowns. The closed bug #710532 is the same issue. Therein is a reference to the following kernel bug that has been closed as fixed:
I don't know whether this is a systemd or kernel issue.
Can you do the following on the console:
systemctl poweroff -ff
This will immediately power off your machine, so make sure to sync things before, in order not to lose any data. Is the issue reproducible with this? If so, then this is a kernel issue.
Tried that twice, and got one shutdown and one restart. Looks like a kernel bug. This is still on 3.6.11-3.fc18.x86_64. I changed the component.
Can you try this scratch build when it completes? It contains the patch referenced in the kernel.org bug.
That seems to work for me. With 3.7.1-3.4.fc18.x86_64, "power off" stayed powered off 5 times out of 5 tests.
Great, thank you for testing. I'll get the patch included into Fedora and in an official build later today.
kernel-3.7.1-5.fc18 has been submitted as an update for Fedora 18.
kernel-3.6.11-4.fc16 has been submitted as an update for Fedora 16.
kernel-3.6.11-5.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-3.7.1-5.fc18'
as soon as you are able to, then reboot.
Please go to the following url:
then log in and leave karma (feedback).
kernel-3.7.2-201.fc18 has been submitted as an update for Fedora 18.
I just got two restarts on power off on 3.7.1-3.4.fc18.x86_64. I will test the latest version later today.
3.7.2-201.fc18.x86_64 does not fix the bug on my system. 3 out of 6 attempts at shutdown resulted in restart.
I seem to have had a period of five days and maybe 20 problem-free shutdowns on kernel version 3.7.1-3.4.fc18.x86_64. Then the bug recurred today on both 3.7.1-3.4.fc18.x86_64 and now 3.7.2-201.fc18.x86_64. Maybe that was just chance, but I did install some updates yesterday (2013-01-12), including a new version of systemd (195-15.fc18.x86_64). I don't know whether that has anything to do with this.
kernel-3.7.2-201.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
The problem still persists.
Please test "sync && systemctl poweroff -ff" again to make sure it's not caused by something else this time.
Did "sync && systemctl poweroff -ff" twice and again got one shutdown and one restart (3.7.1-3.4.fc18.x86_64).
Here are the version details that the firmware on this machine (Lenovo B590) reports.
UEFI BIOS version: H1ET63WW (1.06)
UEFI BIOS date: 2012-09-04
Embedded controller version: H1EC31WW (1.11)
Machine type model: 627429G
kernel-3.6.11-5.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
The problem does still persist on
I can also confirm this on a Compaq desktop (Intel Core i3, HD4000 graphics (I don't have more chipset information handy) in addition to the Lenovo B590 laptop.
kernel-3.6.11-4.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
I have experienced a couple of restarts on power off on
I don't quite understand why this bug is closed, but I suppose that's one way of fixing it.
(In reply to comment #22)
> I have experienced a couple of restarts on power off on
> I don't quite understand why this bug is closed, but I suppose that's one
> way of fixing it.
Does the file "/run/initramfs/.need_shutdown" exist, when you are booted up?
> Does the file "/run/initramfs/.need_shutdown" exist, when you are booted up?
I'm still on 3.7.5-201, because I'm using wireless drivers from RPM Fusion that are not available for 3.7.6-201 yet. I haven't confirmed the unwanted restarts on 3.7.6-201.
The bug is still there in 3.7.9-205.fc18.x86_64.
Can you do this:
# mkdir -p /run/initramfs/etc/cmdline.d
# echo "rd.break=shutdown rd.debug" > /run/initramfs/etc/cmdline.d/debug.conf
# touch /run/initramfs/.need_shutdown
and then you are dropped to a shell at the very last shutdown stage.
You might want to do this
# ps ax
and maybe take a picture of the output. Then you can try:
# poweroff -f -d -n
Created attachment 709066 [details]
photo screenshot of "ps ax" (1/2)
Created attachment 709067 [details]
photo screenshot of "ps ax" (2/2)
I took a photo of the screen after "ps ax", or actually two, as I got two screenfuls of processes. I did get one unwanted reboot after "poweroff -f -d -n" on 3.8.2-206.fc18.x86_64, so I can confirm the problem on the current kernel version.
(In reply to comment #28)
> Created attachment 709067 [details]
> photo screenshot of "ps ax" (2/2)
looks good ... processes with  are kernel thread and are of no harm.
(In reply to comment #29)
> I took a photo of the screen after "ps ax", or actually two, as I got two
> screenfuls of processes. I did get one unwanted reboot after "poweroff -f -d
> -n" on 3.8.2-206.fc18.x86_64, so I can confirm the problem on the current
> kernel version.
so, that's a real kernel problem then.