Description of problem: On my T60 NetworkManager is sometimes "dead" after resuming from suspend-to-RAM. I first thought this was related to systemd, but I've now seen in at least once after the rollback to upstart. After resume I see: - WLAN is disabked (LED is off) - nm-applet menu "Enable Networking" is not selected (not grayed-out though) - selecting "Enable Networking" does *NOT* re-activate networking - "service NetworkManager restart" brings network back to life: # service NetworkManager restart Stopping NetworkManager daemon: [ OK ] Setting network parameters... [ OK ] Starting NetworkManager daemon: [ OK ] Version-Release number of selected component (if applicable): NetworkManager-0.8.1-6.git20100831.fc14.i686 NetworkManager-glib-0.8.1-6.git20100831.fc14.i686 NetworkManager-gnome-0.8.1-6.git20100831.fc14.i686 NetworkManager-vpnc-0.8.1-1.fc14.i686 pm-utils-1.3.1-1.fc14.i686 upower-0.9.5-7.fc14.i686 upstart-0.6.5-8.fc14.i686 upstart-sysvinit-0.6.5-8.fc14.i686 Linux l3f1199 2.6.35.4-28.fc14.i686 #1 SMP Wed Sep 15 02:03:44 UTC 2010 i686 i686 i386 GNU/Linux 02:00.0 Ethernet controller [0200]: Intel Corporation 82573L Gigabit Ethernet Controller [8086:109a] 03:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection [8086:4227] (rev 02) # lsmod | fgrep -e iwl -e 802 -e e100 iwl3945 100464 0 iwlcore 180323 1 iwl3945 mac80211 200317 2 iwl3945,iwlcore cfg80211 113436 3 iwl3945,iwlcore,mac80211 e1000e 162874 0 rfkill 14576 3 cfg80211,bluetooth,thinkpad_acpi I'm using nm-applet with the KDE desktop. These are the only network related messages in /var/log/messages at resume time: Sep 22 07:33:25 l3f1199 kernel: pciehp 0000:00:1c.0:pcie04: Device 0000:02:00.0 already exists at 0000:02:00, cannot hot-add Sep 22 07:33:25 l3f1199 kernel: pciehp 0000:00:1c.0:pcie04: Cannot add device at 0000:02:00 Sep 22 07:33:25 l3f1199 kernel: e1000e 0000:02:00.0: Disabling ASPM L1
It just happened again. According to "nmcli" NM is asleep! # nmcli nm; nmcli dev RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running asleep enabled enabled enabled enabled DEVICE TYPE STATE eth0 802-3-ethernet unmanaged wlan0 802-11-wireless unmanaged # service NetworkManager restart Stopping NetworkManager daemon: [ OK ] Setting network parameters... [ OK ] Starting NetworkManager daemon: [ OK ] # nmcli nm; nmcli dev RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running connecting enabled enabled enabled enabled DEVICE TYPE STATE eth0 802-3-ethernet unavailable wlan0 802-11-wireless connecting (configuring) (after WLAN got connected again) # nmcli nm; nmcli dev RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running connected enabled enabled enabled enabled DEVICE TYPE STATE eth0 802-3-ethernet unavailable wlan0 802-11-wireless connected I guess NM missed the wakep events from upower?
When this next happens, can you attach /var/log/messages for me? Thanks!
Created attachment 449465 [details] /var/log/messages excerpt Excerpt from /var/log/messages from the last time NM was asleep.
Created attachment 450412 [details] /var/log/messages excerpt (another one) It just happened again. Previously the laptop was connected to my home WLAN and now I resumed at work when NM decided to stay "asleep". kernel-2.6.35.4-28.fc14.i686 NetworkManager-0.8.1-6.git20100831.fc14.i686 NetworkManager-glib-0.8.1-6.git20100831.fc14.i686 NetworkManager-gnome-0.8.1-6.git20100831.fc14.i686 NetworkManager-vpnc-0.8.1-1.fc14.i686 pm-utils-1.3.1-1.fc14.i686 udev-161-2.fc14.i686 upower-0.9.5-7.fc14.i686
*** This bug has been marked as a duplicate of bug 638640 ***