Broadcom B43 driver does not survive a suspent/resume

Bug #666371 reported by Jeff Lane 
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

This is a regression from Lucid, I believe. Also, opening this per a discussion with JFo at UDS.

So, I have a Lenovo S10 netbook with a Broadcom BCM4312 wi-fi card. To use this card, I have to use the Broadcom B43 driver (b43.ko) and it does not do well after a suspend/resume cycle.

Steps to reproduce:

Maverick on a system w/ B43 based wi-fi
boot, connect to AP
Suspend system
Resume system
wireless no longer connects to APs found on scan, lots of error messages in /var/log/syslog

I've tried just bouncing the B43 driver as a workaround, but that doesn't work either. I have to fully reboot after each suspend to get wireless working again.

I'll try the STA driver shortly to see if that fares any better.

The error messages seen in syslog are like the following:

Oct 25 12:01:52 AsukaLangleySoryu kernel: [ 3810.628215] b43-phy1 ERROR: MAC suspend failed
Oct 25 12:01:53 AsukaLangleySoryu wpa_supplicant[1355]: Trying to associate with 00:26:cb:c6:df:d0 (SSID=
'Ubuntu' freq=2412 MHz)
Oct 25 12:01:53 AsukaLangleySoryu NetworkManager[889]: <info> (wlan0): supplicant connection state: scan
ning -> associating
Oct 25 12:01:53 AsukaLangleySoryu kernel: [ 3811.050554] wlan0: authenticate with 00:26:cb:c6:df:d0 (try
1)
Oct 25 12:01:53 AsukaLangleySoryu kernel: [ 3811.248173] wlan0: authenticate with 00:26:cb:c6:df:d0 (try
2)
Oct 25 12:01:53 AsukaLangleySoryu kernel: [ 3811.449074] wlan0: authenticate with 00:26:cb:c6:df:d0 (try
3)
Oct 25 12:01:53 AsukaLangleySoryu kernel: [ 3811.648199] wlan0: authentication with 00:26:cb:c6:df:d0 tim
ed out
Oct 25 12:01:59 AsukaLangleySoryu dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Oct 25 12:02:02 AsukaLangleySoryu dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Oct 25 12:02:03 AsukaLangleySoryu wpa_supplicant[1355]: Authentication with 00:26:cb:c6:df:d0 timed out.
Oct 25 12:02:03 AsukaLangleySoryu NetworkManager[889]: <info> (wlan0): supplicant connection state: asso
ciating -> disconnected
Oct 25 12:02:03 AsukaLangleySoryu NetworkManager[889]: <info> (wlan0): supplicant connection state: disc
onnected -> scanning
Oct 25 12:02:03 AsukaLangleySoryu kernel: [ 3821.564165] b43-phy1 ERROR: MAC suspend failed
Oct 25 12:02:04 AsukaLangleySoryu kernel: [ 3822.660179] b43-phy1 ERROR: MAC suspend failed
Oct 25 12:02:05 AsukaLangleySoryu NetworkManager[889]: <warn> (wlan0): link timed out.
Oct 25 12:02:10 AsukaLangleySoryu dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
Oct 25 12:02:10 AsukaLangleySoryu kernel: [ 3828.576108] b43-phy1 ERROR: MAC suspend failed

This happens after each suspend/resume cycle and requires a reboot to fix, as mentioned earlier.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic 2.6.35-22.35
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bladernr 1459 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0640000 irq 43'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,17aa3bf8,00100004'
   Controls : 13
   Simple ctrls : 8
Date: Mon Oct 25 12:04:58 2010
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=3c3fc556-30de-40e0-b2b4-2f7d5ba24d9d
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: LENOVO Lenovo
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=d282272a-a6a5-451a-9f90-25a78a151b77 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 02/05/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 14CN56WW
dmi.board.name: Mariana
dmi.board.vendor: Lenovo
dmi.board.version: Rev 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Lenovo
dmi.chassis.version: Rev 1.0
dmi.modalias: dmi:bvnLENOVO:bvr14CN56WW:bd02/05/2009:svnLENOVO:pnLenovo:pvrLenovo:rvnLenovo:rnMariana:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0:
dmi.product.name: Lenovo
dmi.product.version: Lenovo
dmi.sys.vendor: LENOVO

Revision history for this message
Jeff Lane  (bladernr) wrote :
Revision history for this message
Jeff Lane  (bladernr) wrote :

Update: I've removed the B43 driver and installed the Broadcom STA driver. Thus far, It's survived one suspend/resume cycle which is doing better than B43 was for me. I'll see what happens tomorrow during a full day of suspend/resuming at UDS and see if this is a better fit.

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Jeff Lane, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Jeff Lane  (bladernr) wrote :

Maverick is dead. Closing bug properly.

Changed in linux (Ubuntu):
status: Expired → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.