RT2860 [1814:0781]: rt2800pci filling the syslog with errors after resume from suspend

[Ricardo Graça]

After I resumed my computer from suspend it was very very unresponsive. Typing my password and clicking the unlock button took nearly one minute. When I checked the first TTY with Ctrl+Alt+F1 it was being flooded with these messages:

...
Jun 14 21:08:28 dragonfly kernel: [ 2073.282143] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x0000101c, value=0xffffffff
Jun 14 21:08:28 dragonfly kernel: [ 2073.292412] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff
Jun 14 21:08:28 dragonfly kernel: [ 2073.302624] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff
Jun 14 21:08:28 dragonfly kernel: [ 2073.314925] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x0000101c, value=0xffffffff
Jun 14 21:08:28 dragonfly kernel: [ 2073.323033] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
Jun 14 21:08:28 dragonfly kernel: [ 2073.333261] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff
Jun 14 21:08:28 dragonfly kernel: [ 2073.343494] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff
Jun 14 21:08:28 dragonfly kernel: [ 2073.355909] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x0000101c, value=0xffffffff
Jun 14 21:08:28 dragonfly kernel: [ 2073.363925] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
...

This isn't the first time this has happened but I still can't reproduce it consistently. I was using Unity2D at the time the bug appeared but I don't know if that's related.
System is an Asus Eee PC1000h, running Ubuntu 11.04 updated at least a week ago and using a wireless Ralink RT2860 adapter using the in kernel RT2800pci driver.

WORKAROUND: After disabling the wifi via the toggle key (Fn+F2) and enabling it back again everything worked fine.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-generic 2.6.38.8.22
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-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: ricardo 1632 F.... pulseaudio
CRDA: Error: [Errno 2] Ficheiro ou directoria inexistente
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 44'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,1043831a,00100004'
   Controls : 10
   Simple ctrls : 6
Date: Tue Jun 14 21:19:43 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: ASUSTeK Computer INC. 1000H
ProcEnviron:
 LANGUAGE=pt:en
 PATH=(custom, user)
 LANG=pt_PT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-8-generic root=UUID=fbaf1df7-4b65-475e-8f43-9ff1b6c4e744 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-8-generic N/A
 linux-backports-modules-2.6.38-8-generic N/A
 linux-firmware 1.52
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2204
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1000H
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2204:bd10/21/2009:svnASUSTeKComputerINC.:pn1000H:pvrx.x:rvnASUSTeKComputerINC.:rn1000H:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 1000H
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

[Wolfgang Kufner (wolfgangkufner)]

I have the same [1814:0781] hardware and as far as I remember the kernel that you tested did fix all power saving related issues for me. My feeling from the errors I did get before that were that the specific error messages were not really important. It was just falling apart one way or another.

Since that kernel does not seem to fix it in your case it's time to look at other suspects:

a) Interference from the rt2860sta staging driver:
At least blacklist the rt2860sta. You might also try to just rename the module from rt2860sta.ko to e.g. rt2860sta.ko.disable in the module directory of the kernel you are testing. Not sure if it does make a difference.

b) A platform specific problem:
I vaguely remember issues with a platform driver. Could you read:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/661682/comments/6
and related and see if this has something to do with your problems.

[penalvch (penalvch)]

Ricardo Graça, thank you for reporting this and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume ? As well, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ . However, note you can only test Suspend, not Hibernate, when using a LiveCD. If the issue remains, run the following command in the development release from a Terminal (Applications->Accessories->Terminal) as it will automatically gather and attach updated debug information to this report.

apport-collect -p linux <BUGNUMBER>

Additionally, if you could try to reproduce this with the upstream mainline kernel 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.

[Launchpad Janitor (janitor)]

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