fso-abyss docs anywhere? (Was: GSM errors after 1024 fix)

Petr Vanek vanous at penguin.cz
Sun Oct 18 15:24:18 CEST 2009


>>  I get messages like 
>>[2009-10-18 07:51:27.107655] Signal : cid=4E91, lac=006A
>>[2009-10-18 07:52:45.145288] Signal : cid=4E7B, lac=006A
>>[2009-10-18 07:53:18.218122] Signal : cid=4E91, lac=006A
>>...
>>  So I guess my #1024 is not fixed :-(
>
>The three lines you quoted are not showing #1024. Again, frequent cell 
>_handovers_ are perfectly normal. #1024 is about dropping out of a
>cell, then recamping into it, e.g. it looks like that:
>
>[2009-10-18 07:51:27.107655] Signal : cid=4E91, lac=006A
>[2009-10-18 07:52:45.145288] Signal : cid=4E91, lac=006A
>[2009-10-18 07:53:18.218122] Signal : cid=4E91, lac=006A
>
>(NB: This compact debug output form is not optimal for recognizing
>#1024 anyways, you should rather watch for CSQ and CREG messages. If
>CSQ suddenly drops to 99 and you get thrown out of the cell, then it's
>100% clear you have #1024).

How about this output:

[2009-10-18 13:37:02.701925] Signal : cid=9E4A, lac=17A2
[2009-10-18 13:37:26.813505] Signal : cid=7149, lac=17A2
[2009-10-18 13:41:22.576405] Signal : cid=9E4A, lac=17A2
[2009-10-18 13:45:48.512750] Signal : cid=7149, lac=17A2
[2009-10-18 13:49:10.453532] Signal : cid=9E4A, lac=17A2

If there is a better way - script of determining whether the 1024 has
been dealt with correctly, it would be helpful...

thank you

Petr



 





More information about the community mailing list