Yuval Hager wrote: > Hi, > > I am having the following situation: > System starts fine, b43 module loaded (firmware installed instructions), and > wireless works fine. After I start X, I get: > b43-phy0: Radio hardware status changed to DISABLED > wlan0: No ProbeResp from current AP 00:22:3f:18:89:5e - assume out of range > > and wireless just stops. All future attempts to start it (rmmod/modprobe) > fails. > > See below the workflow, let me know if there is any info missing, or > something > you think I should try to debug this issue. > I'll be yhager on #bcm-users as well. --snip--
> After running X: > --------------- > > b43-phy0: Radio hardware status changed to DISABLED > wlan0: No ProbeResp from current AP 00:22:3f:18:89:5e - assume out of range Normally, this message means that your radio-enable switch has been turned off. The driver cannot control this switch - it can only read the state. In your case, it looks to me as if something has taken your ssb device off-line. We are no longer getting useful info from the registers, but it is as if the reads are returning all ones. --snip-- > b43-pci-bridge 0000:02:00.0: PCI INT A -> GSI 24 (level, low) -> IRQ 24 > b43-pci-bridge 0000:02:00.0: setting latency timer to 64 > Bluetooth: Core ver 2.13 > NET: Registered protocol family 31 > Bluetooth: HCI device and connection manager initialized > Bluetooth: HCI socket layer initialized > Bluetooth: HCI USB driver ver 2.10 > usbcore: registered new interface driver hci_usb > ssb: Sonics Silicon Backplane found on PCI device 0000:02:00.0 > Real Time Clock Driver v1.12ac > HDA Intel 0000:80:01.0: power state changed by ACPI to D0 > HDA Intel 0000:80:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 > HDA Intel 0000:80:01.0: setting latency timer to 64 > HDA Intel 0000:80:01.0: PCI: Disallowing DAC for device > Marking TSC unstable due to TSC halts in idle > b43-phy0: Broadcom 4311 WLAN found > Clocksource tsc unstable (delta = -172616486 ns) > phy0: Selected rate control algorithm 'pid' > Broadcom 43xx driver loaded [ Features: PMLR, Firmware-ID: FW13 ] > EXT3 FS on sda3, internal journal > Unable to find swap-space signature > tg3: eth0: Link is up at 100 Mbps, full duplex. > tg3: eth0: Flow control is on for TX and on for RX. > input: b43-phy0 as /class/input/input8 > firmware: requesting b43/ucode13.fw > firmware: requesting b43/b0g0initvals13.fw > b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) > b43-pci-bridge 0000:02:00.0: PCI: Disallowing DAC for device > b43-phy0: DMA mask fallback from 64-bit to 32-bit > Registered led device: b43-phy0::tx > Registered led device: b43-phy0::rx > Registered led device: b43-phy0::radio > wlan0: authenticate with AP 00:22:3f:18:89:5e > wlan0: authenticate with AP 00:22:3f:18:89:5e > wlan0: authenticated > wlan0: associate with AP 00:22:3f:18:89:5e > wlan0: RX AssocResp from 00:22:3f:18:89:5e (capab=0x401 status=0 aid=2) > wlan0: associated > wlan0: authenticate with AP 00:22:3f:18:89:5e > wlan0: authenticated > wlan0: associate with AP 00:22:3f:18:89:5e > wlan0: RX ReassocResp from 00:22:3f:18:89:5e (capab=0x401 status=0 aid=2) > wlan0: associated At this point, all is normal and you are connected. Below here, the entire ssb/b43 subsystem has been compromised. In particular, the code that issues the warning on an unknown backplane revision has been executed previously without a problem. Suddenly the returned value of the appropriate register has 0xF in the most significant position instead of 0x6 or 0x7 that was previously found. That is why I think that the read is returning all ones. > evdev.c(EVIOCGBIT): Suspicious buffer size 511, limiting output to 64 bytes. > See http://userweb.kernel.org/~dtor/eviocgbit-bug.html > b43-phy0: Radio hardware status changed to DISABLED > wlan0: No ProbeResp from current AP 00:22:3f:18:89:5e - assume out of range > b43-phy0 ERROR: DMA RX reset timed out > b43-phy0 ERROR: DMA TX reset timed out > b43-phy0 ERROR: DMA TX reset timed out > b43-phy0 ERROR: DMA TX reset timed out > b43-phy0 ERROR: DMA TX reset timed out > b43-phy0 ERROR: DMA TX reset timed out > input: b43-phy0 as /class/input/input9 > ssb: Backplane Revision 0xF0000000 > ------------[ cut here ]------------ > WARNING: at drivers/ssb/main.c:1042 ssb_tmslow_reject_bitmask+0x5e/0x68 [ssb] > () Unfortunately, I have no idea what part of X might be causing this. Perhaps Michael might have a suggestion. Is this a new machine, or has this problem just started? Can you rule out a hardware problem? Perhaps the power supply is flaky. Larry _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
