https://osmocom.org/https://osmocom.org/favicon.ico?16647414092018-03-24T14:48:39ZOpen Source Mobile CommunicationsOsmoBTS - Bug #2906: gsm_pchan2chan_nr asserts GSM_PCHAN_CCCH: lchan_nr == 0https://osmocom.org/issues/2906?journal_id=84912018-03-24T14:48:39Zlaforge
<ul><li><strong>Assignee</strong> set to <i>4368</i></li></ul> OsmoBTS - Bug #2906: gsm_pchan2chan_nr asserts GSM_PCHAN_CCCH: lchan_nr == 0https://osmocom.org/issues/2906?journal_id=86522018-04-04T08:43:48Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>4368</i> to <i>pespin</i></li></ul> OsmoBTS - Bug #2906: gsm_pchan2chan_nr asserts GSM_PCHAN_CCCH: lchan_nr == 0https://osmocom.org/issues/2906?journal_id=196452020-09-16T12:19:09Zpespin
<ul></ul><p>Related patch: <a class="external" href="https://gerrit.osmocom.org/c/openbsc/+/589">https://gerrit.osmocom.org/c/openbsc/+/589</a></p>
<p>It may be related to the fact that GSM_PCHAN_NONE is not being handled in the function (which can happen if dyn.pchan_is is passed when it contains GSM_PCHAN_NONE on GSM_PCHAN_TCH_F_TCH_H_PDCH channels.</p> OsmoBTS - Bug #2906: gsm_pchan2chan_nr asserts GSM_PCHAN_CCCH: lchan_nr == 0https://osmocom.org/issues/2906?journal_id=227732021-10-19T10:40:35Zpespin
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>90</i></li></ul><p>I submitted following patch:<br /><a class="external" href="https://gerrit.osmocom.org/c/osmo-bts/+/25825">https://gerrit.osmocom.org/c/osmo-bts/+/25825</a> gsm_pchan2chan_nr(): Properly assert if unexpected pchan is passed</p>
<p>Once merged Ithink this ticket can be closed.</p> OsmoBTS - Bug #2906: gsm_pchan2chan_nr asserts GSM_PCHAN_CCCH: lchan_nr == 0https://osmocom.org/issues/2906?journal_id=230172021-11-15T13:56:48Zpespin
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>90</i> to <i>100</i></li></ul><p>Merged, closing.</p>