Bearer removed but somehow stays active and blocks device (ref bug #17666)

:1.6: cdc-wdm1: USB WDM device cdc_mbim 3-4:1.6 wwan0: register 'cdc_mbim' at usb-:00:14.0-4, CDC MBIM, 6a:58:b1:bb:ac:07 cdc_wdm 3-4:1.8: cdc-wdm2: USB WDM device cdc_acm 3-4:1.9: ttyACM18: USB ACM device Regards, Torsten Hilbrich modem-manager-2.log.gz Description: application/gzip

Re: Bearer removed but somehow stays active and blocks device (ref bug #17666)

listing provisioned contexts? Can you reproduce this easily? Is the issue resolved if the modem device gets rebooted? This is not easily reproducible, the problem was only reported once so far. The problem went away when rebooting the system. Torsten Hilbrich

Problems with PUK handling (CLIENT-8155)

of related components: ModemManager 1.4.6 libmbim 1.12.2 libqmi 1.12.4 With regards, Torsten Hilbrich ** * * Starting log for modem-manager * Current time: 2015-Jul-20 13:26:28 * ** info

Re: Problems with PUK handling (CLIENT-8155)

On 20.07.2015 19:28, Dan Williams wrote: [ Issues reported a LOCK_SIM_PUK ] I can reproduce the issue, and I've pushed a patch to MM git master (and backported it to various release branches) that should fix the issue, return an error to the client, and set the modem lock state accordingly.

Logging in systemd environment

Hello, I tried to integrate ModemManager in our environment where the modemmanager is started as systemd unit and logging is stored into the journal. I tried different settings, using the default syslog mechanism and using the --log-file=/dev/stderr option (and setting up the systemd unit to

[PATCH 4/5] log: Introduce function pointer to handle different log backends

This allows for easier additions of other logging mechanism. Using the syslog loglevel as parameter because we need to be able to map the MMLogLevel and the GLogLevelFlags to a common representation when using the log_backend in _mm_log and log_handler. The syslog level is more suitable because

[PATCHv2]: Logging cleanup and systemd journal support

This series of patches is based on the "Logging and --help updates" series posted by Aleksander Morgado . It start with cleaning up some parts of the logging code. The the existing logging support (supporting syslog and file-based logging) is split into two different

[PATCH 2/5] log: Refactor log level text output

Adding a helper function to turn the log level into the text. Also add an internal flag to disable this output. This flag will become useful when adding systemd journal support. --- src/mm-log.c | 34 -- 1 file changed, 20 insertions(+), 14 deletions(-) diff --git

[PATCH 1/5] log: Refactor evaluation of log level

Starting with adding a typed enum type for the log level named MMLogLevel. Suggested-By: Aleksander Morgado The level was checked twice in _mm_log. Once at the beginning and again when turning the level into both the syslog priority and some descriptive text which was

[PATCH 3/5] log: Add mapping from glib loglevel to syslog priority

Improves readability of log_handler function. --- src/mm-log.c | 44 1 file changed, 20 insertions(+), 24 deletions(-) diff --git a/src/mm-log.c b/src/mm-log.c index 7b4fa7e..2b7907c 100644 --- a/src/mm-log.c +++ b/src/mm-log.c @@ -83,6 +83,25 @@

[PATCH 3/5] log: Add mapping from glib loglevel to syslog priority

Improves readability of log_handler function. --- src/mm-log.c | 44 1 file changed, 20 insertions(+), 24 deletions(-) diff --git a/src/mm-log.c b/src/mm-log.c index 7b4fa7e..2b7907c 100644 --- a/src/mm-log.c +++ b/src/mm-log.c @@ -83,6 +83,25 @@

[PATCH 4/5] log: Introduce function pointer to handle different log backends

This allows for easier additions of other logging mechanism. Using the syslog loglevel as parameter because we need to be able to map the MMLogLevel and the GLogLevelFlags to a common representation when using the log_backend in _mm_log and log_handler. The syslog level is more suitable because

[PATCH 2/5] log: Refactor log level text output

Adding a helper function to turn the log level into the text. Also add an internal flag to disable this output. This flag will become useful when adding systemd journal support. --- src/mm-log.c | 34 -- 1 file changed, 20 insertions(+), 14 deletions(-) diff --git

[PATCH 5/5] log: Add support for journal logging

This logging is available if the software was build with the configure option --with-systemd-journal. It will be enabled by default if libsystemd is found. The runtime parameter --log-journal enables to output of log messages to the systemd journal. Please note that the journal priority field

[PATCH 3/5] log: Add mapping from glib loglevel to syslog priority

Improves readability of log_handler function. --- src/mm-log.c | 44 1 file changed, 20 insertions(+), 24 deletions(-) diff --git a/src/mm-log.c b/src/mm-log.c index eea0bac..151b40d 100644 --- a/src/mm-log.c +++ b/src/mm-log.c @@ -82,6 +82,25 @@

[PATCHv3]: Logging cleanup and systemd journal support

This series of patches is based on master. It start with cleaning up some parts of the logging code. The the existing logging support (supporting syslog and file-based logging) is split into two different functions using a function pointer to select them. Then the support for logging using the

[PATCH 2/5] log: Refactor log level text output

Adding a helper function to turn the log level into the text. Also add an internal flag to disable this output. This flag will become useful when adding systemd journal support. --- src/mm-log.c | 34 -- 1 file changed, 20 insertions(+), 14 deletions(-) diff --git

[PATCH 1/5] log: Refactor evaluation of log level

Starting with adding a typed enum type for the log level named MMLogLevel. Suggested-By: Aleksander Morgado The level was checked twice in _mm_log. Once at the beginning and again when turning the level into both the syslog priority and some descriptive text which was

[PATCH 3/5] log: Add mapping from glib loglevel to syslog priority

Improves readability of log_handler function. --- src/mm-log.c | 45 + 1 file changed, 21 insertions(+), 24 deletions(-) diff --git a/src/mm-log.c b/src/mm-log.c index ec622dc..bedf88f 100644 --- a/src/mm-log.c +++ b/src/mm-log.c @@ -82,6 +82,26 @@

[PATCH 4/5] log: Introduce function pointer to handle different log backends

This allows for easier additions of other logging mechanism. --- src/mm-log.c | 53 ++--- 1 file changed, 34 insertions(+), 19 deletions(-) diff --git a/src/mm-log.c b/src/mm-log.c index bedf88f..6578d68 100644 --- a/src/mm-log.c +++ b/src/mm-log.c

[PATCH] v1: Logging cleanup and systemd journal support

This series of patches is based on the "Logging and --help updates" series posted by Aleksander Morgado . It start with cleaning up some parts of the logging code. The the existing logging support (supporting syslog and file-based logging) is split into two different

Re: [PATCH 1/5] log: Refactor evaluation of log level

Am 29.05.2017 um 13:27 schrieb Aleksander Morgado: > Hey Torsten, > > On 22/05/17 07:49, Torsten Hilbrich wrote: [...] >> diff --git a/src/mm-log.c b/src/mm-log.c >> index bac0fce..e0255c3 100644 >> --- a/src/mm-log.c >> +++ b/src/mm-log.c >> @@ -65,6 +65

Re: [PATCH 2/5] log: Refactor log level text output

Am 29.05.2017 um 13:28 schrieb Aleksander Morgado: > Hey Torsten, > [...] > >> +{ >> +switch (level) { >> +case LOGL_DEBUG: >> +return "debug"; >> +case LOGL_WARN: >> +return "warn"; >> +case LOGL_INFO: >> +return "info"; >> +case LOGL_ERR: >> +

ModemManager consuming 100% CPU while refreshing 3GPP registration

Hello, I recently had some problems with my Lenovo T450s. The ModemManager and mbim-proxy processes were generating a lot of CPU activity. ModemManager: 1.8.0 libmbim: 1.16.0 libqmi: 1.20.0 Kernel: v4.14.65 The modem is a: usb 2-4: New USB device found, idVendor=1199, idProduct=a001 usb 2-4:

Problems compiling with clang (3.8.21)

least in libqdcdm is done with -Werror. It this a known problem? Are fixes welcome to support compilation with clang? The same problem happened in libmbim and libqmi. With regards, Torsten Hilbrich ___ ModemManager-devel mailing list Modem

Re: Problems compiling with clang (3.8.21)

On 02.04.19 17:02, Dan Williams wrote: > I think -Wno-unused-but-set-variable is actually a mistake and it > should be "-Wunused-but-set-variable". But that causes build errors > that we should fix. > > Does clang support -Wunused-but-set-variable? No. > > Also, does making this change in

Re: Problems compiling with clang (3.8.21)

[ I forgot to include the list in my previous answer] On 03.04.19 19:48, Ben Chan wrote: > Could you try these patches? > > https://gitlab.freedesktop.org/mobile-broadband/libmbim/merge_requests/8 > https://gitlab.freedesktop.org/mobile-broadband/libqmi/merge_requests/35 >

Strange Resume behaviour of N5321 since 4.19

Is this problem known to anyone? Is there a better to way to solve this issue than completely ignoring the device? I have attached the complete kernel logs and the logs from the modem manager. During the log creation no SIM was inserted so this error message is to be expected. Thanks, Torsten

Regression regarding ip_type when updating from 1.10.4 to 1.12.0

Hello, I recently tried updating to the new version of ModemManager Previous versions: - ModemManager 1.10.4 - libmbim 1.18.2 New versions: - ModemManager 1.12.0 - libmbim 1.20.2 The test device is a Lenovo T470s with a Sierra Wireless EM7455. The provider is vodafone.de We configure our

1.14.2: Compile errors when using --with-systemd-journal=yes

Hello, I just did some first testing with the new stable version 1.14.2 (Updating from 1.12.12) and noticed some regressions regarding the support of systemd-journal. The compilation fails with: make[5]: Entering directory '/build/client/3.5.x/freedesktop/modemmanager/work/modemmanager/src'

Re: 1.14.2: Compile errors when using --with-systemd-journal=yes

On 18.09.20 10:16, Aleksander Morgado wrote: > Hey, > >> >> I just did some first testing with the new stable version 1.14.2 (Updating >> from 1.12.12) and noticed some regressions regarding the support of >> systemd-journal. >> > > Why is this a regression between 1.14.2 and 1.12.12? IIRC no

Re: 1.14.2: Compile errors when using --with-systemd-journal=yes

On 18.09.20 12:43, Torsten Hilbrich wrote: > I also don't know what is the best way to handle it. It will most likely > be an issue for people not building against the system headers but > against some component-based directory layout where each dependency is > stored in some s

Kernel 5.10.29: Problems with Huawei ME906s

Hello, I'm currently testing kernel 5.10.29 with ModemManager 1.14.10 on a Lenovo T460s: 2021-05-12 10:15:18.286 kernel: usb 1-2: new high-speed USB device number 2 using xhci_hcd 2021-05-12 10:15:18.286 kernel: usb 1-2: New USB device found, idVendor=12d1, idProduct=15c1, bcdDevice= 1.02

Re: Kernel 5.10.29: Problems with Huawei ME906s

On 12.05.21 13:09, Torsten Hilbrich wrote: ... > 2021-05-12 10:15:26.137 kernel: cdc_mbim 1-2:3.0: setting rx_max = 16384 > 2021-05-12 10:15:26.149 kernel: cdc_mbim 1-2:3.0: NDP will be placed at end > of frame for this device. > 2021-05-12 10:15:26.150 kernel: cdc_mbim 1-2:3.0: cdc-w