CPU loading issue

[Marc Murphy]

Hi DavidM,
I am using the MU609 on an embedded AM3359 platform comprising of 3.12 Kernel and the latest ModemManager 1.4.6.

I did have to modify the GPS setup instruction to be a 1 second refresh rates, that brings it in line with other modems.
plugins/huawei/mm-broadband-modem-huawei.c
- "^WPDFR=65535,30"
+ "^WPDFR=65535,1"

Cheers
Marc


________________________________________
From: ModemManager-devel [modemmanager-devel-bounces at lists.freedesktop.org] on behalf of David McCullough [david.mccullough at accelecon.com]
Sent: 10 June 2015 00:33
To: Marc Murphy
Cc: 'modemmanager-devel at lists.freedesktop.org'
Subject: Re: CPU loading issue

Marc,

Marc Murphy wrote the following:
> Hello All,
> I am using ModemManager to perform GPS logging and it works really well with most modems.
>
> I have a SierraWireless MC7710 and that works beautifully with qmi and logging.
> I also have a Huawei MU609 and that works but something slowly causes ModemManager to consume 100% CPU.
> We would really like to get the MU609 to work with ModemManager as the price difference is huge and makes the modem viable for low cost.


I have been running the MU609 under ModemManager for some time.  I haven't
seen this issue.

How long does it take for the CPU to increase a noticable amount ?

I'll fire one up here and see how it goes,  are you running a particular MM
version ?

Cheers,
Davidm


>
> The MC7710 will sit there all day at about 0.7% CPU which is brilliant
>   PID USER      PR  NI    VIRT    RES %CPU %MEM     TIME+ S COMMAND
> 1015 root      20   0   37.8m   6.1m  0.7   1.2   0:12.85 S  `- ModemManager
>
> The MU609 creeps up
>   PID USER      PR  NI    VIRT    RES %CPU %MEM     TIME+ S COMMAND
> 1009 root      20   0   37.8m   5.2m  0.0  1.1   0:05.14 S  `- ModemManager
> 1009 root      20   0   37.8m   5.2m  1.3  1.1   0:05.16 S  `- ModemManager
> 1009 root      20   0   37.8m   5.2m  4.6  1.1   0:05.23 S  `- ModemManager
> 1009 root      20   0   37.8m   5.2m  1.3  1.1   0:05.25 S  `- ModemManager
> up 9 min
> 1009 root      20   0   37.8m   5.3m  4.6  1.1   0:15.22 S  `- ModemManager
> 1009 root      20   0   37.8m   5.3m  9.9  1.1   0:15.37 S  `- ModemManager
> 1009 root      20   0   37.8m   5.3m  5.3  1.1   0:15.45 S  `- ModemManager
> 1009 root      20   0   37.8m   5.3m  9.9  1.1   0:15.60 S  `- ModemManager
> up 21 min
> 1009 root      20   0   37.9m   5.4m 20.5  1.1   1:20.14 S  `- ModemManager
> 1009 root      20   0   37.9m   5.4m 10.5  1.1   1:20.30 S  `- ModemManager
> 1009 root      20   0   37.9m   5.4m 21.2  1.1   1:20.62 S  `- ModemManager
> up 38 min
> 1009 root      20   0   38.0m   5.4m 47.7  1.1   9:49.07 R  `- ModemManager
> 1009 root      20   0   38.0m   5.4m 78.9  1.1   9:51.02 R  `- ModemManager
> 1009 root      20   0   38.0m   5.4m 81.1  1.1   9:52.95 R  `- ModemManager
> 1009 root      20   0   38.0m   5.4m 79.5  1.1   9:54.85 R  `- ModemManager
> 1009 root      20   0   38.0m   5.4m 81.1  1.1   9:56.78 R  `- ModemManager
>
> Im wondering where is the best place to look at where the issue could be ?
>
> Is there a processing loop that could be getting stuck ?
>
> Any help appreciated.
>
> Thanks
> Marc
> _______________________________________________
> ModemManager-devel mailing list
> ModemManager-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

--
David McCullough,  davidm at spottygum.com,   Ph: 0410 560 763
_______________________________________________
ModemManager-devel mailing list
ModemManager-devel at lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/modemmanager-devel