Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
+++ This bug was initially created as a clone of Bug #1333298 +++
not sure if this is exactly the same but can be triggered via creation autoconnectable connection and upping it in a while (novice mode creation and nmcli con up in a while or file creation, reload and up).
device:
Bus 001 Device 006: ID 12d1:1001 Huawei Technologies Co., Ltd. E169/E620/E800 HSDPA Modem
--- Additional comment from Lubomir Rintel on 2016-05-06 04:35:21 EDT ---
(In reply to Vladimir Benes from comment #3)
> Created attachment 1154180[details]
> debul log from yet another device
>
> not sure if this is exactly the same but can be triggered via creation
> autoconnectable connection and upping it in a while (novice mode creation
> and nmcli con up in a while or file creation, reload and up).
>
> device:
> Bus 001 Device 006: ID 12d1:1001 Huawei Technologies Co., Ltd.
> E169/E620/E800 HSDPA Modem
That's a different thing I guess.
https://github.com/NetworkManager/ModemManager/commit/a997c821ce52a03392774f9b54ead885fc56e77bhttps://github.com/NetworkManager/ModemManager/commit/ce44197626b4f5c6e32769403932b8a6b280b708
No problem apparent in the log; work fine when running manually:
[root@wlan-intel-6150 bum2]# nmcli d
DEVICE TYPE STATE CONNECTION
enp3s0 ethernet connected enp3s0
ttyUSB2 gsm disconnected --
lo loopback unmanaged --
[root@wlan-intel-6150 bum2]# nmcli c add type gsm ifname '*' apn internet
Connection 'gsm' (d7af65e1-6953-45df-bae3-28d7e67066f9) successfully added.
[root@wlan-intel-6150 bum2]# while nmcli c up gsm; do :; done
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/4)
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/5)
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/6)
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/7)
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/8)
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/9)
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/10)
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/11)