Bug 917661

Summary: 3G Modem cannot reconnect
Product: [Fedora] Fedora Reporter: prudy <prudy1>
Component: ModemManagerAssignee: Dan Williams <dcbw>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 18CC: dcbw
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: 2014-02-05 19:37:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Patch (for modemmanager git branch MM_06) fixing the problem. none

Description prudy 2013-03-04 13:26:55 UTC 
Created attachment 704984 [details]
Patch (for modemmanager git branch MM_06) fixing the problem.

Description of problem:
The is still the same problem as raised here:
https://bugzilla.redhat.com/show_bug.cgi?id=861664
Once a connection is established with the 3G Modem, if one closes it (disconnection) on cannot connect back unless the modem is unplugged and re-plugged. The modem is still there but it is unable to reconnect.

Version-Release number of selected component (if applicable):
fresh updates as for 28.02.2013

How reproducible:
always

Steps to Reproduce:
1. plug the modem
2. connect
3. disconnect
4. cannot connect
  
Actual results:
unable to reconnect



Expected results:
ability to reconnect


Additional info:
modem-manager call sequence shows:
- mm_serial_port_close(): (ttyUSB0) serial port closed
- impl_modem_disconnect()
- mm_modem_disconnect()
- disconnect()
modem-manager[8295]: <info>  [1362323274.120498] [mm-modem.c:775] mm_modem_set_state(): Modem /org/freedesktop/ModemManager/Modems/0: state changed (connected -> disconnecting)
- real_do_disconnect()
- mm_serial_port_flash()#2 error 0xb7eb50
- disconnect_done()

This one seeing error goes into 'if', setting previous 'connected' state:
modem-manager[8295]: <info>  [1362323274.120708] [mm-modem.c:775] mm_modem_set_state(): Modem /org/freedesktop/ModemManager/Modems/0: state changed (disconnecting -> connected

- whilst it should go into 'else', resulting in:
modem-manager[8295]: <info>  [1362323274.120708] [mm-modem.c:775] mm_modem_set_state(): Modem /org/freedesktop/ModemManager/Modems/0: state changed (disconnecting -> registered
Comment 1 Fedora End Of Life 2013-12-21 11:50:59 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 2 Fedora End Of Life 2014-02-05 19:37:59 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.