[Solved]Weird shutdown problem

asjimene · 2012-02-15 20:48:19

Starting at least today, maybe yesterday my laptop has had a weird shutdown problem

Sometimes (maybe every other shutdown) when I click shutdown the screen immediately turns off and the computer almost looks like it is of, but it isn't. The fan continues running and the Bluetooth indicator light stays on. From there the computer is frozen, i have to hold the power button down in order for it to actually turn off.

Computer info:
Dell XPS M1330- 32bit
Nvidia Graphics card
updated yesturday evening

Here are some of the programs that Updated yesterday and today that I think may be causing the problem
nvidia & nvidia-utils 295.20-1
hdparm
glibc?

relevent log:

Feb 15 13:24:04 localhost shutdown[1958]: shutting down for system halt
Feb 15 13:24:04 localhost spideroak_inotify[1775]: Parent process gone: stopping
Feb 15 13:24:05 localhost spideroak_inotify[1775]: Program terminates normally
Feb 15 13:24:05 localhost init: Switching to runlevel: 0
Feb 15 13:24:06 localhost avahi-daemon[1247]: Got SIGTERM, quitting.
Feb 15 13:24:06 localhost avahi-daemon[1247]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 10.142.23.8.
Feb 15 13:24:06 localhost avahi-daemon[1247]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.208.97.79.
Feb 15 13:24:06 localhost avahi-daemon[1247]: avahi-daemon 0.6.30 exiting.
Feb 15 13:24:07 localhost NetworkManager[1250]: <info> caught signal 15, shutting down normally.
Feb 15 13:24:07 localhost NetworkManager[1250]: <warn> quit request received, terminating...
Feb 15 13:24:07 localhost NetworkManager[1250]: <info> (wlan0): now unmanaged
Feb 15 13:24:07 localhost NetworkManager[1250]: <info> (wlan0): device state change: activated -> unmanaged (reason 'removed') [100 10 36]
Feb 15 13:24:07 localhost NetworkManager[1250]: <info> (wlan0): deactivating device (reason 'removed') [36]
Feb 15 13:24:07 localhost dhcpcd[1400]: received SIGTERM, stopping
Feb 15 13:24:07 localhost dhcpcd[1400]: wlan0: removing interface
Feb 15 13:24:07 localhost bluetoothd[1206]: Terminating
Feb 15 13:24:07 localhost bluetoothd[1206]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSource
Feb 15 13:24:07 localhost bluetoothd[1206]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/HFPAG
Feb 15 20:24:07 localhost rtkit-daemon[1464]: Exiting cleanly.
Feb 15 20:24:07 localhost rtkit-daemon[1464]: Demoting known real-time threads.
Feb 15 20:24:07 localhost rtkit-daemon[1464]: Successfully demoted thread 1578 of process 1578 (/usr/bin/pulseaudio).
Feb 15 20:24:07 localhost rtkit-daemon[1464]: Demoted 1 threads.
Feb 15 20:24:07 localhost rtkit-daemon[1464]: Exiting watchdog thread.
Feb 15 20:24:07 localhost rtkit-daemon[1464]: Exiting canary thread.
Feb 15 13:24:07 localhost NetworkManager[1250]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 1400
Feb 15 13:24:07 localhost NetworkManager[1250]: <info> (wlan0): cleaning up...
Feb 15 13:24:07 localhost NetworkManager[1250]: <info> (wlan0): taking down device.
Feb 15 13:24:07 localhost kernel: [  374.846083] wlan0: deauthenticating from 00:0e:38:62:6b:82 by local choice (reason=3)
Feb 15 13:24:07 localhost bluetoothd[1206]: Stopping hci0 event socket
Feb 15 13:24:07 localhost bluetoothd[1206]: Stopping SDP server
Feb 15 13:24:07 localhost bluetoothd[1206]: Exit
Feb 15 13:24:07 localhost kernel: [  374.853586] cfg80211: Calling CRDA for country: US
Feb 15 13:24:07 localhost NetworkManager[1250]: <info> exiting (success)
Feb 15 13:24:07 localhost laptop-mode: Laptop mode 
Feb 15 13:24:07 localhost laptop-mode: disabled, not active
Feb 15 13:24:07 localhost laptop-mode: failed - udev not active?
Feb 15 13:24:07 localhost laptop-mode: failed - udev not active?
Feb 15 13:24:07 localhost laptop-mode: failed - udev not active?
Feb 15 13:24:07 localhost laptop-mode: failed - udev not active?
Feb 15 13:24:08 localhost acpid: exiting
Feb 15 13:24:08 localhost syslog-ng[674]: syslog-ng shutting down; version='3.3.4'
Feb 15 13:27:20 localhost kernel: [    0.000000] Initializing cgroup subsys cpuset
Feb 15 13:27:20 localhost kernel: [    0.000000] Initializing cgroup subsys cpu
Feb 15 13:27:20 localhost kernel: [    0.000000] Linux version 3.2.5-1-ARCH (tobias@T-POWA-LX) (gcc version 4.6.2 20120120 (prerelease) (GCC) ) #1 SMP PREEMPT Tue Feb 7 08:46:10 UTC 2012

