| Summary: | [abrt] kernel: WARNING: at drivers/net/wireless/ath/ath9k/hw.c:2242 ath9k_hw_gettsf64+0x75/0x79 [ath9k_hw](): TAINTED ---------W | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Misha Shnurapet <shnurapet> |
| Component: | kernel | Assignee: | John W. Linville <linville> |
| 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, mcgrof |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Unspecified | ||
| Whiteboard: | abrt_hash:180e6aca23110ddbafc74d01eff8460fa235f107 | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-01-09 19:17:05 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Misha Shnurapet
2011-07-03 05:12:23 UTC
How often does this happen? The trigger for the warning looks like it should be rather rare. Of course, it should also be rather harmless -- so maybe we shouldn't bother warning about it either... It's always reproducible. I can't agree it's harmless because it is followed (or preceded) by a crash of the kernel, also no connection can be established. I'll explain. I replaced the old BCM4312 card on my Dell mini 1011 (10v) with AR9280 and trying to use it normally. What I do when I get this is trying to connect to my home wifi network protected by a 63 or 64-character WPA2 passphrase. Upon this, Linux crashes and this warning is caught by ABRT. *** Bug 716585 has been marked as a duplicate of this bug. *** Luis, do you have any idea why this TSF read would timeout? If not, can you convince some of your Atheros brethren to take a look at this and add themselves to the Cc list? :-) Does this problem persist with 2.6.40 (or later) kernels? Closing due to lack of response... |