Modify

Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#4598 closed defect (fixed)

Intermittent WiFi (PHY transmission error) after an hour or so of uptime

Reported by: anonymous Owned by: developers
Priority: normal Milestone: Bugs Paradise
Component: kernel Version:
Keywords: b43 phy error mac80211 Cc:

Description

Upgraded my WRT54GSv1.1 from White Russian to Kamikaze 8.09RC2
connected via ethernet cable to reconfigure WiFi, all went fine, very impressed.

Then after an hour or so of uptime, I started noticing bouts of intermittent access over WiFi, pings to the router itself would fail for about 10 seconds, then work for one or two seconds, then fail again.

I managed to SSH onto the router in one of the good periods and get a dmesg from it, which shows some PHY errors, not sure if this is a known issue with b43?

b43-phy0 debug: Updated beacon template at 0x468
b43-phy0 debug: Updated beacon template at 0x68
b43-phy0 debug: Updated beacon template at 0x468
b43-phy0 debug: Updated beacon template at 0x68
b43-phy0 debug: Disabling hardware based encryption for keyidx: 1, mac: 00:00:00:00:00:00
b43-phy0 debug: Using hardware based encryption for keyidx: 1, mac: 00:00:00:00:00:00
b43-phy0 debug: Disabling hardware based encryption for keyidx: 0, mac: 00:16:ea:5e:d1:90
b43-phy0 debug: Set beacon interval to 100
b43-phy0 debug: Updated beacon template at 0x468
b43-phy0 ERROR: PHY transmission error
b43-phy0 ERROR: PHY transmission error
b43-phy0 debug: Set beacon interval to 100
b43-phy0 debug: Updated beacon template at 0x68
b43-phy0 debug: Set beacon interval to 100
b43-phy0 debug: Updated beacon template at 0x468
b43-phy0 ERROR: PHY transmission error
b43-phy0 ERROR: PHY transmission error
b43-phy0 debug: Set beacon interval to 100
b43-phy0 debug: Updated beacon template at 0x68
b43-phy0 ERROR: PHY transmission error
b43-phy0 debug: Set beacon interval to 100
b43-phy0 ERROR: PHY transmission error
b43-phy0 debug: Updated beacon template at 0x468
b43-phy0 ERROR: PHY transmission error
b43-phy0 debug: Set beacon interval to 100
b43-phy0 debug: Updated beacon template at 0x68
b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac: 00:16:ea:5e:d1:90
b43-phy0 ERROR: PHY transmission error
b43-phy0 debug: Disabling hardware based encryption for keyidx: 0, mac: 00:16:ea:5e:d1:90
b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac: 00:16:ea:5e:d1:90
b43-phy0 ERROR: PHY transmission error
b43-phy0 ERROR: PHY transmission error
b43-phy0 debug: Disabling hardware based encryption for keyidx: 0, mac: 00:16:ea:5e:d1:90
b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac: 00:16:ea:5e:d1:90
b43-phy0 ERROR: PHY transmission error
b43-phy0 ERROR: PHY transmission error
b43-phy0 debug: Disabling hardware based encryption for keyidx: 0, mac: 00:16:ea:5e:d1:90
b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac: 00:16:ea:5e:d1:90
b43-phy0 ERROR: PHY transmission error
b43-phy0 ERROR: PHY transmission error
b43-phy0 ERROR: PHY transmission error
b43-phy0 debug: Disabling hardware based encryption for keyidx: 0, mac: 00:16:ea:5e:d1:90
b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac: 00:16:ea:5e:d1:90
b43-phy0 ERROR: PHY transmission error
b43-phy0 ERROR: PHY transmission error
b43-phy0 debug: Disabling hardware based encryption for keyidx: 0, mac: 00:16:ea:5e:d1:90
b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac: 00:16:ea:5e:d1:90
b43-phy0 ERROR: PHY transmission error
b43-phy0 ERROR: PHY transmission error

Attachments (0)

