Red Hat Bugzilla – Bug 836657
Last modified: 2013-07-31 22:11:46 EDT
Description of problem:systemctl poweroff resets
Version-Release number of selected component (if applicable):
How reproducible: always
Steps to Reproduce:
2.bide a wee
3.system goes down as in restart, then restarts
Additional info: windows 7 (sorry) powers off as expected. Hardware is new; F17 install is first linux. files are up-to-date. SElinux is disabled.
Created attachment 595364 [details]
output of lshw
BIOS interface problem? It'a Intel's, DOB 02/24/2012
Does it power off if you use "sync && poweroff -f" ?
Alas, it reboots. shutdown -P reboots as well.
Could this be a problem with BIOS interface?
(In reply to comment #4)
> Alas, it reboots. shutdown -P reboots as well.
> Could this be a problem with BIOS interface?
It might be.
Can you remove the 'rhgb quiet' from the kernel line in the grub configuration file and see if there is anything additional printed to the screen?
Alas, I blinked :-(
Seriously, the messages scroll so quickly, its impossible to read anything. Is there a way to capture the output? (I presume that you are interested in the shutdown output.)
If it looks like a kernel panic, you can put 'pause_on_oops=30' on the kernel line in the grub configuration file and it should hold for 30 seconds.
On the small chance it has a serial port, you could just log everything with a serial console.
Or try this:
echo 8 > /proc/sys/kernel/printk
echo 2000 > /proc/sys/kernel/printk_delay
Now, that certainly slows things down. Aside from a mention that the state S5 is being select a few lines from "Power off", there's nothing that appears to be unusual.
FWIW, 'halt' halts, but does not power off. On Fedora 16, it powers off as well.It seems that this latter behavior is contrary to the man page.
Do you have the file "/run/initramfs/.need_shutdown" ??
If yes, does it help to do:
# systemctl mask dracut-shutdown.service
I don't have "/run/initramfs/.need_shutdown" Should I? What purpose does it serve?
(In reply to comment #12)
> I don't have "/run/initramfs/.need_shutdown" Should I? What purpose does it
If you don't have that, then it eliminates the possibility, that the dracut shutdown mechanism is responsible for your problems. Thanks!
I was told by Puget Systems that the motherboard in question (Intel DH77DF) has a problem with Linux (or vice-versa). Wake On Lan (WOL) needs to be disabled for poweroff to be effective. I've confirmed this.
The Intel Desktop Board status page (http://www.intel.com/support/motherboards/desktop/sb/cs-008326.htm) shows no support for this particular board. Given that it works under Windows 7, I suspect that its a glitch rather than a true bug. Perhaps someone with contacts in intel could investigate (in their spare time, of course :-)
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.