b43 driver locking up my system?

In the past couple of days my laptop has been locking up on programs that use Internet access such as: email checks, USENET, update checks, IM, IRC, Amarok (when uploading the song data to last.fm), and even when updating the firmware for b43, so on and so fourth. It was because of this I checked /var/log/messages and /var/log/warn to see if I can’t get a clue as to what is causing my system to hang, this is what I found

                       
Aug 30 21:42:45 SE-03 syslog-ng[1986]: last message repeated 2 times                              
Aug 30 21:42:45 SE-03 kernel: printk: 5 messages suppressed.                                      
Aug 30 21:42:45 SE-03 kernel: b43-phy0 ERROR: PHY transmission error                              
Aug 30 21:42:45 SE-03 kernel: b43-phy0 ERROR: PHY transmission error
Aug 30 21:42:54 SE-03 kernel: printk: 4 messages suppressed.
Aug 30 21:42:54 SE-03 kernel: b43-phy0 ERROR: PHY transmission error
Aug 30 21:42:54 SE-03 kernel: b43-phy0 ERROR: PHY transmission error
Aug 30 21:42:57 SE-03 kernel: printk: 59 messages suppressed.
Aug 30 21:42:57 SE-03 kernel: b43-phy0 ERROR: PHY transmission error
Aug 30 21:43:03 SE-03 kernel: printk: 7 messages suppressed.
Aug 30 21:43:03 SE-03 kernel: b43-phy0 ERROR: PHY transmission error
Aug 30 21:43:09 SE-03 kernel: printk: 10 messages suppressed.
Aug 30 21:43:09 SE-03 kernel: b43-phy0 ERROR: PHY transmission error
Aug 30 21:43:14 SE-03 kernel: printk: 5 messages suppressed.
Aug 30 21:43:14 SE-03 kernel: b43-phy0 ERROR: PHY transmission error
Aug 30 21:43:20 SE-03 kernel: printk: 5 messages suppressed.
Aug 30 21:43:20 SE-03 kernel: b43-phy0 ERROR: PHY transmission error
Aug 30 21:43:25 SE-03 kernel: printk: 7 messages suppressed.
Aug 30 21:43:25 SE-03 kernel: b43-phy0 ERROR: PHY transmission error
Aug 30 21:43:30 SE-03 kernel: printk: 3 messages suppressed.
Aug 30 21:43:30 SE-03 kernel: b43-phy0 ERROR: PHY transmission error
Aug 30 21:43:35 SE-03 kernel: printk: 1 messages suppressed.
Aug 30 21:43:35 SE-03 kernel: b43-phy0 ERROR: PHY transmission error
Aug 30 21:43:45 SE-03 kernel: printk: 13 messages suppressed.
Aug 30 21:43:45 SE-03 kernel: b43-phy0 ERROR: PHY transmission error
Aug 30 21:43:45 SE-03 kernel: b43-phy0 ERROR: PHY transmission error
Aug 30 21:43:55 SE-03 kernel: printk: 2 messages suppressed.
Aug 30 21:43:55 SE-03 kernel: b43-phy0 ERROR: PHY transmission error
Aug 30 21:44:07 SE-03 syslog-ng[1986]: last message repeated 2 times
Aug 30 21:44:07 SE-03 kernel: printk: 1 messages suppressed.
Aug 30 21:44:07 SE-03 kernel: b43-phy0 ERROR: PHY transmission error
Aug 30 21:44:07 SE-03 kernel: b43-phy0 ERROR: PHY transmission error
Aug 30 21:44:12 SE-03 kernel: printk: 16 messages suppressed.
Aug 30 21:44:12 SE-03 kernel: b43-phy0 ERROR: PHY transmission error
Aug 30 21:44:17 SE-03 kernel: printk: 1 messages suppressed.
Aug 30 21:44:17 SE-03 kernel: b43-phy0 ERROR: PHY transmission error
Aug 30 21:44:22 SE-03 kernel: printk: 15 messages suppressed.
Aug 30 21:44:22 SE-03 kernel: b43-phy0 ERROR: PHY transmission error

This is the only error happening at the time of the lock up, and as you can see it is constantly happening. Before I managed to get my b43 firmware updated it was also complaining about a missing file and I need to update to version 4, after the update that error seems to have gone away and it seems I have a little more of a stable system but I don’t know how long this will last or even if this is the cause of the problem. What makes me think this is the problem is the fact that the problem is so wide spread but every application has one thing in common internet access threw wireless.

Help?

