Bug 700362
Summary: | AR9287 wifi driver stop working after a while | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Uno Engborg <uno> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 15 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, sgruszka |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-04 19:06:44 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: |
Description
Uno Engborg
2011-04-28 08:28:13 UTC
Googling a bit, it seems that it is fix in 2.6.39-rc1 See: http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.39-rc1 commit: d78f4b3e2c4dfb9487624f7157af04ab4260e189 Perhaps this could be backported to 2.6.38 (In reply to comment #1) > Googling a bit, > > it seems that it is fix in 2.6.39-rc1 > > See: http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.39-rc1 > commit: d78f4b3e2c4dfb9487624f7157af04ab4260e189 > > Perhaps this could be backported to 2.6.38 If you look at that commit, you'll see it fixes a bug introduced by commit 86271e460a66003dc1f4cbfd845adafb790b7587 ... and that commit went in 2.6.39-rc1, so it can't be the cause of this problem. Please test compat-wireless-next package from http://people.redhat.com/sgruszka/compact_wireless.html There is patch: commit 1df85ecec36ad5da3f0165760704310d6c03f65f Author: Adrian Chadd <adrian.chadd> Date: Fri May 27 01:08:04 2011 +0800 ath9k: Fix AR9287 calibration which possibly could fix this problem. The commit referenced in comment #3 is included in the 3.0 kernel. F15 is using 2.6.40.x which is just 3.0 renamed. Are you still having this problem on the latest F15 kernel? (In reply to comment #4) > The commit referenced in comment #3 is included in the 3.0 kernel. F15 is > using 2.6.40.x which is just 3.0 renamed. Are you still having this problem on > the latest F15 kernel? Unfortunately, I can't tell. I have no longer access to a machine with that hardware. So if nobody else have any input on this I suggest we close this bug and reopen it again when somebody have a machine to test on, in case the problem still exists in current kernel versions. |