Description of problem:
I am using the bcm43xx driver because the newer driver for the same chipset did
not work at all for me. When NetworkManager is running, the wireless network
connection eventually dies, and then the driver gets stuck with a repeated
message "bcm43xx: IRQ_READY timeout" in dmesg. When I disable NetworkManager
using ntsysv, reboot, and just use service network (re)start, the wireless
connection still dies after a while, but the bcm43xx driver does not get stuck
and I can still bring the connection back up.

Version-Release number of selected component (if applicable):
NetworkManager-0.6.5-5.fc7

How reproducible:
Always

Steps to Reproduce:
1. Using knetworkmanager or the network configuration tool, try to activate
wlan0. Repeat until you succeed.
2. Do nothing.
3.
  
Actual results:
After some period of time, the network goes down, the radio is switched off and
the WLAN light on the case goes off. After the first or second time this happens
(it varies), it is not possible to restart the network, short of a reboot.

Expected results:
Should be possible to bring the network back up

Additional info:
It looks pretty obvious that the driver somehow gets into a state whereby it
thinks it should be receiving IRQs from the device, but the device is not even
listed in /proc/interrupts any more, presumably because it is switched off.
Beyond that, I couldn't figure it out. What would you like me to attach? This is
very reproducable.