Red Hat Bugzilla – Bug 411451
No Access Points Visible After Resume With iwl3945
Last modified: 2008-04-10 17:50:09 EDT
After resume, no access points appear in NetworkManager drop down. (root@hobbes)[~] # rpm -qa | grep NetworkManager NetworkManager-0.7.0-0.6.6.svn3109.fc8 NetworkManager-glib-0.7.0-0.6.6.svn3109.fc8 NetworkManager-gnome-0.7.0-0.6.6.svn3109.fc8 NetworkManager-vpnc-0.7.0-0.4.svn3030.fc8 NetworkManager-0.7.0-0.6.6.svn3109.fc8 NetworkManager-glib-0.7.0-0.6.6.svn3109.fc8 Some relevant log entries: Dec 4 22:38:06 hobbes NetworkManager: <WARN> nm_system_device_get_system_config(): Network configuration for device 'wlan0' was invalid (non-DHCP configuration, but no IP address specified. Will use DHCP instead. Dec 4 22:38:06 hobbes NetworkManager: <info> wlan0: Device is fully-supported using driver 'iwl3945'. Dec 4 22:38:06 hobbes NetworkManager: <info> (wlan0): exporting device as /org/freedesktop/NetworkManager/Device/3 Dec 4 22:38:06 hobbes NetworkManager: <info> Now managing wireless (802.11) device 'wlan0'. Dec 4 22:38:06 hobbes NetworkManager: <info> Bringing up device wlan0 Dec 4 22:38:06 hobbes kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready Dec 4 22:38:06 hobbes NetworkManager: <info> Deactivating device wlan0. I ran into a blog post where the author suggested this workaround: sudo /sbin/service NetworkManager restart sudo /sbin/service NetworkManager stop sleep 12 sudo /sbin/service NetworkManager start This works sometimes, maybe once or twice, after which it either stops doing anything, or I run into other suspend/resume problems and can't use the laptop. (but those are other bugs) How reproducible: Usually happens within one or two suspend/resume cycles. Additional info: Smolt hardware profile available here: http://www.smolts.org/show?UUID=a9265d1e-d331-43f6-873c-c542a0283de0 Please feel free to request any other info, this is everything I could think of so far.
When this happens, can you try doing the following (as root) without restarting NetworkManager? /sbin/iwlist wlan0 scan and see if networks start showing up. Thanks!
This happened to me last night. iwlist scan did indeed see my desired access point, but NetworkManager remained blissfully unaware. Tried rmmod iwl3945; modprobe iwl3945; iwlist scan again saw my AP, but NetworkManager remained unaware. Restarting both iwl3945 and NetworkManager made it work again. NetworkManager-glib-0.7.0-0.6.6.svn3109.fc8 NetworkManager-gnome-0.7.0-0.6.6.svn3109.fc8 NetworkManager-debuginfo-0.7.0-0.6.6.svn3109.fc8 NetworkManager-glib-devel-0.7.0-0.6.6.svn3109.fc8 NetworkManager-devel-0.7.0-0.6.6.svn3109.fc8 NetworkManager-vpnc-debuginfo-0.7.0-0.6.3.svn3109.fc8 NetworkManager-0.7.0-0.6.6.svn3109.fc8 NetworkManager-vpnc-0.7.0-0.6.3.svn3109.fc8 kernel-2.6.23.9-77.fc8.x86_64
Trying to replicate this tonight and it took me a good 8 to 10 cycles before I had wireless problems on resume, in this case: (root@hobbes)[~] # /sbin/iwlist wlan0 scan wlan0 Failed to read scan data : Resource temporarily unavailable In this case however my workaround from earlier did not work. I was unable to get wireless back at all. Tried another 4 or 5 cycles and unable to get the problem to re-occur. No idea why it's working better today than yesterday, no package upgrades have been done.
The "Failed to read scan data" thing is certainly a driver bug; I've gotten it on 4965 quite often after poking the rfkill switch too much; haven't been able to debug it further than that. You might be able to set up a modprobe option to turn on debugging information and see what the driver thinks its doing. See if you can rmmod the module and modprobe it again and see if that fixes things right after resume. If it does, it's certainly a driver issue.
This might be worth closing, I've been using the laptop heavily lately and the wireless networks almost always appear on resume. (may have happened once or twice but I simply cannot reproduce it reliably anymore)
What's your kernel version, just for kicks?