Bug 892599
| Summary: | [abrt]: WARNING: at net/mac80211/driver-ops.h:12 ieee80211_do_stop+0x62e/0x670 [mac80211]() | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Sam Tygier <samtygier> | ||||||
| Component: | kernel | Assignee: | Stanislaw Gruszka <sgruszka> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 18 | CC: | 0601422, apcomptec, atenrok, cpanceac, deusshc, gansalmon, itamar, johannes, jonathan, jwboyer, kernel-maint, madhu.chinakonda, michael, sgruszka, simonlca, temp-2009-09-09, twegener, zbechir | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:d5b5562ad8747424661e0a241cb641ddb149ae04 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-03-17 01:04:55 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
Sam Tygier
2013-01-07 11:21:56 UTC
Waking from sleep then closing inkscape Package: kernel Architecture: i686 OS Release: Fedora release 18 (Spherical Cow) It occured before I suspend my laptop... Package: kernel Architecture: i686 OS Release: Fedora release 18 (Spherical Cow) I guess suspend/resume and rfkill somehow conflict. Yes, looks like a mac80211/cfg80211 bug, but I'm not sure it's really high priority for me personally to fix it ... the notebook was suspended. at resume (wake up) this error occured Package: kernel Architecture: i686 OS Release: Fedora release 18 (Spherical Cow) bug 868175 doesn't seem like a duplicate Logged into Cinnamon desktop after powering on the computer. Package: kernel OS Release: Fedora release 18 (Spherical Cow) Created attachment 709071 [details]
mac80211_fixes_for_ieee80211_do_stop_while_suspend_v3.9.patch
Proposed fix , 3.9 version.
Created attachment 709072 [details]
mac80211_fixes_for_ieee80211_do_stop_while_suspend_v3.8.patch
Proposed fix, 3.8 version.
Josh, please apply above patch as fix for this bug. I posted patch here: http://marc.info/?l=linux-wireless&m=136302126224040&w=2 since, it functionality depends on cfg80211_mac80211_disconnect_on_suspend patch (bug 856863), it is also not CCed stable. Applied on all branches with the respective patches. Thanks! This failed to build on f19/f20. There was a missing closing bracket in the newly added code. The 3.8 version of the patch seems fine. Fixed up. Just an FYI. kernel-3.8.3-101.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/kernel-3.8.3-101.fc17 kernel-3.8.3-201.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/kernel-3.8.3-201.fc18 Package kernel-3.8.3-201.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.8.3-201.fc18' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-3893/kernel-3.8.3-201.fc18 then log in and leave karma (feedback). kernel-3.8.3-201.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. kernel-3.8.3-103.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. The problem seems to persist on 3.9.6-200.fc18.x86_64 Unfortunately ABRT refuses to post anything to a closed bug, what should I do to have it re-opened? Please open a new bug report. |