1814:0781 [STAGING] rt2800pci fails reconnect after suspend

[valkyr]

STATUS:
Fixed in mainline 2.6.36.
Not fixed in maverick.

ORIGINAL REPORT:
Hello,

This wireless network adapter works fine on first boot. It can connect to wireless networks.

After waking from a suspend however, it :

• Tries to connect
• Asks for wireless password again

...continuously, never able to connect.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic 2.6.35-22.33
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-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: james 1331 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
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: Sun Oct 10 22:22:39 2010
HibernationDevice: RESUME=UUID=d89c1510-60d5-4880-ac4d-1ca0242fc40a
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: ASUSTeK Computer INC. 901
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=ba5a9c5e-eb94-4d81-bc68-06280717021f ro quiet splash
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
SourcePackage: linux
StagingDrivers: rt2860sta
Title: [STAGING]
dmi.bios.date: 05/13/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2001
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 901
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.:bvr2001:bd05/13/2009:svnASUSTeKComputerINC.:pn901:pvrx.x:rvnASUSTeKComputerINC.:rn901:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 901
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

[Wolfgang Kufner (wolfgangkufner)]

Wow, over 15000 "phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed:" log lines in under 6 minutes.

I think its best to undupe this bug. On closer look it differs because here unlike bug 589342:
rt2800pci can successfully connect. Trouble only starts after suspend-resume.
Kernel is 2.6.35-22 - the final maverick stock kernel (the other report has a 2.6.34 kernel)

[Wolfgang Kufner (wolfgangkufner)]

Hi valkyr

Thanks for your bug report. It would be great if you could help by testing this further.

Two things:
Your lspci.txt says:
Kernel driver in use: rt2800pci
 Kernel modules: rt2860sta, rt2800pci
I think it would be a good idea to make sure the rt2860sta is not somehow involved in this problem. For this put a file (same permissions as the other ones there) in /etc/modprobe.d with the line:
install rt2860sta /bin/false
(This is stronger than "blacklist rt2860sta".)
Does the bug, specifically this flood of " Error - Indirect register access failed" log lines, still occur?
If yes, then could you please try out the mainline kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.36-maverick/ .
Just download and install the two i386.deb and the all.deb, then _shutdown_ and boot into it (you might have to press shift at boot to get a grub menu to select it).

Notes:
Shutdown and reboot make a difference for network cards. They hold on to e.g. firmware across a mere reboot cycle.
I find lspci -k nice to see which module actually is the one in use by the hardware.

Thanks

[valkyr (locki)]

rt2860 isn't in use according to lspci -k :

"Kernel driver in use: rt2800pci"

Also, there is a slight difference between suspending and hibernating :

Waking from suspend : NM applet shows trying to connect, then after 1-2 minutes, fails. I've had an occasional hard lock-up (total system freeze requiring power-off) after logging back in too. Not sure if it's connected to the WLAN)

Waking from hibernation : NM applet shows trying to connect, then after 1-2 minutes, asks for WPA key, then tries to connect for another 1-2 minutes, asks for WPA key, etc, etc, etc.

dmesg shows the same "Indirect register access failed" in both instances.

And, pressing the wireless enable/disable function key on the notebook I use (eeePC 901) fixes the problem, allowing connection *even after subsequent suspends/hibernates*.

I've attached what dmesg shows about the disable/enable WLAN button FWIW.

[valkyr (locki)]

Tested mainline. Seems to be fixed :)

[Doubletwist (doubletwist)]

I'm still having this exact issue on my EEE PC 1000H.
Updates are current as of 2010-11-08.

[Frederic PITOIZET (frederic-pitoizet)]

This is not fixed (2.6.35-23-generic #37-Ubuntu SMP Fri Nov 5 19:17:11 UTC 2010 i686).
I'm using a Medion Akoya E1210.
Switching wlan on/off doesn't solve the issue.
Sometimes resuming from sleep works.
It never worked, resuming from hibernation state.

[t-ob-i (tobi-t-ob-i)]

Installing http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.36-maverick/ solved it :) Thanks a lot!

[t-ob-i (tobi-t-ob-i)]

Sorry, solved only two or three times ... Now I got the same "Error - Indirect register..." -Error

[t-ob-i (tobi-t-ob-i)]

I installed http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.37-rc2-maverick/ - looks good!

[penalvch (penalvch)]

valkyr, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. 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. As well, please comment on which kernel version specifically you tested.

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', and comment as to why specifically you were unable to test it.

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.]