This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/baseband-devel@lists.osmocom.org/.
Tim Ehlers osmocom at ehlers.infoOn Mon, 10 Dec 2012, Sylvain Munaut wrote: Hi Sylvain, >> Is there a way to somehow "reboot" or restart the layer1 by software? And if >> not, could that easily be implemented? > > Yes there is the L1CTL_RESET but I think shutdown/no shutdown already > sends that command (check the osmocon output) meaning the L1 is no > longer responding at all ... > > Does the osmocon console does anything at all when it's in that state > ? Does that phone have anything special ? (connected to a different > network or doing different things ?). now phone number 6 is crashed. I started the osmocon processes in a screen session. A lot of messages are loged now in the session like this: [...] FB1 (862461:1): TOA= 451, Power= -78dBm, Angle= 3182Hz fn_offset=862460 (fn=862461 + attempt=1 + ntdma = 0) delay=9 (fn_offset=862460 + 11 - fn=862461 - 1 scheduling next FB/SB detection task with delay 9 FB1 (862481:10): TOA=11703, Power= -78dBm, Angle= 3129Hz fn_offset=862480 (fn=862481 + attempt=10 + ntdma = 9) delay=9 (fn_offset=862480 + 11 - fn=862481 - 1 scheduling next FB/SB detection task with delay 9 FB1 (862501:10): TOA=11703, Power= -78dBm, Angle= 3135Hz fn_offset=862500 (fn=862501 + attempt=10 + ntdma = 9) delay=9 (fn_offset=862500 + 11 - fn=862501 - 1 scheduling next FB/SB detection task with delay 9 FB1 (862512:1): TOA= 451, Power= -78dBm, Angle= 3171Hz fn_offset=862511 (fn=862512 + attempt=1 + ntdma = 0) delay=9 (fn_offset=862511 + 11 - fn=862512 - 1 scheduling next FB/SB detection task with delay 9 FB1 (862532:10): TOA=11703, Power= -78dBm, Angle= 3113Hz fn_offset=862531 (fn=862532 + attempt=10 + ntdma = 9) delay=9 (fn_offset=862531 + 11 - fn=862532 - 1 scheduling next FB/SB detection task with delay 9 [...] And mobile says: OsmocomBB# show ms 6 MS '6' is up, service is limited IMEI: XXXXXXXXXXXX IMEISV: XXXXXXXXXXXXX IMEI generation: fixed automatic network selection state: A1 trying RPLMN MCC=262 MNC=07 (Germany, O2) cell selection state: C2 stored cell selection radio ressource layer state: idle mobility management layer state: MM idle, PLMN search I now restated the mobile process and deleted 6.ba. Now it says: OsmocomBB# show ms 6 MS '6' is up, service is limited IMEI: XXXXXXXXXXXX IMEISV: XXXXXXXXXXXXX IMEI generation: fixed automatic network selection state: A1 trying RPLMN MCC=262 MNC=07 (Germany, O2) cell selection state: C1 normal cell selection radio ressource layer state: idle mobility management layer state: MM idle, PLMN search shutdown/no shutdown doesn't change a thing. Now the question again: Could it be because of my hardware situation (special battery simulation with one power supply)? Or in other words has anybody running a steady service with osmocombb and experiences no problem over weeks? Thanks Tim