Bug 490482

Summary:	2.6.27.19-170.2.35.fc10.x86_64 USB-connected UMTS modem regression
Product:	[Fedora] Fedora	Reporter:	Pawel Salek <pawsa>
Component:	NetworkManager	Assignee:	Dan Williams <dcbw>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	low
Version:	10	CC:	dcbw, kernel-maint, quintela, yunus.tji.nyan
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-03-18 17:04:52 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pawel Salek 2009-03-16 16:52:17 UTC

Description of problem:
Recent kernel update broke my USB-connected UMTS modem Huawei E169. 

Version-Release number of selected component (if applicable):
2.6.27.19-170.2.35.fc10

How reproducible:
Always

Steps to Reproduce:
1. Connect the modem. It will be automatically detected as "Auto Mobile Broadband (GSM) connection"
2. Attempt the connection activation using Network Manager
  
Actual results:
NetworkManager fails to establish the connection. Messages say:
<WARN>  check_pin_done(): PIN checking timed out
<info>  (ttyUSB0): device state change: 4 -> 9
<info>  Marking connection 'Auto Mobile Broadband (GSM) connection' invalid.
<info>  Activation (ttyUSB0) failed.

Expected results:
The connection is established. The messages should read:
<info>  (ttyUSB0): powering up...
<info>  Registered on Home network
<info>  Associated with network: (sanitized?)
<info>  Connected, Woo!
<info>  (ttyUSB0): device state change: 4 -> 5
<info>  Starting pppd connection

Additional info:
Should you need any extra information, just ask. I mark this regression as urgent as it effectively takes me off the net, I cannot even download new fixed packages.

Comment 1 yunus 2009-03-18 16:04:49 UTC

Thank you for filing the bug.

Did you also update NetworkManager when you updated the kernel?
It will be helpful if you can provide the version of your NetworkManager. I suspect that this bug related to https://bugzilla.redhat.com/show_bug.cgi?id=487663.


-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 2 Pawel Salek 2009-03-18 16:28:24 UTC

Yes, the kernel and NetworkManager upgrades came in one batch. Downgrading NetworkManager to NetworkManager-0.7.0.99-2.fc10.x86_64 was the first thing I did when I got the chance (that is, alternative network connection, which was not easy). It did not help. Right now, I am running NetworkManager-0.7.0.99-3.fc10.x86_64 with the older kernel and it works fine.

Comment 3 Pawel Salek 2009-03-18 17:04:52 UTC

I withdraw my last comment. A second test showed that NM-0.7.0.99-3 worked because the device was already initialized by NM-0.7.0.99-2. If I initialize the device with NM-0.7.0.99-2, *disconnect it*, install NM-0.7.0.99-3, connect the device again, NM will not be able to establish the connection.

*** This bug has been marked as a duplicate of bug 487663 ***

Comment 4 yunus 2009-03-18 17:24:08 UTC

I reset the component to NetworkManager

Thank you again for reporting the bug and marking this as a duplicate of 487663.

If NM will not be able to establish the connection, you may want to try to unplug the usb modem and replug it until NM establish the connection. This trick works for me.
-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers