Bug 352881
Summary: | iwl3945 does not work after resume | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Julian Sikorski <belegdol> |
Component: | kernel | Assignee: | John W. Linville <linville> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | cebbert, davej, dcbw, linville |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | kernel-2.6.23.1-49.fc8 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-11-12 16:11:41 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Julian Sikorski
2007-10-25 17:49:15 UTC
Now that's peculiar: [root@snowball ~]# lsmod | grep iwl iwl3945 175657 0 mac80211 148433 1 iwl3945 [root@snowball ~]# rmmod iwl3945 [root@snowball ~]# lsmod | grep iwl iwl3945 175657 0 mac80211 148433 1 iwl3945 [root@snowball ~]# It seems that rmmod gives the module some sort of wakeup kick, it starts working without the need for modprobe. I experience exactly the same. Kernel NetworkManager iwl3945 will fail to reassociate without running rmmod first. From /var/log/messages: Nov 9 08:09:39 mobilrechner NetworkManager: <info> Config: added 'group' value 'WEP40 WEP104 TKIP CCMP' Nov 9 08:09:39 mobilrechner NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Nov 9 08:09:39 mobilrechner NetworkManager: <info> (wlan0) Supplicant interface state change: 0 -> 2 Nov 9 08:10:04 mobilrechner NetworkManager: <info> Activation (wlan0/wireless): association took too long, asking for new key. Nov 9 08:10:04 mobilrechner NetworkManager: <info> (wlan0) Supplicant interface state change: 2 -> 0 This was meant to read Kernel: kernel-2.6.23.1-42.fc8 NetworkManager: NetworkManager-0.7.0-0.5.svn3030.fc8 kernel-2.6.23.1-49.fc8 seems to have fixed the issue for me. After resume, NetworkManager reconnects to the AP after around 1 second. I tried 3 resumes so far; I will give feedback if anything goes wrong again. Hmm, it really seems to be fixed with the mentioned kernel. |