Hi there,
I am sorry to bother you but I am really confused by recent experiment.
When I was doing the GSM sniffing I found that some of sms messages that
were sent continuesly were missing, I can only capture 50-60% of all test
messages. By analyzing wireshark data I found that osmocom program keeps
tracking packets(lapdm) once an Immediate Assignment captured and if at the
same time there comes another Immediate Assignment the program will miss
it.I think this is the reason why i lost some messages.So is there any
suggestions I can fix this up? Like using a backup phone to capture the
second Immediate Assignment during one period?
Thanks,
Swift
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/Missing-packet-when-sniffing-by-…
Sent from the baseband-devel mailing list archive at Nabble.com.
Sanchit,
You might want to consider applying this patch.
Ravi Sharan.
On Sun, Jan 25, 2015 at 2:43 PM,
<baseband-devel-request(a)lists.osmocom.org> wrote:
> Send baseband-devel mailing list submissions to
> baseband-devel(a)lists.osmocom.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.osmocom.org/mailman/listinfo/baseband-devel
> or, via email, send a message with subject or body 'help' to
> baseband-devel-request(a)lists.osmocom.org
>
> You can reach the person managing the list at
> baseband-devel-owner(a)lists.osmocom.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of baseband-devel digest..."
>
> Today's Topics:
>
> 1. Regarding Mobile Application of Osmocombb . Core Dumped.
> Ubuntu 14.04 (Sanchit Agarwal)
>
>
> ---------- Forwarded message ----------
> From: Sanchit Agarwal <sanchit.k.agarwal(a)gmail.com>
> To: baseband-devel(a)lists.osmocom.org
> Cc:
> Date: Wed, 21 Jan 2015 01:38:27 +0530
> Subject: Regarding Mobile Application of Osmocombb . Core Dumped. Ubuntu 14.04
> Hi
> I have compiled mobile app with tx support .
> i.e i have checked-out the testing branch .
>
> Layer 1 seems to be uploaded to the mobile phone successfully.
>
> But the program crashes every-time there is a successful connection with the network service provider.
>
> I am attaching my mobile.log and layer1.log file along for debugging.
>
> Hoping some one replies.
>
>
> " mmsgb(0x8955b0): Not enough headroom msgb_push (4285966792 < 7)
> errors
> Dropping frame with 66 bit errors
> Dropping frame with 65 bit errors
> Dropping frame with 58 bit errors
> Dropping frame with 56 bit errors
> LOSS counter for CCCH 57
> Dropping frame with 66 bit errors
> Dropping frame with 66 bit errors
> Dropping frame with 65 bit errors
> Dropping frame with 65 bit errors
> Dropping frame with 70 bit errors
> Dropping frame with 65 bit errors
> Dropping frame with 80 bit errors
> LOSS counter for CCCH 53
> Dropping frame with 61 bit errors
> Dropping frame with 76 bit errors
> Dropping frame with 57 bit errors
> Dropping frame with 67 bit errors
> Dropping frame with 58 bit errors
> Dropping frame with 72 bit errors
> Dropping frame with 63 bit errors
> Dropping frame with 70 bit errors
> LOSS counter for CCCH 49
> Dropping frame with 57 bit errors
> Dropping frame with 61 bit errors
> Dropping frame with 52 bit errors
> Dropping frame with 77 bit errors
> Dropping frame with 60 bit errors
> Dropping frame with 57 bit errors
> Dropping frame with 76 bit errors
> LOSS counter for CCCH 45
> Dropping frame with 70 bit errors
> Dropping frame with 57 bit errors
> Dropping frame with 65 bit errors
> Dropping frame with 46 bit errors
> Dropping frame with 65 bit errors
> Dropping frame with 46 bit errors
> Dropping frame with 70 bit errors
> Dropping frame with 77 bit errors
> LOSS counter for CCCH 46
> Dropping frame with 51 bit errors
> Dropping frame with 56 bit errors
> Dropping frame with 65 bit errors
> Dropping frame with 59 bit errors
> Dropping frame with 65 bit errors
> Dropping frame with 60 bit errors
> Dropping frame with 72 bit errors
> Dropping frame with 79 bit errors
> Dropping frame with 75 bit errors
> Dropping frame with 59 bit errors
> Dropping frame with 72 bit errors
> Dropping frame with 66 bit errors
> Dropping frame with 69 bit errors
> Dropping frame with 70 bit errors
> Dropping frame with 65 bit errors
> Dropping frame with 69 bit errors
> Dropping frame with 66 bit errors
> Dropping frame with 82 bit errors
> Dropping frame with 80 bit errors
> LOSS counter for CCCH 86
> Dropping frame with 67 bit errors
> Dropping frame with 63 bit errors
> Dropping frame with 69 bit errors
> Dropping frame with 69 bit errors
> Dropping frame with 66 bit errors
> Dropping frame with 76 bit errors
> Dropping frame with 63 bit errors
> LOSS counter for CCCH 87
> Dropping frame with 53 bit errors
> Dropping frame with 54 bit errors
> LOSS counter for CCCH 88
> LOSS counter for CCCH 89
> Dropping frame with 46 bit errors
> Dropping frame with 50 bit errors
> Dropping frame with 45 bit errors
> backtrace() returned 10 addresses
> /usr/local/lib/libosmocore.so.6(osmo_panic+0xbe) [0x7f3ccd0745ce]
> /usr/local/lib/libosmogsm.so.5(lapdm_phsap_up+0x18e) [0x7f3cccc3cc5e]
> ./mobile() [0x438c29]
> ./mobile() [0x4394cc]
> /usr/local/lib/libosmocore.so.6(osmo_wqueue_bfd_cb+0x73) [0x7f3ccd071b63]
> /usr/local/lib/libosmocore.so.6(osmo_select_main+0x18f) [0x7f3ccd070b9f]
> ./mobile() [0x4048bf]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f3ccc679ec5]
> ./mobile() [0x404a46]
> "
>
>
> there is core dumped after this error.
>
> _______________________________________________
> baseband-devel mailing list
> baseband-devel(a)lists.osmocom.org
> https://lists.osmocom.org/mailman/listinfo/baseband-devel
>
--
Ravi Sharan B A G.