Description of problem:
I have a Dell Latitude D830 with an Intel Wireless 4965 chipset. With kernels 2.6.40-4.fc15 and 188.8.131.52-0.fc15, WLAN reliability and speed are very bad compared to 184.108.40.206-26.rc1.fc15 -- speed according to iwconfig 1-5.5Mbps vs. 9-36Mbps, measured with iperf 1.2~1.6 Mbps vs. 3.3~9.3Mbps, regular dropped connections/reconnects vs. none.
Version-Release number of selected component (if applicable):
kernel-2.6.40-4.fc15.x86_64 <--- bad
kernel-220.127.116.11-0.fc15.x86_64 <--- bad
kernel-18.104.22.168-26.rc1.fc15.x86_64 <--- good
Steps to Reproduce:
1. Boot one of the kernels
2. Use WLAN
Actual results, expected results: see above -- kernels 2.6.40 vs. 2.6.38.
Uses iwlagn driver on 2.6.38, iwl4965 on 2.6.40 kernels.
Another tidbit: this is against a Linksys WRT54GS Router/Access Point (802.11g).
(In reply to comment #0)
> regular dropped connections/reconnects vs. none.
The connection doesn't "drop" here, it kills the access point :)
After a while, when the access point is restarted, I can connect again and after a minute or two, it's killed again and does a restart.
Access point: Speedport W503 V
Laptop: Lenovo x220 i5:
The problem is with:
kernel-22.214.171.124-35.fc15.x86_64 (and before)
This might be a dub of bug 733269.
The workaround from there seem to work here too:
'add the line "options iwlagn 11n_disable=1" in /etc/modprobe.d/modprobe.conf.'
(But I have iwlagn in both cases of kernels).
The new kernel from:
fixes my issues.
(In reply to comment #3)
> This might be a dub of bug 733269.
> The workaround from there seem to work here too:
> 'add the line "options iwlagn 11n_disable=1" in /etc/modprobe.d/modprobe.conf.'
I don't think so, my access point is 802.11g only, 11n_disable shouldn't influence my setup AIUI.
(In reply to comment #3)
Connection speed maxes is 9Mbps (iwconfig)/7Mbps (iperf) with this kernel, the laptop being half a meter from the access point. I'll monitor stability.
NB: I had the 2.6.38 kernel running for a while and noticed hard lockups of the WLAN hardware after a few hours of uptime/use with it as well. I'll attach a file with the lines of /var/log/messages that seem relevant to me.
Created attachment 521033 [details]
/var/log/messages: lines pertaining to wedged WLAN hardware/firmware
Created attachment 521366 [details]
This time, WLAN got wedged on 126.96.36.199-5.fc15.x86_64.
> Sep 1 15:23:11 gibraltar kernel: [34348.077035] iwlagn 0000:0c:00.0: Queue 2 stuck for 2000 ms.
> Sep 1 15:23:11 gibraltar kernel: [34348.077048] iwlagn 0000:0c:00.0: On demand firmware reload
> Sep 1 15:23:12 gibraltar kernel: [34348.086849] iwlagn 0000:0c:00.0: MAC is in
First message indicate that firmare hangs. It happens after about 9 hours, driver do something bad that's crash the firmware. I'm not sure how to track it down sine this happen after so much time, and gathering and analysing 9h debug logs could be annoying.
Perhaps lets try first solve bad performance problem. Please configure rsyslog like described in "Configure syslog to log kernel debug messages" in https://fedoraproject.org/wiki/DebugWireless .
Then reload driver:
modprobe -r iwl4965
echo > /var/log/kernel
modprobe iwl4965 debug=0x47ffffff
Do some traffic on the network which show bad performance and attach /var/log/kernel here. Thanks.
Created attachment 531602 [details]
/var/log/kernel since last reload of iwl4965 module
I just updated to F-16 and encountered this issue once again (I shirked this on F-15 by just using a 2.6.38 kernel). This is /var/log/kernel since the last reload of the module (albeit with debug=65535 as I didn't remember the exact value and couldn't check what you wrote without network access, I hope it's enough info).
BTW, while logging this, yum was downloading packages to be installed with a whopping 12-16kB/sec ;-).
BTW^2, this is happening with kernel-3.1.0-5.fc16.x86_64.
I do not see anything suspicious in logs from comment 9. Can you provide logs as described in comment 8?
Also if you still have .38 kernel installed or possibility to install would be good to provide verbose logs in case things works. I could then compare logs, and possibly catch the difference, which most likely would allow to find reason of that problem.
Created attachment 532761 [details]
/var/log/kernel of 3.1.0-7 with debugging as requested
I'm sorry, but I cannot tell what is wrong based on above logs.
Could you please install working kernel i.e. 2.6.38:
(on F-16 you can do this using using rpm -ivh --force, or you can run F-15 liveCD) and provide the same verbose logs from that kernel?
Then I could compare these two logs and hopefully catch the difference, what should be enough to find fix for that problem. Thanks.