FS#17205 - Shutdown is reboot and reboot is reboot thus no way to shutdown

Attached to Project: Arch Linux
Opened by Mark (markg85) - Thursday, 19 November 2009, 16:30 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 23 January 2010, 16:21 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Yea, that's odd but the case on my pc.
If i do (as root) poweroff the pc just reboots.
If i do halt -t now the pc also reboots.

So, now i pull the plug as soon i a hear my motherboard beep indicating a new boot cycle to get if off ^_^ that is certainly no way but the only way for me.
What might be of difference is that i have the testing repo enabled (was for gnome 2.28 a few months ago).

I don't know steps you can try.. perhaps this helps?

[mark@Mark-Arch ~]$ which shutdown
/sbin/shutdown
[mark@Mark-Arch ~]$

[mark@Mark-Arch ~]$ which halt
/sbin/halt
[mark@Mark-Arch ~]$

[mark@Mark-Arch ~]$ which reboot
/sbin/reboot
[mark@Mark-Arch ~]$

Nothing strange there as far as i can see..
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Saturday, 23 January 2010, 16:21 GMT
Reason for closing:  Works for me
Additional comments about closing:  No response in +1 month. Please reopen if necessary. Please check the last comment. Looks like a configuration error.
Comment by xduugu (xduugu) - Thursday, 19 November 2009, 16:44 GMT
Did you try to call shutdown directly instead of using halt/reboot/poweroff?
shutdown -h now
Comment by Mark (markg85) - Thursday, 19 November 2009, 16:52 GMT
Just tried that and it gave me a... reboot
Comment by Jan de Groot (JGC) - Thursday, 19 November 2009, 17:41 GMT
I think this is either a kernel bug or a bug in your mainboard (BIOS). What mainboard do you have, and does it have the latest BIOS?
Comment by Mark (markg85) - Thursday, 19 November 2009, 17:54 GMT
Asus P5K but a while ago this was just fine.
O and shutting down through KDE or Gnome (just figured that out btw) also works fine.
But shutting down as root, for example when i'm logged in through ssh, is not working and is rebooting my pc.
Comment by Jan de Groot (JGC) - Thursday, 19 November 2009, 18:05 GMT
In case of GNOME, it just executes ck-system-stop from the consolekit package, which is just a shell wrapper for shutdown -h now. There shouldn't be any difference between shutting down from GNOME or shutting down with shutdown -h now from console.
Comment by Gerardo Exequiel Pozzi (djgera) - Thursday, 26 November 2009, 05:19 GMT
Search for: p5k reboot instead of shutdown, show lots of results, and not only for Linux.
* Check BIOS settings.
* Can try differents options for acpi in kernel command line.
* Can try (with caution, previous check Asus forums for issues) latest BIOS firmware for your motherboard. Problems like this is directly related with bad ACPI tables.

We can't do much more here. :(
Comment by Mark (markg85) - Thursday, 26 November 2009, 13:35 GMT
Hi,

- i have the latest bios firmware
- It used to work just fine and i bet it works fine again when i reinstall archlinux but due to a LOT of settings and applications and a otherwise perfectly working archlinux i'm not about to reinstall it at the moment
- With KDE shutdown works as shutdown. (so i think that rules out bios settings)
- With gnome it's uncertain. can't test it right now since i removed nearly all of gnome
- With root running poweroff or halt -t now just results in a reboot

So, poweroff does work just not for the root user..
Comment by Gerardo Exequiel Pozzi (djgera) - Thursday, 26 November 2009, 15:05 GMT
Running reboot/poweroff/halt under init levels != 0 and != 6 just invokes shutdown -r or shudown -h -> init 6 or init 0, respectively.

can you see this when do a shutdown?
The system is going down for system halt NOW!
INIT: Switching to runlevel: 0

and this when do a reboot?
The system is going down for reboot NOW!"
INIT: Switching to runlevel: 6
Comment by Mark (markg85) - Thursday, 26 November 2009, 19:29 GMT
poweroff
INIT: Switching to runlevel: 0

reboot
INIT: Switching to runlevel: 6

anything else i can test?
Comment by Gerardo Exequiel Pozzi (djgera) - Friday, 27 November 2009, 00:55 GMT
yes from console:

init 1
(enter your root password)
killall5
dmesg -n 8
umount -a
poweroff -f
Comment by Gerardo Exequiel Pozzi (djgera) - Friday, 27 November 2009, 01:01 GMT
another test: boot with init=/bin/bash (append to kernel command line) and on bash prompt type /sbin/poweroff -f

Comment by Mark (markg85) - Friday, 27 November 2009, 18:44 GMT
odd.. i tried the init 1 till poweroff -f method and that worked however the first boot after that brought me in a ramfs mode.. :S so i completely shut down my pc and it boots just fine now but that was a bit odd.

the init=/sbin/bash method didn't work as i couldn't type anything.. the numlock light would just go on with a keypress and off with a release and that's it.

Now i have another odd issue.. poweroff -f works BUT poweroff (without the -f) just reboots my pc... perhaps this narrowed down the issue?
Comment by Gerardo Exequiel Pozzi (djgera) - Friday, 27 November 2009, 22:39 GMT
weird.

poweroff -f, is for bypass init (stop programs, umount filesystems, etc), so using in bad way...

you have changed your rc.shutdown? because this is the same the command that are executed as last step in init0
/sbin/poweroff -d -f -h -i

and worked for you.
Comment by Mark (markg85) - Friday, 27 November 2009, 23:54 GMT
I personally didn't change anything in rc.shutdown but it might just be possible that one of those graphical boot loaders that i had running for a while touched it.. (plymouth perhaps?)
Could you send me the default for that file?
Comment by Gerardo Exequiel Pozzi (djgera) - Sunday, 29 November 2009, 19:28 GMT
If you never touched rc.shutdown then you have the original, because there is no package that touches this file, except the initscripts that is the owner.
Anyway you have it on pacman cache, so can compare with your current installed file.
Comment by tuxce (tuxce) - Tuesday, 08 December 2009, 23:37 GMT
Check if you have some files in /etc/rc.d/functions.d/
plymouth for example puts a file there and makes my computer (msi wind u100) reboot instead of shutdown, I had to comment the "if" bloc to make shutdown works again.

Loading...