[Gta04-owner] Modem logs

Neil Jerram neil at ossau.homelinux.net
Sun Jan 6 01:33:27 CET 2013


Neil Jerram <neil at ossau.homelinux.net> writes:

> Denis 'GNUtoo' Carikli <GNUtoo at no-log.org> writes:
>
>> On Tue, 06 Nov 2012 18:44:11 +0000
>> Neil Jerram <neil at ossau.homelinux.net> wrote:
>>
>>> Denis 'GNUtoo' Carikli <GNUtoo at no-log.org> writes:
>>> 
>>> > Hi,
>>> >
>>> > I found a way to get the modem logs:
>>> 
>>> This is great!  Do you have an example of the output?
>> $ ./show_msm_messages.rb telnet
>> [TS 829023732509] <HIGH>  (rfgsm_mc.c:402)
> [...]
>
>> Maybe we could use that to see what happens before/after the USB reset
>> of the modem (the problem where /dev/ttyHS* disapear, for instance
>> during a call)?
>
> Yes indeed, that's what I was thinking too.

I've written a C program to do the same thing as the Ruby
show_msm_messages.rb does, and it's attached.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: gta04-modem-messages.c
Type: text/x-csrc
Size: 6149 bytes
Desc: not available
URL: <http://lists.goldelico.com/pipermail/gta04-owner/attachments/20130106/fa0fbe3d/attachment.bin>
-------------- next part --------------

I think this will be easier than the Ruby code to integrate in such a
way that I can leave it running all the time without draining the
battery.

To complete such an integration, and hopefully help understand the modem
reset scenarios, I plan now to modify the program so that (a) it saves
the logs into a circular memory buffer, instead of printing them out,
and (b) there is some kind of trigger, probably a signal, that causes
the problem to dump that circular buffer to file and then exit.  Then
when the OS detects a modem-not-responding state, it can generate that
trigger and hopefully we get a useful set of logs to look at.

Any thoughts or other ideas on this?

Thanks,
        Neil


More information about the Gta04-owner mailing list