Red Hat Bugzilla – Bug 448180
[ath5k] Bad connectivity due to regression in outgoing data transfer
Last modified: 2008-05-28 03:30:37 EDT
Description of problem:
For about 2 weeks now, the ath5k driver does not provide acceptable
network connectivity. Latencies are very high, often one has to
trigger the reload of a web page a couple of times to hit the 'right
moment' when data transfer happens. The same for retrieving files
with wget. It often takes several attempts to get the download started.
Once it has started, the download rate reaches normal values.
The worst for me is a completely broken SSH functionality. After
connecting to my lab from home, the session gets usually stuck while
I am typing some command. This already happens after simply hitting
the <return> key several times. Likewise, uploading even small files
via 'scp' is also impossible. the transfer will stall immediately,
something that does not happen when retrieving a file.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Connect to some host via SSH.
2. Type a couple of characters.
Session gets stuck. It does not respond to user input anymore.
I/O via SSH proceeds without interruption.
- WLAN device is a D-Link DWL-G510 Rev. B4 sporting the supported
- Networking works nicely after installing the madwifi driver.
- AP authentication is done via WEP.
- A possibly related thread on the ath5k-devel list:
There is a clear regression from kernel 126.96.36.199-18.fc9.x86_64 to
188.8.131.52-30.fc9.x86_64. Here are the module srcversions for both
| 184.108.40.206-18.fc9.x86_64 220.127.116.11-30.fc9.x86_64
ath5k | 18908C2E600D9B437533B8C 5A711CFF69D9C2D6F93EE16
mac80211 | 0EB6E0DB88CA57CF73FF929 51709970CD733D92F93CD45
cfg80211 | F8516B9136CFABD233613B9 2F73EEBB2DE4F1D785951D4
The regression has been pinned down further to kernel 18.104.22.168-26.fc9
and later ones. From the changelog:
* Mon May 19 2008 John W. Linville <firstname.lastname@example.org> 22.214.171.124-26
- Re-sync wireless bits w/ current upstream
Apart from the issues describes in the original report, I do also
observe intermittent crashes when connecting to the SSH server.
In a first time, I thought this was related to the new glibc-2.8.90
but for kernels < 126.96.36.199-26.fc9, they simply do not occur. Here
is an example of what I get from dmesg after ssh has returned
"segmentation fault" to the shell:
ssh: segfault at 3 ip f063a9 sp 7fff0f00a260 error 4 in
*** Bug 447752 has been marked as a duplicate of this bug. ***
I see the same problems, but I don't think it's ath5k related, as I see the
problems with p54 driver as well.
I think it happened between 2.6.26-rc2 and 2.6.26-rc3 (in this case both
mainline kernels from Linus).
No improvement for kernel-2.6.26-0.33.rc4.fc10.x86_64.
Fixed in kernel 2.6.26-0.37.rc4.fc10.x86_64 with module versions
ath5k : 4ABA5AC1C9F2345308D07B0