Bug 1046495
| Summary: | [abrt] WARNING: CPU: 2 PID: 32267 at drivers/net/wireless/iwlwifi/pcie/tx.c:1501 iwl_trans_pcie_send_hcmd+0x575/0x5d0 [iwlwifi]() | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | benjaminfogel | ||||||||
| Component: | kernel | Assignee: | fedora-kernel-wireless-iwl | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 20 | CC: | blakerohde, gansalmon, ilw, itamar, jonathan, jwboyer, kernel-maint, madhu.chinakonda, paulo.fidalgo.pt, willsk | ||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/caae12c16f986f1291f2ce9bd2a01f50e3ce381b | ||||||||||
| Whiteboard: | abrt_hash:48105588baf4faba909bc3ae8ed1fedc54d9ee45 | ||||||||||
| Fixed In Version: | kernel-3.13.7-100.fc19 | Doc Type: | Bug Fix | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2014-03-28 03:15:40 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: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
benjaminfogel
2013-12-25 20:33:07 UTC
Created attachment 841636 [details]
File: dmesg
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those. In my system this bug had disappeared. Closing per above. I just got an identical trace on 3.13.5 Created attachment 872676 [details]
dmesg
Created attachment 872691 [details]
fix
I am still not sure about this patch.
I just wonder why lockdep hasn't complained louder.
Is it enabled in these system?
I do see the bug in the code though...
Can this patch be tested?
(In reply to Emmanuel Grumbach from comment #7) > I just wonder why lockdep hasn't complained louder. > Is it enabled in these system? Lockdep is enabled only on fedora kernel-debug variant, which is not installed by default due to bad performance. > I do see the bug in the code though... > Can this patch be tested? I launched kernel build with the patch here: http://koji.fedoraproject.org/koji/taskinfo?taskID=6617851 William, Paulo, and others, please test it (note it has to finish to compile first). > I launched kernel build with the patch here:
> http://koji.fedoraproject.org/koji/taskinfo?taskID=6617851
>
> William, Paulo, and others, please test it (note it has to finish to compile
> first).
I will certainly do so when I get home, but this has happened about twice in as many months so I doubt I'll see any immediate effect -- but will post again if I encounter any problems.
This problem happens when RFKILL switch is used, hence using it more frequently will help to stress the patch :-) I am pretty sure that this patch should fix the bug - I am just wondering if it doesn't cause a deadlock or something like that. So a few hours of operation should be enough. I'd want this patch to make it to 3.14. (In reply to Emmanuel Grumbach from comment #11) > I am pretty sure that this patch should fix the bug - I am just wondering if > it doesn't cause a deadlock or something like that. > So a few hours of operation should be enough. > I'd want this patch to make it to 3.14. So far so good: after two-three hours of operation with the patched kernel -- which included me spamming the hell out of the rfkill switch -- everything looks fine. (In reply to William from comment #12) > (In reply to Emmanuel Grumbach from comment #11) > > I am pretty sure that this patch should fix the bug - I am just wondering if > > it doesn't cause a deadlock or something like that. > > So a few hours of operation should be enough. > > I'd want this patch to make it to 3.14. > > So far so good: after two-three hours of operation with the patched kernel > -- which included me spamming the hell out of the rfkill switch -- > everything looks fine. great thanks. Patch is on its way upstream. Yep, patch was posted here: http://marc.info/?l=linux-wireless&m=139453882510796&w=2 Josh, please apply it as fix for this bug. Fixed in git. Thanks to all! kernel-3.13.7-200.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/kernel-3.13.7-200.fc20 kernel-3.13.7-100.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/kernel-3.13.7-100.fc19 Package kernel-3.13.7-200.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.13.7-200.fc20' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-4317/kernel-3.13.7-200.fc20 then log in and leave karma (feedback). kernel-3.13.7-200.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. kernel-3.13.7-100.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. |