Sierra mobile bradband does not wake from usb auto-suspend

[Peter Sasi]

I am using NetworkManager (and ModemManager under it) in 10.10 Maverick (the issue was also present on 10.04 Lucid as well, before I upgraded) on my Lenovo Thinkpad T61, kernel 2.6.35-22-generic.

I started setting power/level to auto using udev for power saving due to usb auto suspend.

Connecting to moble broadband fails if /sys/bus/usb/devices/6-1/power/level contains auto and the device has suspended.
It succeeds, if it is set to on.

I can connect with power/level set to auto only if I am fast enough and Disable then Enable Mobile Broadband in NetworkManager in quick succession, before the device has time to suspend.

Seems like NetworkManager / Kernel cannot get sierra module out of suspend using ttyUSBx.

Logs according to NetworkManager / ModemManager bug reporting protocol are also attached.

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~phc0-generic-phc 2.6.35.4
Uname: Linux 2.6.35-22-generic-phc x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: sape 1847 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfe220000 irq 49'
   Mixer name : 'Analog Devices AD1984'
   Components : 'HDA:11d41984,17aa20bb,00100400'
   Controls : 31
   Simple ctrls : 19
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7KHT24WW-1.08'
   Mixer name : 'ThinkPad EC 7KHT24WW-1.08'
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Wed Oct 13 13:08:27 2010
HibernationDevice: RESUME=UUID=ac20c706-49b8-4afa-a907-2c79ff5196e1
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: LENOVO 6460EDG
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic-phc root=UUID=9a7f4375-8f6b-43f7-aaf8-af5f7a179988 ro crashkernel=384M-2G:64M,2G-:128M quiet splash
ProcEnviron:
 LANGUAGE=hu_HU:hu:en_GB:en
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
SourcePackage: linux
dmi.bios.date: 11/14/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETC5WW (2.25 )
dmi.board.name: 6460EDG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7LETC5WW(2.25):bd11/14/2008:svnLENOVO:pn6460EDG:pvrThinkPadT61:rvnLENOVO:rn6460EDG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 6460EDG
dmi.product.version: ThinkPad T61
dmi.sys.vendor: LENOVO

[Jeremy Foshee (jeremyfoshee)]

Hi Peter,

If you could also please 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 . 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. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Peter Sasi (peter-sasi)]

Hi!
Tried it, does not wake with the latest either:

root@SAPENB:/# tail -n 15 /var/log/syslog
Oct 15 21:35:54 SAPENB wpa_supplicant[1248]: WPA: Group rekeying completed with 00:24:b2:d8:37:1a [GTK=CCMP]
Oct 15 21:35:54 SAPENB NetworkManager[941]: <info> (wlan0): supplicant connection state: group handshake -> completed
Oct 15 21:36:09 SAPENB NetworkManager[941]: <info> Activation (ttyUSB0) starting connection 'T-Mobile'
Oct 15 21:36:09 SAPENB NetworkManager[941]: <info> (ttyUSB0): device state change: 3 -> 4 (reason 0)
Oct 15 21:36:09 SAPENB NetworkManager[941]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 15 21:36:09 SAPENB NetworkManager[941]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
Oct 15 21:36:09 SAPENB NetworkManager[941]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
Oct 15 21:36:16 SAPENB NetworkManager[941]: <warn> GSM connection failed: (32) Sending command failed: 'Resource temporarily unavailable'
Oct 15 21:36:16 SAPENB NetworkManager[941]: <info> (ttyUSB0): device state change: 4 -> 9 (reason 1)
Oct 15 21:36:16 SAPENB NetworkManager[941]: <info> Marking connection 'T-Mobile' invalid.
Oct 15 21:36:16 SAPENB NetworkManager[941]: <warn> Activation (ttyUSB0) failed.
Oct 15 21:36:16 SAPENB NetworkManager[941]: <info> (ttyUSB0): device state change: 9 -> 3 (reason 0)
Oct 15 21:36:16 SAPENB NetworkManager[941]: <info> (ttyUSB0): deactivating device (reason: 0).
Oct 15 21:36:16 SAPENB NetworkManager[941]: <info> Policy set 'Auto eth0' (eth0) as default for IPv4 routing and DNS.
Oct 15 21:36:16 SAPENB NetworkManager[941]: <info> Policy set 'Auto eth0' (eth0) as default for IPv4 routing and DNS.
root@SAPENB:/# uname -a
Linux SAPENB 2.6.36-020636rc7-generic #201010070908 SMP Thu Oct 7 09:10:00 UTC 2010 x86_64 GNU/Linux
root@SAPENB:/# cat /sys/bus/usb/devices/6-1/power/level
auto
root@SAPENB:/#

I am removing the tag.

Thanks,
Peter

[penalvch (penalvch)]

Peter Sasi, 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 test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please 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 <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Peter Sasi (peter-sasi)]

Sorry, I no longer use that Laptop, neither Ubuntu.

[penalvch (penalvch)]

Peter Sasi, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/659837/comments/7 regarding you no longer have the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.