[intrepid] Need to rmmod/modprobe rt61pci after hibernate

Bug #323922 reported by Shaun Crampton
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned
Nominated for Jaunty by Ryan

Bug Description

Binary package hint: linux-image

After hibernating with an rt61-based WiFi card, I have no network. Doing "rmmod rt61pci; modprobe rt61pci" brings back the network connection.

Revision history for this message
Shaun Crampton (fasaxc) wrote :
Revision history for this message
Shaun Crampton (fasaxc) wrote :

$ apt-cache policy linux-image
linux-image:
  Installed: (none)
  Candidate: 2.6.27.11.14
  Version table:
     2.6.27.11.14 0
        500 http://ubuntu.virginmedia.com intrepid-updates/main Packages
        500 http://security.ubuntu.com intrepid-security/main Packages
     2.6.27.7.11 0
        500 http://ubuntu.virginmedia.com intrepid/main Packages

Revision history for this message
Shaun Crampton (fasaxc) wrote :

Addes dmesg output. Note there seem to be a few errors from rt61pci
$ dmesg | grep rt61
[ 2245.512011] phy0 -> rt61pci_set_device_state: Error - Device failed to enter state 1 (-16).
[ 2245.512071] rt61pci 0000:00:0b.0: PCI INT A disabled
[ 2245.628015] rt61pci 0000:00:0b.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[ 2245.628040] rt61pci 0000:00:0b.0: restoring config space at offset 0x3 (was 0x2008, writing 0x2010)
[ 2245.628084] phy0 -> rt61pci_mcu_request: Error - mcu request error. Request 0x50 failed for token 0xff.
[ 2245.628089] phy0 -> rt61pci_mcu_request: Error - mcu request error. Request 0x50 failed for token 0xff.
[ 2541.146484] phy0 -> rt61pci_mcu_request: Error - mcu request error. Request 0x50 failed for token 0xff.
[ 2541.149545] phy0 -> rt61pci_mcu_request: Error - mcu request error. Request 0x50 failed for token 0xff.
[ 2541.200349] rt61pci 0000:00:0b.0: PCI INT A disabled
[ 2543.795964] rt61pci 0000:00:0b.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[ 2543.814742] Registered led device: rt61pci-phy1:radio
[ 2543.815615] Registered led device: rt61pci-phy1:assoc
[ 3394.588011] phy1 -> rt61pci_set_device_state: Error - Device failed to enter state 1 (-16).
[ 3394.588070] rt61pci 0000:00:0b.0: PCI INT A disabled
[ 3394.704015] rt61pci 0000:00:0b.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[ 3394.704041] rt61pci 0000:00:0b.0: restoring config space at offset 0x3 (was 0x2008, writing 0x2010)
[ 3394.704084] phy1 -> rt61pci_mcu_request: Error - mcu request error. Request 0x50 failed for token 0xff.
[ 3394.704090] phy1 -> rt61pci_mcu_request: Error - mcu request error. Request 0x50 failed for token 0xff.
[ 3445.776681] phy1 -> rt61pci_mcu_request: Error - mcu request error. Request 0x50 failed for token 0xff.
[ 3445.777975] phy1 -> rt61pci_mcu_request: Error - mcu request error. Request 0x50 failed for token 0xff.
[ 3445.824318] rt61pci 0000:00:0b.0: PCI INT A disabled
[ 3451.800162] rt61pci 0000:00:0b.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[ 3451.814115] Registered led device: rt61pci-phy2:radio
[ 3451.814989] Registered led device: rt61pci-phy2:assoc

Revision history for this message
Shaun Crampton (fasaxc) wrote :

Forgot to mention. After the resume, I removed the module and modprobed it again to restore connectivity.

Revision history for this message
Ryan (ryan-farmer-personal-deactivatedaccount) wrote :

I can confirm, and this is an upstream bug as mainline kernel does this right up to 2.6.29-rc7.

So technically any Linux distribution should exhibit the same behavior.

affects: linux-meta (Ubuntu) → linux (Ubuntu)
Revision history for this message
StuJordan (r-launchpad-stuartjordan-co-uk) wrote :

Further to that last comment I can say this also affects jaunty (2.6.28-11-generic).

Changed in linux (Ubuntu):
status: New → Confirmed
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.