Project

General

Profile

Bug #4327

remsim-client: Assert failed client rspro_util:360

Added by laforge 10 months ago. Updated 8 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
remsim-client
Target version:
-
Start date:
12/13/2019
Due date:
% Done:

100%

Spec Reference:

Description

I just aw this on our end-to-end test setup after upgrading to cardem 0.7.0:

root@remsimtest:~/simtrace2# osmo-remsim-client-st2 --usb-vendor 1d50 --usb-product 4004 --usb-config 1 --usb-interface 0 --usb-altesetting 0 -H 2-1.1
simtrace2-remsim-client - Remote SIM card client for SIMtrace
(C) 2010-2017, Harald Welte <laforge@gnumonks.org>
(C) 2018, sysmocom -s.f.m.c. GmbH, Author: Kevin Redon <kredon@sysmocom.de>

osmo-remsim-client-st2: unrecognized option '--usb-altesetting'
<0000> fsm.c:461 RSPRO_CLIENT(server)[0x558058b3ec90]{INIT}: Allocated
<0000> fsm.c:461 BANKD_CONN(bankd)[0x558058b38d70]{INIT}: Allocated
SIMtrace <- 01 05 00 00 00 00 09 00 01 
SIMtrace <- 02 02 00 00 00 00 09 00 01 
SIMtrace <= cardem_request_set_atr(3b 00 )
SIMtrace <- 01 02 00 00 00 00 0b 00 02 3b 00 
SIMtrace <- 02 01 00 00 00 00 0b 00 02 2c 01 
Entering main loop
<0000> rspro_client_fsm.c:114 RSPRO_CLIENT(server)[0x558058b3ec90]{INIT}: RSPRO link to 127.0.0.1:9998 DOWN
<0000> rspro_client_fsm.c:116 RSPRO_CLIENT(server)[0x558058b3ec90]{INIT}: Received Event SRVC_E_TCP_DOWN
<0000> rspro_client_fsm.c:227 RSPRO_CLIENT(server)[0x558058b3ec90]{INIT}: state_chg to REESTABLISH
<0000> rspro_client_fsm.c:114 RSPRO_CLIENT(server)[0x558058b3ec90]{REESTABLISH}: RSPRO link to 127.0.0.1:9998 DOWN
<0000> rspro_client_fsm.c:116 RSPRO_CLIENT(server)[0x558058b3ec90]{REESTABLISH}: Received Event SRVC_E_TCP_DOWN
SIMtrace -> 01 06 00 00 00 00 13 00 01 00 00 00 05 00 a0 a4 00 00 02 
SIMtrace => DATA: flags=1, a0 a4 00 00 02 : CLA=a0 INS=a4 P1=00 P2=00 P3=02; case=4, lc=2(0), le=0(0)
SIMtrace <= cardem_request_pb_and_rx(a4, 2)
SIMtrace <- 01 01 00 00 00 00 0f 00 08 00 00 00 01 00 a4 
SIMtrace -> 01 06 00 00 00 00 10 00 02 00 00 00 02 00 7f 20 
SIMtrace => DATA: flags=2, 7f 20 : CLA=a0 INS=a4 P1=00 P2=00 P3=02; case=4, lc=2(2), le=0(0)
Assert failed client rspro_util.c:360
backtrace() returned 6 addresses
/usr/lib/x86_64-linux-gnu/libosmocore.so.12(osmo_panic+0xcb) [0x7f0e3d7f8a6b]
/usr/lib/x86_64-linux-gnu/libosmo-rspro.so.1(rspro_gen_TpduModem2Card+0xcf) [0x7f0e3d7b833f]
osmo-remsim-client-st2(+0x4159) [0x558056c2e159]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7f0e3d3e909b]
osmo-remsim-client-st2(+0x44ca) [0x558056c2e4ca]
Aborted

History

#1 Updated by laforge 10 months ago

  • Subject changed from remsim-client: Assert failed client rsprop_util:360 to remsim-client: Assert failed client rspro_util:360

#2 Updated by laforge 10 months ago

This happens if the client doesn't yet have a connection to the remsim-server.

The proper solution is likely to defer "activating" the card-emulation before a connection to the server, and/or a connection to the bankd is established. Right now remsim-client is doing this unconditionally at startup.

#3 Updated by laforge 8 months ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

This should be fixed by the new main_fsm approach of current osmo-remsim-client.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)