Steinar H. Gunderson wrote: > Package: network-manager > Version: 0.6.4-8+b1 > Severity: important > > Whenever I suspend my D420 (by closing the lid) and resume, > network-manager dies completely; it just shows the standard icon of a > computer with an "X", with the menu only showing a greyed-out cable > network option. To get my network working again, I need to restart > network-manager via the init script (previously dbus script). > > This does not happen if I let it stay in suspend only a few seconds (so > hal thinks that the suspend failed), nor does it happen if I suspend > with "s2ram" manually (so hal doesn't "see" the suspend) -- the network > comes up almost immediately after I resume. IOW, there's something wrong > with network-manager's suspend handling. /var/log/daemon.log reads: > > Apr 27 13:24:28 localhost NetworkManager: <information>^IWaking up from > sleep. > Apr 27 13:24:28 localhost NetworkManager: <information>^IDeactivating device > eth2. > Apr 27 13:24:28 localhost NetworkManager: <WARNING>^I > nm_device_802_11_wireless_set_essid (): error setting ESSID to '' for device > eth2: Resource temporarily unavailable > Apr 27 13:24:28 localhost NetworkManager: <WARNING>^I > nm_device_802_11_wireless_set_wep_enc_key (): error setting key for device > eth2: Resource temporarily unavailable > Apr 27 13:24:28 localhost NetworkManager: <WARNING>^I > nm_device_802_11_wireless_get_mode (): error getting card mode on eth2: > Resource temporarily unavailable > Apr 27 13:24:28 localhost NetworkManager: <WARNING>^I > nm_device_802_11_wireless_set_mode (): error setting card eth2 to > Infrastructure mode: Resource temporarily unavailable > Apr 27 13:24:28 localhost NetworkManager: <information>^IDeactivating device > eth0. > Apr 27 13:24:29 localhost NetworkManager: <information>^Ieth0: Device is > fully-supported using driver 'tg3'. > Apr 27 13:24:29 localhost NetworkManager: <information>^Inm_device_init(): > waiting for device's worker thread to start > Apr 27 13:24:29 localhost NetworkManager: <information>^Inm_device_init(): > device's worker thread started, continuing. > Apr 27 13:24:29 localhost NetworkManager: <information>^INow managing wired > Ethernet (802.3) device 'eth0'. > Apr 27 13:24:29 localhost NetworkManager: <information>^IDeactivating device > eth0. > > After that, there's only debug information about various USB devices being > added before I restart it. > > For the reference, the WLAN card is an ipw3945.
IIRC, the ipw3945 uses a separate regulatory daemon. Have you checked if this daemon is still running after hibernate/resume? Maybe the suspend scripts you are using are stopping this daemon. Btw, which one do you use, acpi-support, hibernate or powersaved? Check the file /usr/lib/hal/scripts/linux/hal-system-power-hibernate-linux (You can also run it manually as root). I doubt it's a bug in NM, rather in the driver. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
