Bug 979870
Summary: | [abrt] BUG: unable to handle kernel NULL pointer dereference at 00000014 | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Markus <unclemarcus91> | ||||
Component: | kernel | Assignee: | fedora-kernel-wireless-brcm80211 | ||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 18 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, unclemarcus91 | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Unspecified | ||||||
Whiteboard: | abrt_hash:d188a3ff342e92aa7e88978b0c7e044985eb3b97 | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2013-11-27 16:19:15 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
Markus
2013-07-01 04:21:21 UTC
Created attachment 767214 [details]
File: dmesg
The log is full of: [ 7836.167582] brcmsmac bcma0:0: brcms_c_ampdu_dotxstatus_complete: ampdu tx phy error (0x10) [ 7836.168670] brcmsmac bcma0:0: phyerr 0x10, rate 0xa [ 7836.168684] brcmsmac bcma0:0: brcms_c_ampdu_dotxstatus_complete: ampdu tx phy error (0x10) [ 7836.268674] brcmsmac bcma0:0: phyerr 0x10, rate 0x6e [ 7836.268701] brcmsmac bcma0:0: brcms_c_ampdu_dotxstatus_complete: ampdu tx phy error (0x10) [ 7836.269299] brcmsmac bcma0:0: phyerr 0x10, rate 0x6e [ 7836.269312] brcmsmac bcma0:0: brcms_c_ampdu_dotxstatus_complete: ampdu tx phy error (0x10) [ 7836.269903] brcmsmac bcma0:0: phyerr 0x10, rate 0x6e [ 7836.269917] brcmsmac bcma0:0: brcms_c_ampdu_dotxstatus_complete: ampdu tx phy error (0x10) [ 7838.069969] brcmsmac bcma0:0: phyerr 0x10, rate 0x37 [ 7838.069997] brcmsmac bcma0:0: brcms_c_ampdu_dotxstatus_complete: ampdu tx phy error (0x10) [ 7838.070352] brcmsmac bcma0:0: phyerr 0x10, rate 0x37 [ 7838.070366] brcmsmac bcma0:0: brcms_c_ampdu_dotxstatus_complete: ampdu tx phy error (0x10) [ 7838.070702] brcmsmac bcma0:0: phyerr 0x10, rate 0x37 [ 7838.070710] brcmsmac bcma0:0: brcms_c_ampdu_dotxstatus_complete: ampdu tx phy error (0x10) [ 7838.667825] brcmsmac bcma0:0: phyerr 0x1, rate 0x14 [ 7838.667834] brcmsmac bcma0:0: brcms_c_ampdu_dotxstatus_complete: ampdu tx phy error (0x1) [ 7838.667985] brcmsmac bcma0:0: phyerr 0x1, rate 0x14 [ 7838.667989] brcmsmac bcma0:0: brcms_c_ampdu_dotxstatus_complete: ampdu tx phy error (0x1) [ 7838.668134] brcmsmac bcma0:0: phyerr 0x1, rate 0x14 [ 7838.668138] brcmsmac bcma0:0: brcms_c_ampdu_dotxstatus_complete: ampdu tx phy error (0x1) [ 7839.078964] brcmsmac bcma0:0: phyerr 0x10, rate 0x14 I'm guessing that is resulting in memory corruption of some kind. *********** 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. *********** 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. It has been over a month since we asked you to test the 3.11 kernel updates and let us know if your issue has been resolved or is still a problem. When this happened, the bug was set to needinfo. Because the needinfo is still set, we assume either this is no longer a problem, or you cannot provide additional information to help us resolve the issue. As a result we are closing with insufficient data. If this is still a problem, we apologize, feel free to reopen the bug and provide more information so that we can work towards a resolution If you experience different issues, please open a new bug report for those. |