Bug 457197
Summary: | 4965AGN wifi not working on T61 in specific situation | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Eduards <edzis> | ||||
Component: | NetworkManager | Assignee: | Dan Williams <dcbw> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 9 | CC: | arxs, dcbw, matthewbstanton, wtogami | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2009-06-11 19:33:17 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: | |||||||
Attachments: |
|
Description
Eduards
2008-07-30 08:09:35 UTC
I'll gathered full logs after resume from hibernate in env. where wireless doesn't work. I'll attach them to this bug. And more details on the issue (to make things more clear): Messages in logs appear only when I'm at workplace, that is - env. where that hidden SID network exists. As long as computer starts wireless messages in logs appear at a rate of about one per second and wireless is non functional. I can't connect at all. When booting everywhere else log has no such messages and wireless is functional. It seems that settings are remembered (I see saved network in NM) and when wireless sees that hidden network it somehow wants to disconnect from it like every second. NM restart doesn't help, rmmod and modprobe too. Rebooting (as I wrote earlier) doesn't help either. And yes, I tried wireless-compat thing too, nothing helps. There should be bug somewhere but the thing is I can't figure out where. Created attachment 313073 [details]
wpa_supplicant log file in env. where wifi is not working with -dd switch enabled
Promised log files.
wpa_supplicant binary does give the same output every second:
ioctl[SIOCSIWENCODEEXT]: No such file or directory
Dmesg has this (nothing really important I think):
Jul 31 09:31:10 tpevil NetworkManager: <info> Waking up...
Jul 31 09:31:10 tpevil NetworkManager: <info> (eth0): now managed
Jul 31 09:31:10 tpevil NetworkManager: <info> (eth0): device state change: 1
-> 2
Jul 31 09:31:10 tpevil NetworkManager: <info> (eth0): bringing up device.
Jul 31 09:31:10 tpevil kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 31 09:31:10 tpevil NetworkManager: <info> (eth0): preparing device.
Jul 31 09:31:10 tpevil NetworkManager: <info> (eth0): deactivating device.
Jul 31 09:31:10 tpevil NetworkManager: <info> (wlan0): now managed
Jul 31 09:31:10 tpevil NetworkManager: <info> (wlan0): device state change: 1
-> 2
Jul 31 09:31:10 tpevil NetworkManager: <info> (wlan0): bringing up device.
Jul 31 09:31:10 tpevil kernel: ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17
(level, low) -> IRQ 17
Jul 31 09:31:10 tpevil acpid: client connected from 2542[0:0]
Jul 31 09:31:11 tpevil kernel: Registered led device: iwl-phy0:radio
Jul 31 09:31:11 tpevil kernel: Registered led device: iwl-phy0:assoc
Jul 31 09:31:11 tpevil kernel: Registered led device: iwl-phy0:RX
Jul 31 09:31:11 tpevil kernel: Registered led device: iwl-phy0:TX
Jul 31 09:31:11 tpevil acpid: client connected from 2542[0:0]
Jul 31 09:31:11 tpevil kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jul 31 09:31:11 tpevil NetworkManager: <info> (wlan0): preparing device.
Jul 31 09:31:11 tpevil NetworkManager: <info> (wlan0): deactivating device.
Jul 31 09:31:11 tpevil kernel: hub 1-0:1.0: unable to enumerate USB device on
port 1
Jul 31 09:31:11 tpevil NetworkManager: <info> (wlan0): device state change: 2
-> 3
Jul 31 09:31:11 tpevil NetworkManager: <info> (wlan0): supplicant interface
state change: 1 -> 2.
Is this still an issue with latest kernel, NM, and supplicant in F9 updates? ie, 2.6.26.5-fc9 and later, wpa_supplicant 0.6.4 and later, and NM svn4022.4 and later? Hi, sorry for late answer, somehow I felt this bug will be abandoned. So, this is still an issue, but now there are different conditions. Now I'm on ArchLinux (I had numerous problems with wifi, hibernate on F8 and F9 didn't suite me at all). I'm building NM and wpa_supplicant myself now (to get latest features and hope bug is fixed). Software: 1. kernel - 2.6.26-5 (ArchLinux one) (standard wifi is failing after 20 mins so...) I use compat-wireless from September 14, later releases just fails to load (I assume that this is because of new iwlagn thing), when compiling it gives out some agn_config warning (additional note: I can't use 2.6.27, coz my usb stops functioning after two(2) hibernates) 2. wpa_supplicant - 0.6.5 3. NM - it was around commit 4200 from SVN back then (when I tested this again) It sort of worked for first time, so I thought bug disapeared, but once I use my ethernet and plug out cable, issue appears again - log shows this: Oct 30 09:50:15 tpevil wlan0: authenticated Oct 30 09:50:15 tpevil wlan0: associate with AP 00:xx:xx:xx:a6:f1 Oct 30 09:50:15 tpevil wlan0: associate with AP 00:xx:xx:xx:a6:f1 Oct 30 09:50:15 tpevil wlan0: deauthenticated Oct 30 09:50:16 tpevil wlan0: authenticate with AP 00:xx:xx:xx:a6:f1 Oct 30 09:50:16 tpevil wlan0: authenticated Oct 30 09:50:16 tpevil wlan0: associate with AP 00:xx:xx:xx:a6:f1 Oct 30 09:50:16 tpevil wlan0: associate with AP 00:xx:xx:xx:a6:f1 Oct 30 09:50:16 tpevil wlan0: deauthenticated This goes on and on... No networks are found in between. When I go to other office that has the same hidden sid, it connects fine and is working nice. So it seems the auth/deauth thing is coming from that one particular access point. I don't know how to track this better, if You have any suggestions, please tell me. When newest kernel will arrive, be it 2.6.27-xx or 2.6.28 I'll try to use that one hoping fingerprint reader will work and wireless too :) regards Kirurgs Hi, 2.6.27.5 came out and I tested this bug. It's still there. This time no wireless-compat, just default modules. This doesn't seem to be NM bug, it seems it's wireless driver bug. To test this You should: 1. connect to wireless network 2. plug in network cable, disconnect from wireless 3. plug out network cable and here it goes. In case You see this is not anyhow related to NM, can You please assign this bug to approriate team (wifi team?) Thanx and regards Kirurgs I can confirm this bug on fc10 with intel 4965AGN, fully updated as of Dec 17, 2008. I can see networks after hibernation, but I cannot connect to them. Works after a computer restart. Do latest kernels work better? Like 2.6.27.12 from Fedora updates. This bug is highly driver specific (not connecting after resume), and if recent kernels have the problem too, it may be good to test out software encryption rather than hardware accelerated encryption on the Intel wifi cards. Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. 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 '9'. 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 9'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 9 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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 Hi! Feel free to close the bug, I'm not using Fedora anyway, so I can't assist to further diagnostics. I might use F11 soon, if bug will happen there, I'll fill a new bug. regards Kirurgs |