1814:0781 Wireless does not reconnect when resuming on EEEPC 901

Bug #661206 reported by Jim McKean
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

1) install maverick UNE on eeepc 901
2) upgrade all packages to current version
3) put machine to sleep
4) resume

Expected action, wireless reconnects automatically or I can reconnect manually

Actual action, 20% of time I can reconnect if I have not changed networks
The rest of the time, the network either spins without connecting (60%) or locks up everything (20%).

My fix is to reboot. I probably could reset something, but am stilling finding my way around the Unity interface and reboot works. I will trigger this when I have a minute and add the dmesg output.

WORKAROUND: Work around (mostly) by adding the following to /etc/modprobe.d/blacklist.conf

blacklist rt2800pci
blacklist rt2800usb
blacklist rt2x00lib
blacklist rt2x00pci
blacklist rt2x00usb

I also downloaded and compiled the current version of rt2860 drivers based on instructions I found here:

http://ubuntuforums.org/showthread.php?p=9988272

See post #3.

WORKAROUND: disable power saving script for pcie_aspm and wireless.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic 2.6.35-22.34
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.34-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: 0/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: jmckean 1412 F.... pulseaudio
 /dev/snd/pcmC0D0p: jmckean 1412 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 45'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,1043831a,00100004'
   Controls : 10
   Simple ctrls : 6
Date: Fri Oct 15 08:35:17 2010
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=23f7340a-83ea-49c3-849c-95ed9f7d0856 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
SourcePackage: linux
StagingDrivers: rt2860sta
Title: [STAGING]
WifiSyslog: Oct 15 08:13:15 Cub kernel: [39890.649653] lo: Disabled Privacy Extensions
dmi.bios.date: 06/11/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2103
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.:bvr2103:bd06/11/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.

Revision history for this message
Jim McKean (jimmckean) wrote :
Revision history for this message
Jim McKean (jimmckean) wrote :

Adding dmesg.txt with content of dmesg before and after suspend/move to another (known) network/resume. This this case, wireless applet spins without connecting.

Revision history for this message
Jim McKean (jimmckean) wrote :

Seems to be related to conflict between ralink drivers and -- something in the kernel?

Work around (mostly) by adding the following to /etc/modprobe.d/blacklist.conf

blacklist rt2800pci
blacklist rt2800usb
blacklist rt2x00lib
blacklist rt2x00pci
blacklist rt2x00usb

I also downloaded and compiled the current version of rt2860 drivers based on instructions I found here:

http://ubuntuforums.org/showthread.php?p=9988272

See post #3. Not sure it was needed, but I did it. Works OK, but sometimes when I am out of wireless network range for a long time (like an hour) network-manager greys out and a red exclamation mark appears. When returning to a network, the only way I have found to reconnect is reboot. No idea if this is a driver issue or a n-m issue or something else.

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Robert Drozda (drozda) wrote :

With Natty, this bug is still here.

Asus eeePC 901, wifi chip Ralink RT2860, driver RT2860sta, WPA-PSK wireless network

Wifi works on boot or restart, after suspend wireless does not reconnect when resuming from sleep. BUT only on battery! If power supply is connected, then wifi reconnect after suspend normally.

Attached is dmesg with succesfull (power supply) and unsuccesfull (battery) attempts.

Revision history for this message
Robert Drozda (drozda) wrote :

I found a similar bug - 773018 and suggested workaround - disable power saving script for pcie_aspm helped. Now wifi reconnects after suspend.

Revision history for this message
Jim McKean (jimmckean) wrote : Re: [Bug 661206] Re: Wireless does not reconnect when resuming on EEEPC 901

Thanks. I disabled both wireless and pcie_aspm and it seems to work.

On 04/30/2011 11:27 AM, Robert Drozda wrote:
> I found a similar bug - 773018 and suggested workaround - disable power
> saving script for pcie_aspm helped. Now wifi reconnects after
> suspend.
>

penalvch (penalvch)
summary: - Wireless does not reconnect when resuming on EEEPC 901
+ 1814:0781 Wireless does not reconnect when resuming on EEEPC 901
penalvch (penalvch)
description: updated
Revision history for this message
penalvch (penalvch) wrote :

Jim McKean, 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, could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspend ? 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>

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.

Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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