Change History (10)

comment:1 Changed 9 years ago by openwrt@…

Almost exactly the same issue here. I did too migrate from WR to Kamikaze 8.09 RC2.

What is more - I've shifted from WEP to WPA2. I did not install the full hostapd package since there's no enough space on my WRT54GL v1.1 for the libopenssl package.

comment:2 follow-up: Changed 9 years ago by jow

  • Keywords b43 phy error mac80211 added
  • Milestone changed from Kamikaze 8.09 RC2 to Kamikaze Bugs Paradize

This is a known issue with b43. Transition to a newer kernel and updated driver is unlikely to be finished in time for the 8.09 release. However, there is still support for the proprietary driver and kernel 2.4 . You should consider brcm-2.4 for reliable wifi support.

comment:3 in reply to: ↑ 2 Changed 9 years ago by anonymous

Replying to jow:

This is a known issue with b43.

I knew there had been problems with the b43 driver, suppose I was hoping they were fixed already, as suggested I'll drop back to a 2.4 kernel (but stick with Kamikaze rather than drop all the way back to White Russian) before I do that are there any trunk builds worth trying first?

comment:4 Changed 9 years ago by openwrt@…

That did the trick - thanks for the info.

comment:5 Changed 9 years ago by sasha_max

Hi All,

I am also experiencing the same issue with Kamikadze 8.09 final with 2.6 kernel on LINKSYS WRT54GL.
Looks like I found a workaround: I made the following script and put to crontab to run every minute:

#!/bin/sh
if (dmesg|egrep "b43-phy.*encryption for keyidx"|tail -1|grep "Disabling hardware based encryption for keyidx");
then
        echo B43 wireless encryption error detected. Performing repair.

        echo Disabling wireless interface...
        wifi down

        echo Removing B43 module from the kernel...
        rmmod b43

        echo Reloading B43 module...
        insmod b43

        echo Re-enabling wireless interface...
        wifi

        echo Done.
fi;

For me, this script helps to recover automatically. So, each time the problem happens, the script reloads b43 module and my wireless clients reconnect automatically.

comment:6 Changed 9 years ago by florian

  • Resolution set to fixed
  • Status changed from new to closed

This should be fixed with the recent updates of compat-wireless.

comment:7 Changed 9 years ago by francis.lacoste@…

I have the same issue here (LinkSys WRT54GL with Kamikaze 8.09, r14511, kernel 2.6.25.17).

All my packages are up to date as of today and I don't see the compat-wireless package you are talking about? Should I downgrade to the 2.4 kernel?

comment:8 Changed 9 years ago by info@…

I still seems to have the symptoms described above on my WRT54GS v4.0 running Kamikaze 8.09. The crontab hack seemed to work reasonable well, but it still tends to die on me a few times a day.

I have copied (the old?) firmware images (dated 19/Apr/2008) of at http: (slash)(slash) www (dot omattos (dot) com (slash) broadcom (slash) \[1\] into my device and after a reboot it seems to preform much more stable (no crashed experienced yet).

As the firmware had quite a few differences, makes we wonder which firmware is being used in the image as I could not find a easy hint in the subversion repository.

\[1\] Bloody spam filter workaround, but where to create a account to avoid using this dirty quirks?

comment:9 Changed 9 years ago by Francis J. Lacoste <francis.lacoste@…>

I've tried these other firmwares, but I get the same problems. Should I rename the b43legagy to b43?

Any images we can upgrade to solve this problem? Because I put the script in place, but it still very annoying. Skype calls just drop even with this in place. So it basically means the wireless isn't useable.

I've tried downgrading to 2.4, but WPA wans't working at all :-/

comment:10 Changed 9 years ago by thermoman (IRC)

I had the same issues as described in this ticket.

Only the messages occured every 10 minutes instead of once an hour.

I just finished flashing my custom build of openwrt TRUNK: wifi now works as supposed to be.

KAMIKAZE (bleeding edge, r15771)

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.