software development of the OsmocomBB Open Source GSM BaseBand stack

Mobile testing branch

Hi all

I have built Osmocommbb with testing branch and I want to run Mobile app allowing me to make a call via my local network.

All goes well in the build but I am unable to register on my own network while using a genuine network sim.

This is output from my compal_e88/layer1.compalram.bin.

As you can see all looks good with signal levels fairly ok until this point and then level drops to -138 dbm and there it stays on all chanells.

I have tried this with 3 different sims and all is the same.

Can someone help?

Tom

    bat_compal_e88_chg_state=0
L1CTL_RESET_REQ: FULL!SIM Request (7): a0 a4 00 00 02 3f 00
SIM Response (2): 9f 20
SIM Request (5): a0 c0 00 00 20
SIM Response (34): 00 00 02 b7 3f 00 01 00 00 00 00 00 13 b3 05 0a 04 00 83 8a 83 8a 00 03 00 00 02 b7 00 00 02 b7 90 00
SIM Request (7): a0 a4 00 00 02 2f e2
SIM Response (2): 9f 0f
SIM Request (5): a0 c0 00 00 0f
SIM Response (17): 00 00 00 0a 2f e2 04 00 0f 00 ff 01 02 00 00 90 00
SIM Request (5): a0 b0 00 00 0a
SIM Response (12): 98 53 03 11 02 08 22 45 65 f6 90 00
SIM Request (7): a0 a4 00 00 02 7f 20
SIM Response (2): 9f 20
SIM Request (5): a0 c0 00 00 20
SIM Response (34): 00 00 00 00 7f 20 02 00 00 00 00 00 13 b3 00 23 04 00 83 8a 83 8a 00 03 00 00 02 b7 00 00 00 00 90 00
SIM Request (7): a0 a4 00 00 02 6f 07
SIM Response (2): 9f 0f
SIM Request (5): a0 c0 00 00 0f
SIM Response (17): 00 00 00 09 6f 07 04 00 14 00 14 01 02 00 00 90 00
SIM Request (5): a0 b0 00 00 09
SIM Response (11): 08 29 27 10 17 21 89 26 33 90 00
SIM Request (7): a0 a4 00 00 02 6f 7e
SIM Response (2): 9f 0f
SIM Request (5): a0 c0 00 00 0f
SIM Response (17): 00 00 00 0b 6f 7e 04 00 11 00 14 01 02 00 00 90 00
SIM Request (5): a0 b0 00 00 0b
SIM Response (13): ff ff ff ff 72 f2 60 ff fe 00 03 90 00
SIM Request (7): a0 a4 00 00 02 6f 20
SIM Response (2): 9f 0f
SIM Request (5): a0 c0 00 00 0f
SIM Response (17): 00 00 00 09 6f 20 04 00 11 00 44 01 02 00 00 90 00
SIM Request (5): a0 b0 00 00 09
SIM Response (11): ff ff ff ff ff ff ff ff 07 90 00
SIM Request (7): a0 a4 00 00 02 6f 30
SIM Response (2): 9f 0f
SIM Request (5): a0 c0 00 00 0f
SIM Response (17): 00 00 01 2c 6f 30 04 00 11 00 44 01 02 00 00 90 00
SIM Request (5): a0 b0 00 00 2c
SIM Response (46): 32 f4 51 02 f8 01 12 f4 60 12 f4 10 62 f2 20 02 f4 40 22 f2 01 02 f6 10 22 f8 10 72 f0 77 62 f8 10 42 f0 80 32 f8 10 02 f2 50 32 f2 90 00
BAT-ADC: 593   6   0   0 1023 353 327 277
    Charger at 51 mV.

