Bug 1001666
| Summary: | [abrt] WARNING: at drivers/net/wireless/brcm80211/brcmsmac/mac80211_if.c:827 brcms_ops_ampdu_action+0x1b2/0x1c0 [brcmsmac]() | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | bugzilla.ebv | ||||
| Component: | kernel | Assignee: | fedora-kernel-wireless-brcm80211 | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 18 | CC: | arend, bugzilla.ebv, gansalmon, hauke, itamar, jogreene, jonathan, kernel-maint, madhu.chinakonda, marcelo.barbosa, marcosmds | ||||
| Target Milestone: | --- | Flags: | hauke:
needinfo-
|
||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:71276345f5dd39b35ad2277231028ea6db8924df | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-02-05 22:20:12 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
bugzilla.ebv
2013-08-27 13:37:04 UTC
Created attachment 790975 [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 18 kernel bugs. Fedora 18 has now been rebased to 3.11.4-101.fc18. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19. If you experience different issues, please open a new bug report for those. Is this easily repeatable? I checked on upstream, nothing really obvious to address this, but can try a later kernel? Looking at the dmesg it seems like a race condition. mac80211 does a addba, but brcmsmac has not initialized the data structure for that. I noticed in brcms_ops_sta_add(), which is responsible for initializing the data structure, the following comment: /* * minstrel_ht initiates addBA on our behalf by calling * ieee80211_start_tx_ba_session() */ There is no lock taken in brcms_ops_sta_add() during this initialization so mac80211 can freely move on and call brcms_ops_ampdu_action() on interface worker thread. (In reply to Arend van Spriel from comment #4) > Looking at the dmesg it seems like a race condition. mac80211 does a addba, > but brcmsmac has not initialized the data structure for that. > > I noticed in brcms_ops_sta_add(), which is responsible for initializing the > data structure, the following comment: > > /* > * minstrel_ht initiates addBA on our behalf by calling > * ieee80211_start_tx_ba_session() > */ > > There is no lock taken in brcms_ops_sta_add() during this initialization so > mac80211 can freely move on and call brcms_ops_ampdu_action() on interface > worker thread. I'll see about this one. Thanks Arend. *** Bug 1028776 has been marked as a duplicate of this bug. *** This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days |