Problem with WIFI in 10.10

Asked by chris on 2010-11-28

Since I've upgraded to 10.10 on my eepc 901 I have problems reconnecting to WIFI after suspending the computer. Looking the system log I get this message:

Nov 28 13:48:29 netbook kernel: [ 3118.380090] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed
: offset=0x0000101c, value=0xffffffff
Nov 28 13:48:29 netbook kernel: [ 3118.380624] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed
: offset=0x0000101c, value=0xffffffff
Nov 28 13:48:29 netbook kernel: [ 3118.381189] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed
: offset=0x0000101c, value=0xffffffff
Nov 28 13:48:29 netbook kernel: [ 3118.382305] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed
: offset=0x0000101c, value=0xffffffff
Nov 28 13:48:29 netbook kernel: [ 3118.388613] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed
: offset=0x0000101c, value=0xffffffff
Nov 28 13:48:29 netbook kernel: [ 3118.389185] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed
: offset=0x0000101c, value=0xffffffff
Nov 28 13:48:29 netbook kernel: [ 3118.390099] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed
: offset=0x0000101c, value=0xffffffff
Nov 28 13:48:30 netbook NetworkManager[795]: <warn> Activation (wlan0/wireless): association took too long.
Nov 28 13:48:30 netbook NetworkManager[795]: <info> (wlan0): device state change: 5 -> 6 (reason 0)
Nov 28 13:48:30 netbook NetworkManager[795]: <warn> Activation (wlan0/wireless): asking for new secrets
Nov 28 13:48:30 netbook NetworkManager[795]: <info> (wlan0): supplicant connection state: scanning -> disconnected
Nov 28 13:48:34 netbook NetworkManager[795]: <info> (wlan0): device state change: 6 -> 9 (reason 7)
Nov 28 13:48:34 netbook NetworkManager[795]: <warn> Activation (wlan0) failed for access point

The only way to connect again is to reboot :-(

Thanks for your help or for passing it on to whoever would be able to fix this bug ...

Question information

Can you help with this problem?

Provide an answer of your own, or ask chris for more information if necessary.

To post a message you must log in.