| Summary: | Activation (wlan0/wireless): association took too long, failing activation. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Wendell Baker <wendellcraigbaker> |
| Component: | iwl3945-firmware | Assignee: | Matthias Saou <matthias> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | matthias, wielkipiec |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-02-13 16:32:58 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Wendell Baker
2012-02-19 23:47:09 UTC
I was going to report a problem with WPA-Corporate, but recently WLAN stopped working on any networks. No security/WEP/WPA. Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) NetworkManager x86_64 0.9.4-2.git20120328_2.fc18 Apr 5 00:09:38 mewtwo NetworkManager[529]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Apr 5 00:09:38 mewtwo NetworkManager[529]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Apr 5 00:09:38 mewtwo NetworkManager[529]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0] Apr 5 00:09:38 mewtwo NetworkManager[529]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Apr 5 00:09:38 mewtwo NetworkManager[529]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Apr 5 00:09:38 mewtwo NetworkManager[529]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Apr 5 00:09:38 mewtwo NetworkManager[529]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0] Apr 5 00:09:38 mewtwo NetworkManager[529]: <info> Activation (wlan0/wireless): connection 'weeeee 1' has security, and secrets exist. No new secrets needed. Apr 5 00:09:38 mewtwo NetworkManager[529]: <info> Config: added 'ssid' value 'weeeee' Apr 5 00:09:38 mewtwo NetworkManager[529]: <info> Config: added 'scan_ssid' value '1' Apr 5 00:09:38 mewtwo NetworkManager[529]: <info> Config: added 'key_mgmt' value 'WPA-PSK' Apr 5 00:09:38 mewtwo NetworkManager[529]: <info> Config: added 'psk' value '<omitted>' Apr 5 00:09:38 mewtwo NetworkManager[529]: <info> Config: added 'proto' value 'WPA RSN' Apr 5 00:09:38 mewtwo NetworkManager[529]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Apr 5 00:09:39 mewtwo NetworkManager[529]: <info> Config: set interface ap_scan to 1 Apr 5 00:09:39 mewtwo NetworkManager[529]: <info> (wlan0): supplicant interface state: disconnected -> scanning Apr 5 00:09:42 mewtwo NetworkManager[529]: <info> (wlan0): supplicant interface state: scanning -> authenticating Apr 5 00:09:42 mewtwo NetworkManager[529]: <info> (wlan0): supplicant interface state: authenticating -> associating Apr 5 00:09:42 mewtwo NetworkManager[529]: <info> (wlan0): supplicant interface state: associating -> associated Apr 5 00:09:52 mewtwo NetworkManager[529]: <info> (wlan0): supplicant interface state: associated -> disconnected Apr 5 00:09:53 mewtwo NetworkManager[529]: <info> (wlan0): supplicant interface state: disconnected -> scanning Apr 5 00:09:56 mewtwo NetworkManager[529]: <info> (wlan0): supplicant interface state: scanning -> authenticating Apr 5 00:09:56 mewtwo NetworkManager[529]: <info> (wlan0): supplicant interface state: authenticating -> associating Apr 5 00:09:56 mewtwo NetworkManager[529]: <info> (wlan0): supplicant interface state: associating -> associated Apr 5 00:10:04 mewtwo NetworkManager[529]: <warn> Activation (wlan0/wireless): association took too long. Apr 5 00:10:04 mewtwo NetworkManager[529]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0] Apr 5 00:10:04 mewtwo NetworkManager[529]: <warn> Activation (wlan0/wireless): asking for new secrets Apr 5 00:10:04 mewtwo NetworkManager[529]: <info> (wlan0): supplicant interface state: associated -> disconnected Apr 5 00:10:04 mewtwo NetworkManager[529]: <warn> Couldn't disconnect supplicant interface: This interface is not connected. Apr 5 00:10:09 mewtwo NetworkManager[529]: get_secret_flags: assertion `is_secret_prop (setting, secret_name, error)' failed Randomly, I can see my favorite line: device state change: failed -> disconnected (reason 'none') [120 30 0] This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |