RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1334325 - [1.6] cannot up device after 20 successful uppings
Summary: [1.6] cannot up device after 20 successful uppings
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ModemManager
Version: 7.3
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Lubomir Rintel
QA Contact: Desktop QE
URL:
Whiteboard:
: 1333298 (view as bug list)
Depends On:
Blocks: 1333766 1334327
TreeView+ depends on / blocked
 
Reported: 2016-05-09 11:56 UTC by Vladimir Benes
Modified: 2016-11-04 08:32 UTC (History)
9 users (show)

Fixed In Version: ModemManager-1.6.0-0.1.rc4.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1334327 (view as bug list)
Environment:
Last Closed: 2016-11-04 08:32:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
debug logs (185.12 KB, text/plain)
2016-05-09 11:57 UTC, Vladimir Benes 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
FreeDesktop.org 95302 0 None None None 2016-08-26 13:37:38 UTC
Red Hat Product Errata RHEA-2016:2556 0 normal SHIPPED_LIVE ModemManager bug fix and enhancement update 2016-11-03 14:21:30 UTC

Description Vladimir Benes 2016-05-09 11:56:24 UTC 
Description of problem:
I've tried to up device several times (like 20x) and after a while device seems to be dead. Neither MM restart nor for i in $(ls /sys/bus/usb/devices/usb*/authorized); do echo 0 > $i; done; for i in $(ls /sys/bus/usb/devices/usb*/authorized); do echo 1 > $i; done helps. 


Version-Release number of selected component (if applicable):
ModemManager-1.6-0.3.rc3.el7.centos.lr3.x86_64
NetworkManager-1.2.0-1.el7.centos.rh1331395.x86_64
Comment 1 Vladimir Benes 2016-05-09 11:56:48 UTC 
Bus 001 Device 004: ID 0bdb:190d Ericsson Business Mobile Networks BV
Comment 2 Vladimir Benes 2016-05-09 11:57:05 UTC 
Created attachment 1155258 [details]
debug logs
Comment 3 Vladimir Benes 2016-05-09 11:57:33 UTC 
other machines still work so it's not a BTS issue
Comment 4 Lubomir Rintel 2016-05-09 12:24:55 UTC 
May 09 07:47:58 wlan-ralink-rt2500.wlan.rhts.eng.bos.redhat.com ModemManager[2897]: <debug> [1462794478.350253] [mm-port-serial-at.c:459] debug_log(): (ttyACM0): <-- '<CR><LF>+CME ERROR: 277<CR><LF>'
May 09 07:47:58 wlan-ralink-rt2500.wlan.rhts.eng.bos.redhat.com ModemManager[2897]: Invalid mobile equipment error code: 277
Comment 5 Dan Williams 2016-07-19 15:36:37 UTC 
CME error 277 means "not disconnected", and that should be fixed upstream already by https://bugs.freedesktop.org/attachment.cgi?id=123525.
Comment 6 Dan Williams 2016-07-19 15:40:04 UTC 
Vlad, can you re-test this bug with Lubo's latest COPR with ModemManager-1.6-0.4.20160615git8080be8.el7 ?  That should contain the necessary fix.
Comment 7 Dan Williams 2016-07-19 15:42:50 UTC 
*** Bug 1333298 has been marked as a duplicate of this bug. ***
Comment 8 Thomas Haller 2016-08-26 13:37:38 UTC 
(In reply to Dan Williams from comment #5)
> CME error 277 means "not disconnected", and that should be fixed upstream
> already by https://bugs.freedesktop.org/attachment.cgi?id=123525.

seems the correct BZ is https://bugs.freedesktop.org/show_bug.cgi?id=95302

and the commit that got merged to upstream is https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=55f3ab80835114342618083664c4fa585455b9e0


Already released with 1.6.0, and thus part of current builds.
Move to MODIFIED.
Comment 10 Vladimir Benes 2016-08-29 12:46:18 UTC 
still somehow seeing this.. not sure if it's device specific as some devices are not affected.
Comment 11 Vladimir Benes 2016-09-28 16:05:38 UTC 
Behavior is far better, and these failures can be caused by BTS as well. Failure rate is something around few % so nothing serious.
Comment 13 errata-xmlrpc 2016-11-04 08:32:27 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-2556.html
Note You need to log in before you can comment on or make changes to this bug.