PM MEAS: ARFCN=1016, 33   dBm at baseband, -104 dBm at RF
PM MEAS: ARFCN=1017, 33   dBm at baseband, -104 dBm at RF
PM MEAS: ARFCN=1018, 29   dBm at baseband, -108 dBm at RF
PM MEAS: ARFCN=1019, 29   dBm at baseband, -108 dBm at RF
PM MEAS: ARFCN=1020, 28   dBm at baseband, -109 dBm at RF
PM MEAS: ARFCN=1021, 29   dBm at baseband, -108 dBm at RF
PM MEAS: ARFCN=1022, 27   dBm at baseband, -110 dBm at RF
PM MEAS: ARFCN=1023, 39   dBm at baseband, -98 dBm at RF
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=1, flags=0x7)
Starting FCCH RecognitionFB0 (3859:4): TOA= 3792, Power= -88dBm, Angle=-1361Hz
DSP Error Status: 256
FB1 (3869:8): TOA= 8751, Power= -88dBm, Angle= -36Hz
fn_offset=3867 (fn=3869 + attempt=8 + ntdma = 6)
delay=8 (fn_offset=3867 + 11 - fn=3869 - 1
scheduling next FB/SB detection task with delay 8
=>FB @ FNR 3867 fn_offset=3867 qbits=4820
Synchronize_TDMA
LOST 3711!
DSP Error Status: 256
DSP Error Status: 264
L1CTL_RESET_REQ: FULL!LOST 1893!
L1CTL_FBSB_REQ (arfcn=981, flags=0x7)
Starting FCCH RecognitionLOST 1857!
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=71, flags=0x7)
Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=993, flags=0x7)
Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!LOST 1899!
L1CTL_FBSB_REQ (arfcn=979, flags=0x7)
Starting FCCH RecognitionLOST 1851!
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=4, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
BAT-ADC: 590   6   0   0 1023 356 330 277
    Charger at 51 mV.
    Battery at 4033 mV.
    Charging at 0 mA.
    Battery capacity is 100%.
    Battery range is 3199..3999 mV.
    Battery full at 468 LSB .. full at 585 LSB
    Charging at 239 LSB (204 mA).
    BCICTL2=0x3ff
    battery-info.flags=0x00000000
    bat_compal_e88_chg_state=0
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=1023, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!LOST 1900!
L1CTL_FBSB_REQ (arfcn=980, flags=0x7)
Starting FCCH RecognitionLOST 1850!
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=78, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=53, flags=0x7)
LOST 1880!
Starting FCCH RecognitionLOST 1870!
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=69, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=94, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=57, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=985, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=970, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=45, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=43, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=33, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=7, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=988, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=971, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=969, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=42, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=40, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=32, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
BAT-ADC: 592   6   0   0 1023 353 327 270
    Charger at 51 mV.
    Battery at 4047 mV.
    Charging at 0 mA.
    Battery capacity is 100%.
    Battery range is 3199..3999 mV.
    Battery full at 468 LSB .. full at 585 LSB
    Charging at 239 LSB (204 mA).
    BCICTL2=0x3ff
    battery-info.flags=0x00000000
    bat_compal_e88_chg_state=0
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=85, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=55, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=47, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=28, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=5, flags=0x7)
Starting FCCH RecognitionDSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
DSP Error Status: 8
L1CTL_RESET_REQ: FULL!L1CTL_PM_REQ start=0 end=124
DSP Error Status: 8
PM MEAS: ARFCN=0, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=1, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=2, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=3, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=4, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=5, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=6, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=7, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=8, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=9, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=10, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=11, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=12, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=13, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=14, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=15, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=16, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=17, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=18, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=19, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=20, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=21, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=22, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=23, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=24, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=25, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=26, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=27, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=28, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8
PM MEAS: ARFCN=29, 0    dBm at baseband, -138 dBm at RF
DSP Error Status: 8

Re: Mobile testing branch

Hi,

> I have built Osmocommbb with testing branch and I want to run Mobile app
> allowing me to make a call via my local network.
> All goes well in the build but I am unable to register on my own network
> while using a genuine network sim.
> This is output from my  compal_e88/layer1.compalram.bin.
> As you can see all looks good with signal levels fairly ok until this point
> and then level drops to -138 dbm and there it stays on all chanells.
> I have tried this with 3 different sims and all is the same.
> Can someone help?

Use master, not testing.

Re: Mobile testing branch

Hi I have same problem.

But in case with master with TX enabled, it just hang up ?

OsmocomBB> enable

OsmocomBB# sim reader 1

OsmocomBB#

% (MS 1)

% Searching network...

% (MS 1)

% Trying to registering with network...

Connection closed by foreign host.

????

msgb(0x1638020): Not enough headroom msgb_push (4271669080 < 7)

backtrace() returned 10 addresses

/usr/local/lib/libosmocore.so.4(osmo_panic+0xb9) [0x7f2b4ea57929]

/usr/local/lib/libosmogsm.so.5(lapdm_phsap_up+0x16f) [0x7f2b4e62378f]

./mobile() [0x43981c]

./mobile() [0x439fce]

/usr/local/lib/libosmocore.so.4(osmo_wqueue_bfd_cb+0x93) [0x7f2b4ea550d3]

/usr/local/lib/libosmocore.so.4(osmo_select_main+0x1b1) [0x7f2b4ea54171]

./mobile() [0x404be7]

/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f2b4e099eed]

./mobile() [0x404d59]

Signal 6 received.

