Moderator: Closing
]]>For my machine, disable runtime-pm module in laptop-mode-tools fixed it, no need to disable ethernet.
And it doesn't seems very useful anyway, or I might didn't understood correctly what runtime-pm does.
Is anyone else having the problem still? My Toshiba Satellite A660 will fail to shut down about 1/2 of the time. I don't use laptop-mode. I have looked through /var/log and everything looks normal.
I'm having this issue on 2.6.39, disabling laptop-mode tools from rc.conf didn't work for me. This happens on every shutdown. Strange but I don't recall this happening right after updating the kernel. I checked my pacman log and the last major system update was the nvidia drivers. I downgraded but that didn't work. This is on a HP Pavilion 2415nr.
]]>Same problem on a Toshiba Satellite L455.
:-O aaaahh i have the same probleem!!...
]]>I only got the problem when upgraded to .38
Can't shutdown or reboot.
It unloads modules, kills all processes and turns off the monitor but never actually powers down.
And it gets stuck in the same place with restart.
Same problem for me. But I do not think that this is related to the problem reported in this thread. I do not have laptop-mode installed and had no issues wit 2.6.37 kernels.
]]>-rw-r--r-- 1 root root 1.7K Aug 5 2010 auto-hibernate.conf
-rw-r--r-- 1 root root 803 Aug 5 2010 ac97-powersave.conf
-rw-r--r-- 1 root root 858 Aug 6 2010 wireless-power.conf
-rw-r--r-- 1 root root 914 Aug 6 2010 wireless-ipw-power.conf
-rw-r--r-- 1 root root 963 Aug 6 2010 wireless-iwl-power.conf
-rw-r--r-- 1 root root 1.7K Feb 18 22:41 usb-autosuspend.conf
-rw-r--r-- 1 root root 2.4K Feb 19 12:22 ethernet.conf
-rw-r--r-- 1 root root 953 Mar 4 12:51 bluetooth.conf
-rw-r--r-- 1 root root 929 Mar 4 17:49 runtime-pm.conf
I've disabled ethernet.conf and runtime-pm.conf
]]># ac97-powersave
# cpufreq
# dpms-standby
# eee-superhe
# ethernet
# exec-commands
# hal-polling
# hdparm
# intel-hda-powersave
# intel-sata-powermgmt
# runtime-pm
# sched-mc-power-savings
# sched-smt-power-savings
# terminal-blanking
# usb-autosuspend
# wireless-ipw-power
# wireless-iwl-power
# wireless-power
And see which one/ones triggers the problem? this might be a good approach (a tedious one, but a good one nevertheless). I dont have the time right now to test this, anyone with available time for 18 reboots?
]]>