I am investigating these PHY transmission errors, but they do not lock
up my computer. When too many occur in a short time, the driver will
reset the device, which will cause some delay in data reception, but
the rest of the computer should be responsive.

Larry

So I need to find another cause for the system locking up, it would be nice to know what is also causing the PHY transmission problem. This lock up is weird because everything but the cursor stops responding, I can still move the cursor around and if I place the cursor over a button for a window it will react and light up but when I click it nothing happens even if I give it time, the keypad does not work so I can’t restart X, the Kmenu does not open the only thing I can do is press and hold the power button until the system shuts down.

After updating the b43 firmware and modprobing ssb, which caused another system lock up, my system seems to have stabilized but I still see the PHY transmission errors. Maybe I will have better luck getting the answer to this problem from the authors of the driver?

To whom do you think you have been talking?

We believe it to be a firmware error and we are trying other later
versions to see if it helps.

Larry

Sorry I was unaware of who you are.

I also am seeing this error:
Sep 13 11:09:42 road kernel: b43-phy0 ERROR: PHY transmission error
HP2133 notebook, SUSE 11.0,
02:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11a/b/g [14e4:4312] (rev 02)
Subsystem: Hewlett-Packard Company Device [103c:1370]
Flags: bus master, fast devsel, latency 0, IRQ 24
Memory at fdffc000 (64-bit, non-prefetchable) [size=16]
Capabilities: [40] Power Management version 3
Capabilities: [58] Vendor Specific Information <?>
Capabilities: [e8] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Capabilities: [d0] Express Endpoint, MSI 00
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb

And I am seeing X crash but I have not yet related it to this error msg.[/size]

rwmarch wrote:

>
> I also am seeing this error:
> Sep 13 11:09:42 road kernel: b43-phy0 ERROR: PHY transmission error
> HP2133 notebook, SUSE 11.0,
> 02:00.0 Network controller [0280]: Broadcom Corporation BCM4312
> 802.11a/b/g [14e4:4312] (rev 02)
> Subsystem: Hewlett-Packard Company Device [103c:1370]
> Flags: bus master, fast devsel, latency 0, IRQ 24
> Memory at fdffc000 (64-bit, non-prefetchable) [size=16]
> Capabilities: [40] Power Management version 3
> Capabilities: [58] Vendor Specific Information <?>
> Capabilities: [e8] Message Signalled Interrupts: Mask- 64bit+
> Queue=0/0 Enable-
> Capabilities: [d0] Express Endpoint, MSI 00
> Kernel driver in use: b43-pci-bridge
> Kernel modules: ssb
>
> And I am seeing X crash but I have not yet related it to this error
> msg.
>
>
Is X crashing when you are using wireless, or is it just random you may want to look into that.

“We must plan for freedom, and not only for security, if for no other reason than only freedom can make security more secure.” Karl Popper
[/size]

rwmarch wrote:
> I also am seeing this error:
> Sep 13 11:09:42 road kernel: b43-phy0 ERROR: PHY transmission error

That ERROR is not causing any problems. On some systems, there are
storms of these errors - enough to cause the driver to reset the
interface and restarts. Even those do not crash the system, and merely
slow communications.

You need to look elsewhere for your crashes/lockups. Does the machine
ever recover? When it does, does anything show up in the dmesg output?

You might also try running top in a terminal and look for activity
when this condition occurs. Strangely enough, when I was writing this
reply, my System Monitor showed the machine to be roughly 50% busy.
The top output showed the top 2 entries to be:

3138 root 20 0 119m 44m 5584 S 53 1.5 43:04.80 Xorg
4350 finger 20 0 1842m 1.7g 28m R 44 60.6 30:04.95 ld-linux.so.2

Fortunately, I have a dual-processor system, thus I have spare
capacity. I certainly imagine that if I had only one CPU, response
would be really sluggish. Killing the ld-linux.so process made the
system work right again.

Larry

This isn’t the case for me, my system doesn’t recover I have to hard kill it (holding the power button until it turns off) and when a ran top and waited until my system locked up my system (also a dual core system) was only at 12% busy and one of the things that was making it busy was “b43”.

Strange. On my system, b43 doesn’t show up at all in the top page.

Is anything logged (dmesg output) other than that one PHY transmission
error?

Larry

Without a recent crash here is the other things logged about my wireless device