full talloc report on 'layer2 context' (total 40828 bytes in 53 blocks)

Layer2 contains 424 bytes in 1 blocks (ref 0) 0x1638020

GSM 04.08 L3 contains 456 bytes in 1 blocks (ref 0) 0x1639e10

struct gsm_sub_plmn_list contains 24 bytes in 1 blocks (ref 0) 0x1638930

struct gsm_sub_plmn_list contains 24 bytes in 1 blocks (ref 0) 0x16388c0

struct gsm_sub_plmn_list contains 24 bytes in 1 blocks (ref 0) 0x1638850

struct gsm_sub_plmn_list contains 24 bytes in 1 blocks (ref 0) 0x16387e0

struct gsm_sub_plmn_list contains 24 bytes in 1 blocks (ref 0) 0x1638770

struct gsm_sub_plmn_list contains 24 bytes in 1 blocks (ref 0) 0x1638700

struct gsm_sub_plmn_list contains 24 bytes in 1 blocks (ref 0) 0x1638690

struct gsm_sub_plmn_list contains 24 bytes in 1 blocks (ref 0) 0x1638620

struct gsm_sub_plmn_list contains 24 bytes in 1 blocks (ref 0) 0x16385b0

struct gsm_sub_plmn_list contains 24 bytes in 1 blocks (ref 0) 0x1638540

struct gsm_sim_handler contains 32 bytes in 1 blocks (ref 0) 0x1634810

struct gsm_sim_handler contains 32 bytes in 1 blocks (ref 0) 0x1634890

struct gsm_sim_handler contains 32 bytes in 1 blocks (ref 0) 0x1634910

struct gsm48_sysinfo contains 1452 bytes in 1 blocks (ref 0) 0x1637970

struct gsm48_sysinfo contains 1452 bytes in 1 blocks (ref 0) 0x1637360

struct gsm48_sysinfo contains 1452 bytes in 1 blocks (ref 0) 0x1636d50

struct gsm48_sysinfo contains 1452 bytes in 1 blocks (ref 0) 0x1636740

struct gsm48_sysinfo contains 1452 bytes in 1 blocks (ref 0) 0x1635e60

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x1635dc0

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x1635d20

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x1635c80

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x1635be0

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x1635b40

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x1635aa0

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x1635a00

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x1635960

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x16358c0

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x1635820

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x1635780

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x16356e0

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x162d010

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x162cf70

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x162ced0

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x162ce30

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x162cd90

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x162ccf0

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x162d420

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x162d380

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x162d2e0

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x162d240

struct gsm322_neighbour contains 64 bytes in 1 blocks (ref 0) 0x162d1a0

struct gsm48_sysinfo contains 1452 bytes in 1 blocks (ref 0) 0x16350d0

telnet_connection contains 89 bytes in 2 blocks (ref 0) 0x1634bf0

struct telnet_connection contains 88 bytes in 1 blocks (ref 0) 0x1634c50

struct gsm322_ba_list contains 192 bytes in 1 blocks (ref 0) 0x1634fb0

struct gsm322_ba_list contains 192 bytes in 1 blocks (ref 0) 0x1634e90

struct gsm322_ba_list contains 192 bytes in 1 blocks (ref 0) 0x1634990

struct osmocom_ms contains 28704 bytes in 1 blocks (ref 0) 0x162d590

/root/.osmocom/bb contains 29 bytes in 1 blocks (ref 0) 0x15ca730

main.c:240 contains 29 bytes in 1 blocks (ref 0) 0x15ca6b0

Aborted

On Fri, Jul 25, 2014 at 12:54 PM, Sylvain Munaut <246tnt@gmail.com> wrote:

Hi,

> I have built Osmocommbb with testing branch and I want to run Mobile app
> allowing me to make a call via my local network.
> All goes well in the build but I am unable to register on my own network
> while using a genuine network sim.
> This is output from my compal_e88/layer1.compalram.bin.
> As you can see all looks good with signal levels fairly ok until this point
> and then level drops to -138 dbm and there it stays on all chanells.
> I have tried this with 3 different sims and all is the same.
> Can someone help?

Use master, not testing.

--

Milinko Isakovic, CEO
CS Network Solutions Limited

72 Blythe Road, West Kensington, London W14 0HB

London Switchboard: +442071933539

Belgrade Operations: +381112620152

Personal mobille: +381666666666

Web: www.cs-networks.net

--------------------------

This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. CS Networks shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. CS Networks does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference.

Re: Mobile testing branch