I have no idea what could be causing this, so I'm wondering if anyone else is experiencing the problem.

[edit]
After reading some of the other posts where people were having problems, I took laptop-mode out of my rc.conf, but that did not remedy the problem.

[edit]
Ok i thought it was solved but it is most definitely not,I have determined that it is not a shutdoen problem but a freezing problem. I tried to go to tty1 yesturday and it froze. so it must freeze when it switches to another tty when it shuts down, ill try to replace fgetty with agetty and see if that fixes it.

Last edited by asjimene (2012-02-18 00:17:44)

vwyodajl · 2012-02-15 22:02:20

I have had nvdia related shutdown issues but on a different laptop. Mine sometimes will show a red screen or just hang at the black screen with or with out a cursor. I have managed to work around it by adding this to my rc.local.shutdown

#!/bin/bash
#
# /etc/rc.local.shutdown: Local shutdown script.
#
ifconfig eth0 down
ifconfig wlan0 down
pgrep -P `pidof openbox` | xargs kill -s SIGTERM
sleep 5

Not sure if the problems are related but this may help shed some light on the issue you are having. You can also always include debug info you want to get in the scripts in /etc/rc.*shutdown

HTH

asjimene · 2012-02-15 22:54:40

Thanks,
I tried adding

ip link set eth0 down
ip link set wlan0 down

to my rc.local.shutdown(since i guess ifconfig is depreciated and not on my install) and I get the same behavior.

vwyodajl · 2012-02-16 00:15:48

Thanks for posting what you did I had forgotten ifconfig had been depreciated. Did that work for you though and are able to shutdown?

asjimene · 2012-02-16 02:19:20

No, it didn't work. I'll try some other things if it becomes too troublesome. Hopefully an update will fix it soon. Thanks for the help.

Last edited by asjimene (2012-02-16 02:27:00)

asjimene · 2012-02-16 15:54:53

Ok, I fixed it, I had to change my NIC settings in the BIOS from "enabled w/ PXE" to just "enabled" so I basically turned of LAN boot which another thread pointed out

asjimene · 2012-02-18 00:17:19

So i ended up rolling back the nvidia driver to 290.10 and the issue was resolved.

Arch Linux

#1 2012-02-15 20:48:19

[Solved]Weird shutdown problem

#2 2012-02-15 22:02:20

Re: [Solved]Weird shutdown problem

#3 2012-02-15 22:54:40

Re: [Solved]Weird shutdown problem

#4 2012-02-16 00:15:48

Re: [Solved]Weird shutdown problem

#5 2012-02-16 02:19:20

Re: [Solved]Weird shutdown problem

#6 2012-02-16 15:54:53

Re: [Solved]Weird shutdown problem

#7 2012-02-18 00:17:19

Re: [Solved]Weird shutdown problem

Board footer