9.10 / Kernel 2.6.31-17 / b43 / D810 suspend problem

**afluth** · January 9th, 2010

After upgrading my kernel from linux-image-2.6.31-16-generic to linux-image-2.6.31-17-generic my wireless adapter does not work after suspending the machine. If I select the 2.6.31-16

Laptop model: Dell Latitude D810

lspci

Code:

03:03.0 Network controller: Broadcom Corporation BCM4309 802.11a/b/g (rev 03)

lsmod | grep b43

Code:

b43                   122168  0 
mac80211              181140  1 b43
cfg80211               93052  2 b43,mac80211
led_class               4096  1 b43
ssb                    35364  1 b43

dmesg | grep b43

Code:

[    1.570851] b43-pci-bridge 0000:03:03.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[   17.242923] b43-phy0: Broadcom 4306 WLAN found (core revision 5)
[   17.756050] b43 ssb0:0: firmware: requesting b43/ucode5.fw
[   17.783490] b43 ssb0:0: firmware: requesting b43/pcm5.fw
[   17.788781] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
[   17.794956] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
[   17.916039] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
[   17.985016] Registered led device: b43-phy0::tx
[   17.985036] Registered led device: b43-phy0::rx
[   17.985061] Registered led device: b43-phy0::radio
[   85.905815] b43-pci-bridge 0000:03:03.0: PCI INT A disabled
[   86.429872] b43-pci-bridge 0000:03:03.0: restoring config space at offset 0xf (was 0x100, writing 0x10a)
[   86.429892] b43-pci-bridge 0000:03:03.0: restoring config space at offset 0x4 (was 0x0, writing 0xdfbfe000)
[   86.429897] b43-pci-bridge 0000:03:03.0: restoring config space at offset 0x3 (was 0x0, writing 0x4000)
[   86.429904] b43-pci-bridge 0000:03:03.0: restoring config space at offset 0x1 (was 0x0, writing 0x106)
[   87.872202] b43-pci-bridge 0000:03:03.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[   88.969062] b43-phy0: Radio hardware status changed to DISABLED
[  289.159600] b43-phy1: Broadcom 4306 WLAN found (core revision 5)
[  289.260066] b43 ssb0:0: firmware: requesting b43/ucode5.fw
[  289.266901] b43 ssb0:0: firmware: requesting b43/pcm5.fw
[  289.275567] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
[  289.282434] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
[  289.400053] b43-phy1: Loading firmware version 410.2160 (2007-05-26 15:32:10)
[  289.453105] Registered led device: b43-phy1::tx
[  289.453147] Registered led device: b43-phy1::rx
[  289.453191] Registered led device: b43-phy1::radio

iwconfig before suspend:

Code:

wlan0     IEEE 802.11bg  ESSID:"XXXXX"  
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:22:3F:BC:57:A8   
          Bit Rate=54 Mb/s   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=63/70  Signal level=-47 dBm  Noise level=-70 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

after suspend:

Code:

wlan0     IEEE 802.11bg  ESSID:"XXXXX"  
          Mode:Managed  Frequency:2.437 GHz  Access Point: Not-Associated   
          Tx-Power=off   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

rfkill list after suspend

Code:

1: phy1: Wireless LAN
	Soft blocked: no
	Hard blocked: yes

So far I've been using rmmod and modprobe to get connected again without having to restart.

Any advice would be appreciated.

**%hMa@?b<C** · January 9th, 2010

edit the line with MODULES=" " to read

Code:

MODULES="b43"

in /etc/default/acpi-support

**afluth** · January 9th, 2010

I added b43 to the MODULES variable in acpi-support, but it doesn't seem to help. I'm not sure why.

From reading the description found in /etc/default/acpi-support, I would have expected to to have the same result as rmmod and modprobe that I've been using.

**%hMa@?b<C** · January 10th, 2010

Originally Posted by afluth

I added b43 to the MODULES variable in acpi-support, but it doesn't seem to help. I'm not sure why.

From reading the description found in /etc/default/acpi-support, I would have expected to to have the same result as rmmod and modprobe that I've been using.

that is odd, because essentially what it does is load and unload the module.
have you tried a reboot since adding the b43 to the file?

**afluth** · January 10th, 2010

Yeah, I did end up rebooting and that didn't seem to help.

I suppose I should be looking into the change logs of the kernel update and see if I can locate what patch is causing me trouble...

**Phesto** · January 10th, 2010

Just wanted to share that you aren't the only one that is having this issue. I am having the same problem with my Dell latitude d600. I haven't found a fix yet either.

**afluth** · January 11th, 2010

Does your laptop have the BCM4309 as well? ..or a slightly different part?

**afluth** · January 13th, 2010

I found what is causing us trouble: http://git.kernel.org/?p=linux/kerne...0e1520b0dcc81b

I reverted this change, compiled the kernel and that seems to fix the issue for me.