search

uw-ictd / colte

Community LTE Project
MIT License
59 stars 27 forks source link

MME Crash "corrupted double-linked list" #53

Closed matt9j closed 4 years ago

matt9j commented 5 years ago

Backtrace:

Aug 13 18:02:59 colte mme[848]: *** Error in `/usr/bin/mme': corrupted double-linked list: 0x00007f1fb80051e0 ***
Aug 13 18:02:59 colte mme[848]: ======= Backtrace: =========
Aug 13 18:02:59 colte mme[848]: /lib/x86_64-linux-gnu/libc.so.6(+0x70bfb)[0x7f204f9c5bfb]
Aug 13 18:02:59 colte mme[848]: /lib/x86_64-linux-gnu/libc.so.6(+0x76fc6)[0x7f204f9cbfc6]
Aug 13 18:02:59 colte mme[848]: /lib/x86_64-linux-gnu/libc.so.6(+0x7964c)[0x7f204f9ce64c]
Aug 13 18:02:59 colte mme[848]: /lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x54)[0x7f204f9cff64]
Aug 13 18:02:59 colte mme[848]: /usr/bin/mme(balloc+0x122)[0x55f0b34c7d63]
Aug 13 18:02:59 colte mme[848]: /usr/bin/mme(bvcformata+0xb0)[0x55f0b34cfc50]
Aug 13 18:02:59 colte mme[848]: /usr/bin/mme(log_message+0x4f7)[0x55f0b34bee44]
Aug 13 18:02:59 colte mme[848]: /usr/bin/mme(s1ap_is_ue_mme_id_in_list+0x87)[0x55f0b3454dd2]
Aug 13 18:02:59 colte mme[848]: /usr/bin/mme(s1ap_mme_handle_initial_context_setup_response+0xe9)[0x55f0b3458775]
Aug 13 18:02:59 colte mme[848]: /usr/bin/mme(s1ap_mme_handle_message+0x168)[0x55f0b3456d90]
Aug 13 18:02:59 colte mme[848]: /usr/bin/mme(s1ap_mme_thread+0x203)[0x55f0b345402d]
Aug 13 18:02:59 colte mme[848]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x74a4)[0x7f2051bd64a4]
Aug 13 18:02:59 colte mme[848]: /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f204fa3dd0f]

I don't have a pcap of the s1ap trace that causes the failure, but I'll start logging and see if I can catch it happening again.

spencersevilla commented 5 years ago

Kenneth saw a similar bug two weeks ago. Looking forward to a pcap, and in the meantime I will also attach his information to this bug.

On Aug 13, 2019, at 11:24, Matthew Johnson notifications@github.com wrote:

Backtrace:

Aug 13 18:02:59 colte mme[848]: Error in `/usr/bin/mme': corrupted double-linked list: 0x00007f1fb80051e0 Aug 13 18:02:59 colte mme[848]: ======= Backtrace: ========= Aug 13 18:02:59 colte mme[848]: /lib/x86_64-linux-gnu/libc.so.6(+0x70bfb)[0x7f204f9c5bfb] Aug 13 18:02:59 colte mme[848]: /lib/x86_64-linux-gnu/libc.so.6(+0x76fc6)[0x7f204f9cbfc6] Aug 13 18:02:59 colte mme[848]: /lib/x86_64-linux-gnu/libc.so.6(+0x7964c)[0x7f204f9ce64c] Aug 13 18:02:59 colte mme[848]: /lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x54)[0x7f204f9cff64] Aug 13 18:02:59 colte mme[848]: /usr/bin/mme(balloc+0x122)[0x55f0b34c7d63] Aug 13 18:02:59 colte mme[848]: /usr/bin/mme(bvcformata+0xb0)[0x55f0b34cfc50] Aug 13 18:02:59 colte mme[848]: /usr/bin/mme(log_message+0x4f7)[0x55f0b34bee44] Aug 13 18:02:59 colte mme[848]: /usr/bin/mme(s1ap_is_ue_mme_id_in_list+0x87)[0x55f0b3454dd2] Aug 13 18:02:59 colte mme[848]: /usr/bin/mme(s1ap_mme_handle_initial_context_setup_response+0xe9)[0x55f0b3458775] Aug 13 18:02:59 colte mme[848]: /usr/bin/mme(s1ap_mme_handle_message+0x168)[0x55f0b3456d90] Aug 13 18:02:59 colte mme[848]: /usr/bin/mme(s1ap_mme_thread+0x203)[0x55f0b345402d] Aug 13 18:02:59 colte mme[848]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x74a4)[0x7f2051bd64a4] Aug 13 18:02:59 colte mme[848]: /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f204fa3dd0f]

I don't have a pcap of the s1ap trace that causes the failure, but I'll start logging and see if I can catch it happening again.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

spencersevilla commented 4 years ago

migrating to open5gs