Bug 1061836
| Summary: | regression BCM4331 wireless, b43-phy0 ERROR PHY transmission error | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Chris Murphy <bugzilla> |
| Component: | kernel | Assignee: | fedora-kernel-wireless-b43 |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 22 | CC: | bqueiros, gansalmon, itamar, jonathan, kernel-maint, larry.finger, madhu.chinakonda |
| Target Milestone: | --- | Flags: | jforbes:
needinfo?
|
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-23 17:22:50 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Chris Murphy
2014-02-05 17:50:53 UTC
Mostly copied from the bugzilla.kernel.org entry. Thanks for the complete posting. I do not have a 14e4:4331 device, but I have posted on the wireless and b43 mailing lists to see if anyone else has seen the problem. My 1434:4315 does not have this problem, which is a an indication that changes in the rest of the kernel did not cause this problem. One difficulty is that I do not understand the "PHY transmission error" messages. They are some kind of error indication from the firmware that the TX descriptor is faulty, but the cause is not clear. A further complication is that we have no source for that firmware. I reviewed the changes to both bcma and b43 between 3.13 and 3.14-rc1. None of the bcma changes is likely to be the problem. The only change for b43 that cannot be ruled out is one that fixed a definite bug. It is possible, however, that fixing that bug exposed another that is now triggering on your device. Is it possible for you to obtain the full mainline git repo and bisect the problem? If that is not possible, perhaps the Fedora devs could build a special kernel with commit 64e5acb reverted. That kernel would test the one commit that I question. I'm also facing this problem, i have a Macbook from 2007 and have Fedora 20 x86_64 with kernel 3.15.6-200.fc20.x86_64. After installing the firmware the wireless interface is up but it doesn't scan for wireless networks, therefore it's useless. all i see in the messages are: [ 692.143318] b43-phy1 warning: LEDs: Unknown behaviour 0x5B [ 692.143321] b43-phy1 warning: LEDs: Unknown behaviour 0x5B [ 692.143323] b43-phy1 warning: LEDs: Unknown behaviour 0x46 [ 692.143324] b43-phy1 warning: LEDs: Unknown behaviour 0x3B [ 692.312094] b43-phy1: Loading firmware version 666.2 (2011-02-23 01:15:07) [ 692.317155] b43-phy1 ERROR: radio post init timeout [ 692.360190] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22 *********** 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 22 kernel bugs. Fedora 22 has now been rebased to 4.2.3-200.fc22. 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 23, and are still experiencing this issue, please change the version to Fedora 23. If you experience different issues, please open a new bug report for those. *********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. |