Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#30136 - [linux] 'restart' does not restart the system

Attached to Project: Arch Linux
Opened by Amitav (amitavmohanty01) - Monday, 04 June 2012, 10:47 GMT
Last edited by Tom Gundersen (tomegun) - Tuesday, 02 October 2012, 09:51 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Eric Belanger (Snowman)
Tom Gundersen (tomegun)
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 6
Private No

Details

Description:
When I try to restart my system from the KDE restart button or using restart command or using shutdown -h now command, it works fine till dropping to run level 6, stopping processes. I get a line saying "Restarting system"; but it stays at that and does not restart.

A similar bug is reported in Ubuntu but they have somehow fixed it. My friend using Ubuntu can restart fine.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/833705

Additional info:
* package version(s)
LINUX - 3.3.7-1
upower 0.9.16-1
dbus-core 1.4.20-2
initscripts 2012.05.1-1
* config and/or log files etc.

# /etc/modprobe.d/mei.conf
blacklist mei

# generated by nvidia-installer
blacklist nouveau
options nouveau modeset=0
This task depends upon

Closed by  Tom Gundersen (tomegun)
Tuesday, 02 October 2012, 09:51 GMT
Reason for closing:  Upstream
Additional comments about closing:  kernel bug
Comment by Darshit Shah (darnir) - Tuesday, 05 June 2012, 12:32 GMT
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.
Comment by Amitav (amitavmohanty01) - Tuesday, 05 June 2012, 13:51 GMT
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.
Comment by Amitav (amitavmohanty01) - Saturday, 09 June 2012, 11:14 GMT
There is an upstream bug about this issue.
https://bugzilla.kernel.org/show_bug.cgi?id=42542
Comment by Mort Yao (soimort) - Sunday, 10 June 2012, 10:05 GMT
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.
Comment by Amitav (amitavmohanty01) - Monday, 11 June 2012, 21:37 GMT
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
Comment by Victor Frederico Silva (vfbsilva) - Friday, 15 June 2012, 13:49 GMT
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.
Comment by Amitav (amitavmohanty01) - Friday, 15 June 2012, 14:29 GMT
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.
Comment by Victor Frederico Silva (vfbsilva) - Friday, 15 June 2012, 21:53 GMT
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.
Comment by Amitav (amitavmohanty01) - Saturday, 16 June 2012, 08:00 GMT
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.
Comment by Victor Frederico Silva (vfbsilva) - Saturday, 16 June 2012, 14:12 GMT
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.
Comment by Victor Frederico Silva (vfbsilva) - Saturday, 16 June 2012, 16:14 GMT
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.
Comment by Amitav (amitavmohanty01) - Saturday, 16 June 2012, 18:41 GMT
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.
Comment by Victor Frederico Silva (vfbsilva) - Monday, 18 June 2012, 06:54 GMT
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.
Comment by Victor Frederico Silva (vfbsilva) - Monday, 18 June 2012, 17:39 GMT
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
Comment by Laurent Carlier (lordheavy) - Thursday, 06 September 2012, 11:20 GMT
Is it still an issue ?
Comment by Amitav (amitavmohanty01) - Tuesday, 11 September 2012, 05:55 GMT
I saw the status being changed to "requires testing". What is it that you want to test? Let me know if I can help.
Comment by Tom Gundersen (tomegun) - Tuesday, 02 October 2012, 09:51 GMT
This is a kernel bug, so not much we can do about it downstream. Please follow up at lkml or kernel bugzilla.

Loading...