Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 395815

Summary: ath5k continuous reconnection and eventually hang the device
Product: Gentoo Linux Reporter: Oschtan <dawnstyle>
Component: [OLD] Core systemAssignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel>
Status: RESOLVED UPSTREAM    
Severity: normal    
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
URL: http://forums.gentoo.org/viewtopic-t-906498.html
See Also: http://bugs.debian.org/611107
https://bugzilla.kernel.org/show_bug.cgi?id=27382
https://bugzilla.redhat.com/show_bug.cgi?id=672778
Whiteboard:
Package list:
Runtime testing required: ---

Description Oschtan 2011-12-23 16:56:28 UTC
http://forums.gentoo.org/viewtopic-t-906498.html

Reproducible: Always

Steps to Reproduce:
Update to kernel, which is not observed problems - 2.6.36-r8
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2011-12-23 17:15:46 UTC
How about the stable sys-kernel/gentoo-sources-3.0.6? That bug report is ancient so I would figure it's been fixed in Linus' tree by now.
Comment 2 Oschtan 2011-12-23 17:22:09 UTC
I tested it on kernel 2.6.39-r3 and 3.1.0. Check availability to 3.0.6. Maybe it does not cause such an effect
Comment 3 Oschtan 2011-12-23 17:50:26 UTC
Kernel 3.0.6: same problem. Already tired of checking out. I do not want to check also on 3.1.5
Comment 4 Oschtan 2011-12-23 18:01:29 UTC
(In reply to comment #1)
> How about the stable sys-kernel/gentoo-sources-3.0.6? That bug report is
> ancient so I would figure it's been fixed in Linus' tree by now.


As for the patch from RedHat. They tried to fix the final error when the device hangs completely. But apparently no one noticed that the device is constantly reconnect before. I would agree with the fact that the cause of Reason = 3/Reason = 7 in another place (not in the kernel), but all the recipes the internet did not give the slightest cure the problem. As soon as the remote back from the tree kernel 2.6.36 and challenges as never happened before. The most interesting is that this mistake many times as observed beginning with the release of kernel 2.6.37, as can be easily seen in the search, for example, Google
Comment 5 Mike Pagano gentoo-dev 2012-03-04 21:25:48 UTC
I understand that repeated testing can be trying. Please take this upstream to http://bugzilla.kernel.org