Bug 733269
Summary: | [iwl5300] wireless broken on 11n (F15) | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | tuxor <acc-bugz-redhat> | ||||||||
Component: | kernel | Assignee: | Stanislaw Gruszka <sgruszka> | ||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | high | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 15 | CC: | aquini, gansalmon, itamar, joh, jonathan, kernel-maint, madhu.chinakonda, mishu, sgruszka, tomspur | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | x86_64 | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | 2.6.40.4-5 | Doc Type: | Bug Fix | ||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2011-09-01 11:06:39 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
tuxor
2011-08-25 10:29:57 UTC
All bug 648732 fixes are applied in F-15. So this is a different problem. I don't think it is common. Regarding bug 648732 I was able to reproduce the problem, now all my 11n APs works with iwl5300 and 5100. Please provide me information about your AP vendor and type. I will see if I can get the same AP and hence if I can reproduce problem locally, if not I will ask you for more verbose debug messages. I just tested it one more time and again the same problem: At first NM connects fine, but after a few seconds the connection dies and /var/log/messages has the following log: http://pastebin.com/fCLn5xFs This doesn't occur with 11n_disable=1 for iwlagn. I'm living in a household together with three other persons using the same AP without problems. It's only my "Intel Corporation Ultimate N WiFi Link 5300" that's behaving wrong. We are using a Telekom Speedport W504V WLAN-Router/DSL-Modem with WPA-PSK. Unfortunately, there is no other AP or another OS to check at the moment. These Telecom is quite exotic device, I don't thing some of my friends have it. Ok, please configure rsyslog like described in "Configure syslog to log kernel debug messages" in https://fedoraproject.org/wiki/DebugWireless . Then do the following: modprobe -r iwlagn echo > /var/log/kernel modprobe iwlagn debug=0x47ffffff wait until connection fail. modprobe -r iwlagn and attach /var/log/kernel here. Thanks. Created attachment 520060 [details]
Debug-Output in /var/log/kernel
As Stanislaw Gruszka requested, here is the debug-output when error occurs.
Is your access point still alive, when you are disconnected? I have a W503 V and this kernel kills the access point... After a restart of it, it works for maybe a minute (depends on the load of the wifi) and then it's killed again. Will try the 11n_disable=1 workaround. Well, it doesn't _always_ kill my AP, but in most cases. And yes, after a restart, it works again for a minute and so on, like you describe. We seem to have exactly the same problem, me having a W504V and you having the W503V. So this bug seems to take shape now. Try some new kernel i.e that one: http://koji.fedoraproject.org/koji/buildinfo?buildID=261186 It include fix/workaround discussed in bug 708747 Created attachment 520811 [details] debug-output as per comment #2 (In reply to comment #6) > Well, it doesn't _always_ kill my AP, but in most cases. And yes, after a > restart, it works again for a minute and so on, like you describe. > > We seem to have exactly the same problem, me having a W504V and you having the > W503V. So this bug seems to take shape now. Yes, hopefully it's poosible to resolve it... (In reply to comment #5) > Will try the 11n_disable=1 workaround. Works here too! Attached the debugoutput in my case, hope it helps. (In reply to comment #7) > Try some new kernel i.e that one: > http://koji.fedoraproject.org/koji/buildinfo?buildID=261186 > It include fix/workaround discussed in bug 708747 Works like before 2.6.40. Thanks! 2.6.40.4-5 works for me, too! Thanks! Tried 2.6.40.4-5 and unfortunately the problem persists. I'm on a different card though (4965AGN) which uses a different driver (iwl4965). Attaching dmesg output when 11n is enabled and performance is severely degraded. Disabling 11n with 11n_disable=1 results in good performance. The only difference in dmesg output between the two are the lines: [ 802.507084] iwl4965 0000:03:00.0: Aggregation not enabled for tid 0 because load = 6 [ 815.870043] iwl4965 0000:03:00.0: iwl4965_tx_agg_start on ra = 00:25:9c:ca:7b:bc tid = 0 which appear only when 11n is enabled. Let me know if you think this is a different issue and should be reported as a new bug. Created attachment 521094 [details]
dmesg output when 11n is enabled on iwl4965
(In reply to comment #11) > Tried 2.6.40.4-5 and unfortunately the problem persists. I'm on a different > card though (4965AGN) which uses a different driver (iwl4965). Attaching dmesg > output when 11n is enabled and performance is severely degraded. Disabling 11n > with 11n_disable=1 results in good performance. > > The only difference in dmesg output between the two are the lines: > > [ 802.507084] iwl4965 0000:03:00.0: Aggregation not enabled for tid 0 because > load = 6 > [ 815.870043] iwl4965 0000:03:00.0: iwl4965_tx_agg_start on ra = > 00:25:9c:ca:7b:bc tid = 0 > > which appear only when 11n is enabled. Let me know if you think this is a > different issue and should be reported as a new bug. Sounds like another issue. Could be bug #732592, he has a "Dell Latitude D830 with an Intel Wireless 4965 chipset". (In reply to comment #13) > Sounds like another issue. Yes, we do not set max_tx_aggregation_subframes parameter in 4965 driver, what was issue here. > Could be bug #732592, he has a "Dell Latitude D830 with an Intel Wireless 4965 > chipset". Rather no, because #732592 does not work in G (and N) mode, Johannes have only problems in N mode. I'll prefer separate bug report for Johannes issue. |