Ubuntu
linux package

3G modem stopped working since upgrading to 3.5.0-11

Bug #1041597 reported by Chris Coulson
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Since the upgrade to 3.5.0-11, I can no longer connect using my built-in 3G modem. If I try to connect using network manager, I get a notification a few seconds later telling me that I've been disconnected. There are some errors from modem-manager and network-manager in my syslog when this happens.

If I boot in to the 3.5.0-10 kernel, then the 3G modem works normally

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-11-generic 3.5.0-11.11
ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
Uname: Linux 3.5.0-11-generic x86_64
ApportVersion: 2.5.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: chr1s 2702 F.... pulseaudio
Date: Sat Aug 25 18:04:06 2012
HibernationDevice: RESUME=UUID=74c313af-6ee4-460f-98f3-c1ed84bb6cae
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
MachineType: Dell Inc. Latitude E6410
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-11-generic root=UUID=b2e419c9-361b-45c5-8964-3ee8ca387122 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-11-generic N/A
 linux-backports-modules-3.5.0-11-generic N/A
 linux-firmware 1.90
SourcePackage: linux
UpgradeStatus: Upgraded to quantal on 2011-11-16 (282 days ago)
dmi.bios.date: 02/15/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 04373Y
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA07:bd02/15/2011:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn04373Y:rvrA03:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6410
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

These are the errors I get when I try to connect:

Aug 25 18:13:19 farnsworth NetworkManager[964]: <info> Activation (ttyACM0) starting connection 'T-Mobile Default'
Aug 25 18:13:19 farnsworth NetworkManager[964]: <info> (ttyACM0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Aug 25 18:13:19 farnsworth NetworkManager[964]: <info> Activation (ttyACM0) Stage 1 of 5 (Device Prepare) scheduled...
Aug 25 18:13:19 farnsworth NetworkManager[964]: <info> Activation (ttyACM0) Stage 1 of 5 (Device Prepare) started...
Aug 25 18:13:19 farnsworth NetworkManager[964]: <info> (ttyACM0): device state change: prepare -> need-auth (reason 'none') [40 60 0]
Aug 25 18:13:19 farnsworth NetworkManager[964]: <info> Activation (ttyACM0) Stage 1 of 5 (Device Prepare) complete.
Aug 25 18:13:19 farnsworth NetworkManager[964]: <info> Activation (ttyACM0) Stage 1 of 5 (Device Prepare) scheduled...
Aug 25 18:13:19 farnsworth NetworkManager[964]: <info> Activation (ttyACM0) Stage 1 of 5 (Device Prepare) started...
Aug 25 18:13:19 farnsworth NetworkManager[964]: <info> (ttyACM0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Aug 25 18:13:19 farnsworth NetworkManager[964]: <info> Activation (ttyACM0) Stage 1 of 5 (Device Prepare) complete.
Aug 25 18:13:19 farnsworth modem-manager[941]: <info> Modem /org/freedesktop/ModemManager/Modems/0: state changed (registered -> connecting)
Aug 25 18:13:20 farnsworth modem-manager[941]: Invalid error code: 277
Aug 25 18:13:20 farnsworth modem-manager[941]: <info> Modem /org/freedesktop/ModemManager/Modems/0: state changed (connecting -> registered)
Aug 25 18:13:20 farnsworth NetworkManager[964]: <warn> GSM connection failed: (32) Unknown error
Aug 25 18:13:20 farnsworth NetworkManager[964]: <info> (ttyACM0): device state change: prepare -> failed (reason 'unknown') [40 120 1]
Aug 25 18:13:20 farnsworth NetworkManager[964]: <warn> Activation (ttyACM0) failed for connection 'T-Mobile Default'
Aug 25 18:13:20 farnsworth NetworkManager[964]: <info> (ttyACM0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Aug 25 18:13:20 farnsworth NetworkManager[964]: <info> (ttyACM0): deactivating device (reason 'none') [0]

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.6 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. 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'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc3-quantal/

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would you also be able to test some additional kernels? I'd like to perform a kernel bisect to identify the commit that introduced this regression.

tags: added: needs-bisect needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: regression-update
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

I'm actually not convinced this is a kernel bug anymore. When I reported the bug at the weekend, switching to the old kernel allowed me to use the modem. However, this morning I am also getting the same error in 3.5.0-10 so it might be something else (and I might have just been extremely lucky to get it to work once over the weekend)

I've subscribed Mathieu who might be able to provide some insight

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.