ssb: Sonics Silicon Backplane found on PCI device 0000:02:00.0
b43-phy0: Broadcom 4311 WLAN found
phy0: Selected rate control algorithm ‘pid’
Broadcom 43xx driver loaded Features: PMLR, Firmware-ID: FW13 ]
input: b43-phy0 as /devices/virtual/input/input11
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
Registered led device: b43-phy0::radio
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:17:3f:44:89:8c
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:17:3f:44:89:8c
wlan0: RX authentication from 00:17:3f:44:89:8c (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:17:3f:44:89:8c
wlan0: authentication frame received from 00:17:3f:44:89:8c, but not in authenticate state - ignored
wlan0: RX ReassocResp from 00:17:3f:44:89:8c (capab=0x401 status=0 aid=3)
wlan0: associated
wlan0: switched to short barker preamble (BSSID=00:17:3f:44:89:8c)
wlan0: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0
wlan0: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0
wlan0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30
wlan0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15
martian source 255.255.255.255 from 192.168.2.1, on dev wlan0
ll header: ff:ff:ff:ff:ff:ff:00:17:3f:44:89:8c:08:00
martian source 255.255.255.255 from 192.168.2.1, on dev wlan0
ll header: ff:ff:ff:ff:ff:ff:00:17:3f:44:89:8c:08:00
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.2.3 DST=224.0.0.251 LEN=245 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=225
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.2.3 DST=224.0.0.251 LEN=466 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=446
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.2.3 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.2.3 DST=224.0.0.251 LEN=466 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=446
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.2.3 DST=224.0.0.251 LEN=466 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=446
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=00:19:7e:d3:49:17:00:17:3f:44:89:8c:08:00 SRC=192.168.2.1 DST=192.168.2.3 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=40529 PROTO=UDP SPT=18934 DPT=137 LEN=58
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
Registered led device: b43-phy0::radio
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.2.3 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=00:19:7e:d3:49:17:00:17:3f:44:89:8c:08:00 SRC=192.168.2.1 DST=192.168.2.3 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=40641 PROTO=UDP SPT=18970 DPT=137 LEN=58
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=00:19:7e:d3:49:17:00:17:3f:44:89:8c:08:00 SRC=192.168.2.1 DST=192.168.2.3 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=40644 PROTO=UDP SPT=18970 DPT=137 LEN=58
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=00:19:7e:d3:49:17:00:17:3f:44:89:8c:08:00 SRC=192.168.2.1 DST=192.168.2.3 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=40650 PROTO=UDP SPT=18973 DPT=137 LEN=58
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=00:19:7e:d3:49:17:00:17:3f:44:89:8c:08:00 SRC=192.168.2.1 DST=192.168.2.3 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=40653 PROTO=UDP SPT=18973 DPT=137 LEN=58
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC=00:19:7e:d3:49:17:00:17:3f:44:89:8c:08:00 SRC=192.168.2.1 DST=192.168.2.3 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=40655 PROTO=UDP SPT=18977 DPT=137 LEN=58

on top of the PHY transmission this keeps repeating, the first half looks like it is starting up/connecting the bottom half I have no clue what is going on. I’ll keep an eye on dmesg and if something changes or new shows up, mainly when my system does lock up, I’ll post my findings.

All of those SWF2 messages are coming from the firewall. The b43
messages are all normal.

Larry

Larry Finger wrote:

> All of those SWF2 messages are coming from the firewall. The b43
> messages are all normal.
>
> Larry

Thanks for clearing that up
“We must plan for freedom, and not only for security, if for no other reason than only freedom can make security more secure.” Karl Popper

Mine isnt locking up the system but i am having multiple error logs from b43-phy0.

reads
linux-2z9v kernal: b43-phy0 ERROR: PHY transmission error.

getting this message about every 30 seconds

running 11.0 kde4
gateway turion 64
ati radeon 200m
i think its a broadcom 4318.

Ideas on what to do? ALso, whats the best way to check what broadcom I have. I am still not sure if its the 4318. Had to go to the gateway specs website.

thx

jtopliff wrote:
> Mine isnt locking up the system but i am having multiple error logs from
> b43-phy0.
>
> reads
> linux-2z9v kernal: b43-phy0 ERROR: PHY transmission error.
>
> getting this message about every 30 seconds
>
> running 11.0 kde4
> gateway turion 64
> ati radeon 200m
> i think its a broadcom 4318.
>
> Ideas on what to do? ALso, whats the best way to check what broadcom I
> have. I am still not sure if its the 4318. Had to go to the gateway
> specs website.
>
> thx
>
>
You can tell what your version is with a ‘/sbin/lspci’ command.

We think the PHY transmission errors come from a firmware error. They started
showing up with the latest firmware that comes from 4.150.10.5. There are
reports that firmware from 4.80.53.0 is OK. In any case, these errors are not fatal.

Larry