Bug 99047 - ModemManager 1.6.2 core dump with Huawei E372 / Vodafone K4605
Summary: ModemManager 1.6.2 core dump with Huawei E372 / Vodafone K4605
Status: RESOLVED MOVED
Alias: None
Product: ModemManager
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: ModemManager bug user
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-10 12:37 UTC by Lorenzo
Modified: 2018-06-10 09:05 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
MM debug log (266.10 KB, text/plain)
2016-12-10 12:37 UTC, Lorenzo
Details
Part of dmesg log (3.74 KB, text/plain)
2016-12-10 12:39 UTC, Lorenzo
Details
lsusb -v output for device (8.13 KB, text/plain)
2016-12-10 12:39 UTC, Lorenzo
Details
dmesg 2 (36.39 KB, text/plain)
2016-12-11 12:54 UTC, Lorenzo
Details

Description Lorenzo 2016-12-10 12:37:55 UTC
Created attachment 128405 [details]
MM debug log

ModemManager 1.6.2 crashes when my Huawei E372 / Vodafone K4605 is attached.

OS is OpenSUSE Tumbleweed

Let me know if you need more information.

Many thanks!
Lorenzo

Output of uname -a:
Linux linux-fwcq.site 4.8.12-1-default #1 SMP PREEMPT Fri Dec 2 09:44:55 UTC 2016 (f8adb5a) x86_64 x86_64 x86_64 GNU/Linux
Comment 1 Lorenzo 2016-12-10 12:39:12 UTC
Created attachment 128406 [details]
Part of dmesg log
Comment 2 Lorenzo 2016-12-10 12:39:45 UTC
Created attachment 128407 [details]
lsusb -v output for device
Comment 3 Aleksander Morgado 2016-12-11 11:49:51 UTC
Thanks; thg assert will be fixed in the next 1.6.x release.

BUT, it looks like the device you're trying to use is already in "autoconnected" mode, and therefore you just need to run DHCP client on the WWAN interface; without ModemManager intervention (the "Start Network" command returns "No Effect"). 

Could you validate this assumption running the following command?
$ qmicli -d /dev/cdc-wdm0 -p --wds-get-autoconnect-settings
Comment 4 Lorenzo 2016-12-11 12:54:35 UTC
Created attachment 128412 [details]
dmesg 2

Autoconnect is enabled:
# qmicli -d /dev/cdc-wdm0 -p --wds-get-autoconnect-settings 
Autoconnect settings retrieved:
        Status: 'enabled'

but there is no connection (as also evidenced by the connection LED signal on the device being off):
# qmicli -d /dev/cdc-wdm0 --wds-get-packet-service-status
[/dev/cdc-wdm0] Connection status: 'disconnected'

I have attached the dmesg log from a new attempt.

Thanks for your help!
Comment 5 Aleksander Morgado 2016-12-12 08:46:46 UTC
(In reply to Lorenzo from comment #4)
> Created attachment 128412 [details]
> dmesg 2
> 
> Autoconnect is enabled:
> # qmicli -d /dev/cdc-wdm0 -p --wds-get-autoconnect-settings 
> Autoconnect settings retrieved:
>         Status: 'enabled'
> 
> but there is no connection (as also evidenced by the connection LED signal
> on the device being off):
> # qmicli -d /dev/cdc-wdm0 --wds-get-packet-service-status
> [/dev/cdc-wdm0] Connection status: 'disconnected'
> 
> I have attached the dmesg log from a new attempt.
> 

Can you disable autoconnect and retry?

# qmicli -d /dev/cdc-wdm0 -p --wds-set-autoconnect-settings=disabled
Comment 6 Lorenzo 2017-01-01 19:24:33 UTC
Hi Aleksander,

the connection succeeds in fact with autoconnect disabled.
Let me know if you need other information.

Thanks,
Lorenzo
Comment 7 GitLab Migration User 2018-06-10 09:05:12 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/63.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.