Cannot reboot?

ponder

Honorary Master
Joined
Jan 22, 2005
Messages
98,654
Reaction score
31,317
Location
Niflheimr
Sorry mate: never seen that before in my life ... I have had situations that certain processes 'stops' the shutdown, but I have never had a problem with init 6.

I would probably start with manually stopping all services, one after the other, and attempting init 6 every now and then: Also killing any processes that I can. Hopefully you'll find one service that doesn't want to stop, and you will now your culprit.
 
Does it not reboot as you do the command as root or as normal user?

In other words, does it reboot fine under a different user?
 
In the olden days this was usually an ACPI issue and you needed to add a few lines to your lilo/grub to handle this. I have not run into this problem in years, so try this:
https://bbs.archlinux.org/viewtopic.php?id=74451

3rd post from the bottom.

It could also be gfx drivers, but I doubt it - https://bbs.archlinux.org/viewtopic.php?id=34211

Some older info:
I had this exact problem on some old IBM x86-64 Netburst Xeon architecture systems running Red Hat 3, 4 and 5.

When HT was enabled in the BIOS, init 6 would fail to reboot. With HT disabled, automatic reboot would work fine. I don't know if the problem is fixed now, but for a couple of years (while the servers performance was still relevant), it continued to be a problem.
Check for mounted network dependencies - are there any NFS, CIFS shares or iSCSI, nbd, AoE targets initiated?
I tried passing "reboot=bios" as kernel option. This solved the reboot hanging problem. My system is no more hanging now.

Thanks for all those who helped. :)
http://serverfault.com/questions/126571/system-hangs-while-rebooting-on-debian
 

Just did a fresh install of Arch in a VM, edited rc.conf a bit, added a few packages and a user, and edited /etc/sudoers according to that wiki. Then I tried "sudo reboot" as the user and the VM rebooted. ("sudo shutdown -h now" also works)

I'm wondering if you added your user to the "power" group. It probably shouldn't make a difference with sudo, but you never know.
 
Last edited:
I'm wondering if you added your user to the "power" group. It probably shouldn't make a difference with sudo, but you never know.

Those obvious things have been taken care of, I'm part of the power group, my sudoers file has been configured to perform these functions without requiring a password. I have dbus daemon running and even the dbus restart strings don't work, upower is installed. This happens irrespective of me being logged in as a normal user or as root.
 
This looks like a kernel bug (already filed) as I'm not the only one with the problem by the looks of things.
 
Is it a bug in the current kernel or something that came with previous kernels also?

If just current, then just downgrade.

Install "downgrader" from aur and simply downgrade the kernel.
 
If you're using an Nvidia driver it may be as simple as just reinstalling teh driver from a safe boot up at grub.
 
Is it a bug in the current kernel or something that came with previous kernels also?

If just current, then just downgrade.

Install "downgrader" from aur and simply downgrade the kernel.

It was present in the previous kernel as well. Since my initial net install there has been one kernel upgrade on my system.
 
Top
Sign up to the MyBroadband newsletter
X