Arch Linux

I am using Linux 3.3.7-1 with LXDE and XFCE and cannot replicate the issue. I have rebooted from the WM, used the reboot command in an emulator, and manually set init to 6 and it worked in all cases.

The issue is specific to Dell Latitude E6520. It is mentioned in the Ubuntu bug; but I guess I forgot to mention here. My bad.

There is an upstream bug about this issue.
https://bugzilla.kernel.org/show_bug.cgi?id=42542

For my Dell Latitude E6520, Linux 3.3.7-1 works just fine.
But after upgrading to Linux 3.3.8-1 this issue replicates (both in GNOME 3 and console). I can neither poweroff nor reboot.

With kernel parameter "reboot=pci",the Dell Latitude system reboots fine. Ubuntu maintains a list of such one-off cases. That is why it reboots fine out of the box. The upstream ticket says that it can be solved using kernel parameters. So, should individual distributions care of this at distribution level? Let me know if I can put it somewhere in some wiki and I shall edit that to add the solution. For now, I am detailing the issue and solution at http://intosimple.blogspot.com/2012/06/reboot-on-dell-latitude-e6520-with-arch.html

I'm having the same issue with an Athlon Desktop. More people have also reported this, here is the link on the forums regarding what we are facing:
https://bbs.archlinux.org/viewtopic.php?id=143113&p=3
http://mailman.archlinux.org/pipermail/arch-general/2012-June/027156.html

I will try the kernel parameter and see what happens.

Check the upstream bug I mentioned. The kernel developers are working with Dell to understand the issue better. It would be interesting to see if the kernel parameters I mentioned works for you. Even if it does not I would encourage you to try other kernel parameters.

Do I add all those parameters editing menu.lst? Can I pass them on my active session? I ask cause I'm at work and cant test it but people on the mailing lists are also suffering from this issue.

I don't know the way to pass those parameters in an active session. I editted menu.lst only. Just add "reboot=pci" to the kernel line and try. Refer to the blog link I mentioned above for an example.

I did pass the parameter on boot line still did not have the expected effect. Also upgrading to the last kernel released yesterday broken the system to apoint where I have no network, no xserver, nothing. I could not even paste the logs I will chrott from a live cd today and post more info.

I did pass the parameter on boot line still did not have the expected effect. Also upgrading to the last kernel released yesterday broken the system to apoint where I have no network, no xserver, nothing. I could not even paste the logs I will chrott from a live cd today and post more info.

I am not sure whether the kernel parameters I mentioned will work for you. As far as I have read, those work for specific versions of Dell laptops. Thats why I encourage you to find other parameters that you can try for reboot.

arti74 wrote:

What I've noticed yet - htop shows 100% CPU usage on that command:
/bin/mount -o realtime /dev/sda4 /mnt/usbhd-sda4 - I can't kill it, shutdown or reboot can't kill it either.
Interesting thing is, that I don't have sda4 partition at all. My fstab:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>

devpts /dev/pts devpts defaults 0 0
/dev/sda2 / ext4 defaults 0 1
/dev/sda6 /home ext4 defaults 0 1
/dev/sdb1 /mnt/FA auto defaults,nosuid,nodev,uhelper=udisks,uid=1000,gid=100,dmask=0077,fmask=0177 0 0
/dev/sda3 /var reiserfs defaults 0 1
shm /dev/shm tmpfs nodev,nosuid 0 0

uname -r
3.4.2-2-ARCH

I have the same problem so now I know why I cant shutdown, thou I also cannot kill it.

A potential solution was posted here. I'm not at home now can someone please try this https://bbs.archlinux.org/viewtopic.php?pid=1118102#p1118102 ?

Regards,
vfbsilva

Is it still an issue ?

I saw the status being changed to "requires testing". What is it that you want to test? Let me know if I can help.

This is a kernel bug, so not much we can do about it downstream. Please follow up at lkml or kernel bugzilla.