On Wed, Jul 30, 2014 at 10:54:39AM +0200, Milinko Isakovic wrote:
> Hi I have same problem.

Hi,

> msgb(0x1638020): Not enough headroom msgb_push (4271669080 < 7)
> backtrace() returned 10 addresses
> /usr/local/lib/libosmocore.so.4(osmo_panic+0xb9) [0x7f2b4ea57929]
> /usr/local/lib/libosmogsm.so.5(lapdm_phsap_up+0x16f) [0x7f2b4e62378f]
> ./mobile() [0x43981c]
> ./mobile() [0x439fce]
> /usr/local/lib/libosmocore.so.4(osmo_wqueue_bfd_cb+0x93) [0x7f2b4ea550d3]
> /usr/local/lib/libosmocore.so.4(osmo_select_main+0x1b1) [0x7f2b4ea54171]
> ./mobile() [0x404be7]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f2b4e099eed]
> ./mobile() [0x404d59]

we are still waiting for a patch. The LAPDm code is using l2h/l3h but
in rx_l1_rach_conf it is not initialized at all.

Patches welcome.

	holger

Re: Mobile testing branch

Hi,

On 07/30/2014 07:28 AM, Holger Hans Peter Freyther wrote:
> On Wed, Jul 30, 2014 at 10:54:39AM +0200, Milinko Isakovic wrote:
>> Hi I have same problem.
>
> Hi,
>
>> msgb(0x1638020): Not enough headroom msgb_push (4271669080 < 7)
>> backtrace() returned 10 addresses
>> /usr/local/lib/libosmocore.so.4(osmo_panic+0xb9) [0x7f2b4ea57929]
>> /usr/local/lib/libosmogsm.so.5(lapdm_phsap_up+0x16f) [0x7f2b4e62378f]
>> ./mobile() [0x43981c]
>> ./mobile() [0x439fce]
>> /usr/local/lib/libosmocore.so.4(osmo_wqueue_bfd_cb+0x93) [0x7f2b4ea550d3]
>> /usr/local/lib/libosmocore.so.4(osmo_select_main+0x1b1) [0x7f2b4ea54171]
>> ./mobile() [0x404be7]
>> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f2b4e099eed]
>> ./mobile() [0x404d59]
>
> we are still waiting for a patch. The LAPDm code is using l2h/l3h but
> in rx_l1_rach_conf it is not initialized at all.
>
> Patches welcome.
>
The attached patch works for me. Anything I've missed?

> 	holger
>

--

-- 
Igor Almeida

Attachment (0001-layer23-initialize-l2h-l3h-pointers.patch): text/x-diff, 807 bytes

Re: Mobile testing branch

On Thu, Aug 21, 2014 at 01:04:38AM -0300, Igor Almeida wrote:

Hi!

>  	dl = (struct l1ctl_info_dl *) msg->l1h;
> +	msg->l2h = msg->l3h = dl->payload;
>  

yes, looks fine. I had msg->l2h = msg->l3h = msg->tail but
dl->payload should probably work as well. I will leave it for
Sylvain/Andreas to comment.

thanks a lot for the patch

holger

Re: Mobile testing branch

On Fri, Aug 22, 2014 at 5:50 PM, Holger Hans Peter Freyther
<holger@freyther.de> wrote:
> On Thu, Aug 21, 2014 at 01:04:38AM -0300, Igor Almeida wrote:
>
> Hi!
>
>
>>       dl = (struct l1ctl_info_dl *) msg->l1h;
>> +     msg->l2h = msg->l3h = dl->payload;
>>
>
> yes, looks fine. I had msg->l2h = msg->l3h = msg->tail but
> dl->payload should probably work as well. I will leave it for
> Sylvain/Andreas to comment.
>
> thanks a lot for the patch

I'll give it a shot this week end when I have a osmocom-bb phone handy
and merge it.

Cheers,

   Sylvain

Re: Mobile testing branch

>>
>>>       dl = (struct l1ctl_info_dl *) msg->l1h;
>>> +     msg->l2h = msg->l3h = dl->payload;
>>>
>>
>> yes, looks fine. I had msg->l2h = msg->l3h = msg->tail but
>> dl->payload should probably work as well. I will leave it for
>> Sylvain/Andreas to comment.
>>
>> thanks a lot for the patch
>
> I'll give it a shot this week end when I have a osmocom-bb phone handy
> and merge it.

Merged thanks.

Sorry, it got delayed, life got in the way that weekend and I was just
reminded of it by someone having that issue in IRC ...

I think dl->payload makes sense since this is what's used to init it
in the other cases (like data_ind).

Cheers,

   Sylvain