BRANCH_CImasterosmo-ci.git branch BRANCH_CIStringParameterDefinitionCOMMENT_TYPEset by gerrit verification pipeline jobCOMMENT_TYPEStringParameterDefinitionDISTROset by gerrit verification pipeline jobDISTROStringParameterDefinitionGERRIT_BRANCHset by gerrit verification pipeline jobGERRIT_BRANCHStringParameterDefinitionGERRIT_CHANGE_NUMBERset by gerrit verification pipeline jobGERRIT_CHANGE_NUMBERStringParameterDefinitionGERRIT_HOSTset by gerrit verification pipeline jobGERRIT_HOSTStringParameterDefinitionGERRIT_PATCHSET_NUMBERset by gerrit verification pipeline jobGERRIT_PATCHSET_NUMBERStringParameterDefinitionGERRIT_PATCHSET_REVISIONset by gerrit verification pipeline jobGERRIT_PATCHSET_REVISIONStringParameterDefinitionGERRIT_PATCHSET_UPLOADER_NAMEset by gerrit verification pipeline jobGERRIT_PATCHSET_UPLOADER_NAMEStringParameterDefinitionGERRIT_PORTset by gerrit verification pipeline jobGERRIT_PORTStringParameterDefinitionGERRIT_PROJECTset by gerrit verification pipeline jobGERRIT_PROJECTStringParameterDefinitionGERRIT_REFSPECset by gerrit verification pipeline jobGERRIT_REFSPECStringParameterDefinitionGERRIT_REPO_URLset by gerrit verification pipeline jobGERRIT_REPO_URLStringParameterDefinitionPIPELINE_BUILD_URLset by gerrit verification pipeline jobPIPELINE_BUILD_URLStringParameterDefinitionPROJECT_NAMEset by gerrit verification pipeline jobPROJECT_NAMEStringParameterDefinitionhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d-build/Build job of CI for patches sent to <a href="https://gerrit.osmocom.org/#/q/status:open+project:osmo-e1d">osmo-e1d</a> <br/><br/> <b>Auto-generated using Jenkins Job Builder. DO NOT EDIT MANUALLY!</b> <!-- Managed by Jenkins Job Builder -->gerrit-osmo-e1d-buildgerrit-osmo-e1d-buildgerrit-osmo-e1d-buildgerrit-osmo-e1d-buildhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d-build/trueStarted by upstream project "gerrit-osmo-e1d" build number 146146gerrit-osmo-e1djob/gerrit-osmo-e1d/COMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42681GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION1097edd1885413b335a786e71f18a3ba1733b804GERRIT_PATCHSET_UPLOADER_NAMEfalconiaGERRIT_PORT29418GERRIT_PROJECTosmo-e1dGERRIT_REFSPECrefs/changes/81/42681/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-e1dPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d/146/PROJECT_NAMEosmo-e1dBRANCH_CImaster000045395453951.00722672261461097edd1885413b335a786e71f18a3ba1733b8041097edd1885413b335a786e71f18a3ba1733b804master1097edd1885413b335a786e71f18a3ba1733b8041097edd1885413b335a786e71f18a3ba1733b804master1097edd1885413b335a786e71f18a3ba1733b8041097edd1885413b335a786e71f18a3ba1733b804masterssh://jenkins@gerrit.osmocom.org:29418/osmo-e1dfalse#1464539545395gerrit-osmo-e1d-build #146146falsefalse14699473SUCCESS1777170240682https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d-build/146/src/e1d.h1097edd1885413b335a786e71f18a3ba1733b8041777168625000https://jenkins.osmocom.org/jenkins/user/falconfalconfalcon@freecalypso.orgHDLC timeslots: fix Rx of maximum-sized frames E1D protocol sets the maximum permitted size of an HDLC frame to 264 bytes of useful payload, not counting the 2 bytes of FCS. This limit is fair enough, as it matches GSM TS 08.56, the primary intended application. However, osmo_isdnhdlc engine used internally by the daemon requires an Rx buffer 2 bytes larger than the maximum payload length, for temporary storage of FCS bytes: by the nature of HDLC, a receiver has no way of identifying FCS bytes as such until after they have been received and stored in the Rx buffer. This bug was caught when bringing up OsmoBSC with Nokia Flexi Multiradio BTS. This BTS emits some long OML messages that get broken into segments, with each not-last segment traveling over HDLC as a maximum-sized frame - and these frames then get dropped by osmo-e1d, causing further breakage downstream. Change-Id: I479e8fe5118c8eb7d4e6b16b49047a3278bc9808 2026-04-26 01:57:05 +00001097edd1885413b335a786e71f18a3ba1733b804HDLC timeslots: fix Rx of maximum-sized frameseditsrc/e1d.hgithttps://jenkins.osmocom.org/jenkins/user/falconfalcon146https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/146/blueStarted by upstream project "gerrit-osmo-e1d" build number 146146gerrit-osmo-e1djob/gerrit-osmo-e1d/COMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42681GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION1097edd1885413b335a786e71f18a3ba1733b804GERRIT_PATCHSET_UPLOADER_NAMEfalconiaGERRIT_PORT29418GERRIT_PROJECTosmo-e1dGERRIT_REFSPECrefs/changes/81/42681/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-e1dPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d/146/PROJECT_NAMEosmo-e1dBRANCH_CImaster000045395453951.00722672261461097edd1885413b335a786e71f18a3ba1733b8041097edd1885413b335a786e71f18a3ba1733b804master1097edd1885413b335a786e71f18a3ba1733b8041097edd1885413b335a786e71f18a3ba1733b804master1097edd1885413b335a786e71f18a3ba1733b8041097edd1885413b335a786e71f18a3ba1733b804masterssh://jenkins@gerrit.osmocom.org:29418/osmo-e1dfalse#1464539545395gerrit-osmo-e1d-build #146146falsefalse14699473SUCCESS1777170240682https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d-build/146/src/e1d.h1097edd1885413b335a786e71f18a3ba1733b8041777168625000https://jenkins.osmocom.org/jenkins/user/falconfalconfalcon@freecalypso.orgHDLC timeslots: fix Rx of maximum-sized frames E1D protocol sets the maximum permitted size of an HDLC frame to 264 bytes of useful payload, not counting the 2 bytes of FCS. This limit is fair enough, as it matches GSM TS 08.56, the primary intended application. However, osmo_isdnhdlc engine used internally by the daemon requires an Rx buffer 2 bytes larger than the maximum payload length, for temporary storage of FCS bytes: by the nature of HDLC, a receiver has no way of identifying FCS bytes as such until after they have been received and stored in the Rx buffer. This bug was caught when bringing up OsmoBSC with Nokia Flexi Multiradio BTS. This BTS emits some long OML messages that get broken into segments, with each not-last segment traveling over HDLC as a maximum-sized frame - and these frames then get dropped by osmo-e1d, causing further breakage downstream. Change-Id: I479e8fe5118c8eb7d4e6b16b49047a3278bc9808 2026-04-26 01:57:05 +00001097edd1885413b335a786e71f18a3ba1733b804HDLC timeslots: fix Rx of maximum-sized frameseditsrc/e1d.hgithttps://jenkins.osmocom.org/jenkins/user/falconfalcon146https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/146/Build stability: No recent builds failed.icon-health-80plushealth-80plus.png100falsefalseStarted by upstream project "gerrit-osmo-e1d" build number 146146gerrit-osmo-e1djob/gerrit-osmo-e1d/COMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42681GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION1097edd1885413b335a786e71f18a3ba1733b804GERRIT_PATCHSET_UPLOADER_NAMEfalconiaGERRIT_PORT29418GERRIT_PROJECTosmo-e1dGERRIT_REFSPECrefs/changes/81/42681/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-e1dPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d/146/PROJECT_NAMEosmo-e1dBRANCH_CImaster000045395453951.00722672261461097edd1885413b335a786e71f18a3ba1733b8041097edd1885413b335a786e71f18a3ba1733b804master1097edd1885413b335a786e71f18a3ba1733b8041097edd1885413b335a786e71f18a3ba1733b804master1097edd1885413b335a786e71f18a3ba1733b8041097edd1885413b335a786e71f18a3ba1733b804masterssh://jenkins@gerrit.osmocom.org:29418/osmo-e1dfalse#1464539545395gerrit-osmo-e1d-build #146146falsefalse14699473SUCCESS1777170240682https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d-build/146/src/e1d.h1097edd1885413b335a786e71f18a3ba1733b8041777168625000https://jenkins.osmocom.org/jenkins/user/falconfalconfalcon@freecalypso.orgHDLC timeslots: fix Rx of maximum-sized frames E1D protocol sets the maximum permitted size of an HDLC frame to 264 bytes of useful payload, not counting the 2 bytes of FCS. This limit is fair enough, as it matches GSM TS 08.56, the primary intended application. However, osmo_isdnhdlc engine used internally by the daemon requires an Rx buffer 2 bytes larger than the maximum payload length, for temporary storage of FCS bytes: by the nature of HDLC, a receiver has no way of identifying FCS bytes as such until after they have been received and stored in the Rx buffer. This bug was caught when bringing up OsmoBSC with Nokia Flexi Multiradio BTS. This BTS emits some long OML messages that get broken into segments, with each not-last segment traveling over HDLC as a maximum-sized frame - and these frames then get dropped by osmo-e1d, causing further breakage downstream. Change-Id: I479e8fe5118c8eb7d4e6b16b49047a3278bc9808 2026-04-26 01:57:05 +00001097edd1885413b335a786e71f18a3ba1733b804HDLC timeslots: fix Rx of maximum-sized frameseditsrc/e1d.hgithttps://jenkins.osmocom.org/jenkins/user/falconfalcon146https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/146/Started by upstream project "gerrit-osmo-e1d" build number 146146gerrit-osmo-e1djob/gerrit-osmo-e1d/COMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42681GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION1097edd1885413b335a786e71f18a3ba1733b804GERRIT_PATCHSET_UPLOADER_NAMEfalconiaGERRIT_PORT29418GERRIT_PROJECTosmo-e1dGERRIT_REFSPECrefs/changes/81/42681/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-e1dPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d/146/PROJECT_NAMEosmo-e1dBRANCH_CImaster000045395453951.00722672261461097edd1885413b335a786e71f18a3ba1733b8041097edd1885413b335a786e71f18a3ba1733b804master1097edd1885413b335a786e71f18a3ba1733b8041097edd1885413b335a786e71f18a3ba1733b804master1097edd1885413b335a786e71f18a3ba1733b8041097edd1885413b335a786e71f18a3ba1733b804masterssh://jenkins@gerrit.osmocom.org:29418/osmo-e1dfalse#1464539545395gerrit-osmo-e1d-build #146146falsefalse14699473SUCCESS1777170240682https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d-build/146/src/e1d.h1097edd1885413b335a786e71f18a3ba1733b8041777168625000https://jenkins.osmocom.org/jenkins/user/falconfalconfalcon@freecalypso.orgHDLC timeslots: fix Rx of maximum-sized frames E1D protocol sets the maximum permitted size of an HDLC frame to 264 bytes of useful payload, not counting the 2 bytes of FCS. This limit is fair enough, as it matches GSM TS 08.56, the primary intended application. However, osmo_isdnhdlc engine used internally by the daemon requires an Rx buffer 2 bytes larger than the maximum payload length, for temporary storage of FCS bytes: by the nature of HDLC, a receiver has no way of identifying FCS bytes as such until after they have been received and stored in the Rx buffer. This bug was caught when bringing up OsmoBSC with Nokia Flexi Multiradio BTS. This BTS emits some long OML messages that get broken into segments, with each not-last segment traveling over HDLC as a maximum-sized frame - and these frames then get dropped by osmo-e1d, causing further breakage downstream. Change-Id: I479e8fe5118c8eb7d4e6b16b49047a3278bc9808 2026-04-26 01:57:05 +00001097edd1885413b335a786e71f18a3ba1733b804HDLC timeslots: fix Rx of maximum-sized frameseditsrc/e1d.hgithttps://jenkins.osmocom.org/jenkins/user/falconfalcon146https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/146/Started by upstream project "gerrit-osmo-e1d" build number 146146gerrit-osmo-e1djob/gerrit-osmo-e1d/COMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42681GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION1097edd1885413b335a786e71f18a3ba1733b804GERRIT_PATCHSET_UPLOADER_NAMEfalconiaGERRIT_PORT29418GERRIT_PROJECTosmo-e1dGERRIT_REFSPECrefs/changes/81/42681/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-e1dPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d/146/PROJECT_NAMEosmo-e1dBRANCH_CImaster000045395453951.00722672261461097edd1885413b335a786e71f18a3ba1733b8041097edd1885413b335a786e71f18a3ba1733b804master1097edd1885413b335a786e71f18a3ba1733b8041097edd1885413b335a786e71f18a3ba1733b804master1097edd1885413b335a786e71f18a3ba1733b8041097edd1885413b335a786e71f18a3ba1733b804masterssh://jenkins@gerrit.osmocom.org:29418/osmo-e1dfalse#1464539545395gerrit-osmo-e1d-build #146146falsefalse14699473SUCCESS1777170240682https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d-build/146/src/e1d.h1097edd1885413b335a786e71f18a3ba1733b8041777168625000https://jenkins.osmocom.org/jenkins/user/falconfalconfalcon@freecalypso.orgHDLC timeslots: fix Rx of maximum-sized frames E1D protocol sets the maximum permitted size of an HDLC frame to 264 bytes of useful payload, not counting the 2 bytes of FCS. This limit is fair enough, as it matches GSM TS 08.56, the primary intended application. However, osmo_isdnhdlc engine used internally by the daemon requires an Rx buffer 2 bytes larger than the maximum payload length, for temporary storage of FCS bytes: by the nature of HDLC, a receiver has no way of identifying FCS bytes as such until after they have been received and stored in the Rx buffer. This bug was caught when bringing up OsmoBSC with Nokia Flexi Multiradio BTS. This BTS emits some long OML messages that get broken into segments, with each not-last segment traveling over HDLC as a maximum-sized frame - and these frames then get dropped by osmo-e1d, causing further breakage downstream. Change-Id: I479e8fe5118c8eb7d4e6b16b49047a3278bc9808 2026-04-26 01:57:05 +00001097edd1885413b335a786e71f18a3ba1733b804HDLC timeslots: fix Rx of maximum-sized frameseditsrc/e1d.hgithttps://jenkins.osmocom.org/jenkins/user/falconfalcon146https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/146/Started by upstream project "gerrit-osmo-e1d" build number 146146gerrit-osmo-e1djob/gerrit-osmo-e1d/COMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42681GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION1097edd1885413b335a786e71f18a3ba1733b804GERRIT_PATCHSET_UPLOADER_NAMEfalconiaGERRIT_PORT29418GERRIT_PROJECTosmo-e1dGERRIT_REFSPECrefs/changes/81/42681/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-e1dPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d/146/PROJECT_NAMEosmo-e1dBRANCH_CImaster000045395453951.00722672261461097edd1885413b335a786e71f18a3ba1733b8041097edd1885413b335a786e71f18a3ba1733b804master1097edd1885413b335a786e71f18a3ba1733b8041097edd1885413b335a786e71f18a3ba1733b804master1097edd1885413b335a786e71f18a3ba1733b8041097edd1885413b335a786e71f18a3ba1733b804masterssh://jenkins@gerrit.osmocom.org:29418/osmo-e1dfalse#1464539545395gerrit-osmo-e1d-build #146146falsefalse14699473SUCCESS1777170240682https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d-build/146/src/e1d.h1097edd1885413b335a786e71f18a3ba1733b8041777168625000https://jenkins.osmocom.org/jenkins/user/falconfalconfalcon@freecalypso.orgHDLC timeslots: fix Rx of maximum-sized frames E1D protocol sets the maximum permitted size of an HDLC frame to 264 bytes of useful payload, not counting the 2 bytes of FCS. This limit is fair enough, as it matches GSM TS 08.56, the primary intended application. However, osmo_isdnhdlc engine used internally by the daemon requires an Rx buffer 2 bytes larger than the maximum payload length, for temporary storage of FCS bytes: by the nature of HDLC, a receiver has no way of identifying FCS bytes as such until after they have been received and stored in the Rx buffer. This bug was caught when bringing up OsmoBSC with Nokia Flexi Multiradio BTS. This BTS emits some long OML messages that get broken into segments, with each not-last segment traveling over HDLC as a maximum-sized frame - and these frames then get dropped by osmo-e1d, causing further breakage downstream. Change-Id: I479e8fe5118c8eb7d4e6b16b49047a3278bc9808 2026-04-26 01:57:05 +00001097edd1885413b335a786e71f18a3ba1733b804HDLC timeslots: fix Rx of maximum-sized frameseditsrc/e1d.hgithttps://jenkins.osmocom.org/jenkins/user/falconfalcon146https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/146/147BRANCH_CImasterosmo-ci.git branch BRANCH_CIStringParameterDefinitionCOMMENT_TYPEset by gerrit verification pipeline jobCOMMENT_TYPEStringParameterDefinitionDISTROset by gerrit verification pipeline jobDISTROStringParameterDefinitionGERRIT_BRANCHset by gerrit verification pipeline jobGERRIT_BRANCHStringParameterDefinitionGERRIT_CHANGE_NUMBERset by gerrit verification pipeline jobGERRIT_CHANGE_NUMBERStringParameterDefinitionGERRIT_HOSTset by gerrit verification pipeline jobGERRIT_HOSTStringParameterDefinitionGERRIT_PATCHSET_NUMBERset by gerrit verification pipeline jobGERRIT_PATCHSET_NUMBERStringParameterDefinitionGERRIT_PATCHSET_REVISIONset by gerrit verification pipeline jobGERRIT_PATCHSET_REVISIONStringParameterDefinitionGERRIT_PATCHSET_UPLOADER_NAMEset by gerrit verification pipeline jobGERRIT_PATCHSET_UPLOADER_NAMEStringParameterDefinitionGERRIT_PORTset by gerrit verification pipeline jobGERRIT_PORTStringParameterDefinitionGERRIT_PROJECTset by gerrit verification pipeline jobGERRIT_PROJECTStringParameterDefinitionGERRIT_REFSPECset by gerrit verification pipeline jobGERRIT_REFSPECStringParameterDefinitionGERRIT_REPO_URLset by gerrit verification pipeline jobGERRIT_REPO_URLStringParameterDefinitionPIPELINE_BUILD_URLset by gerrit verification pipeline jobPIPELINE_BUILD_URLStringParameterDefinitionPROJECT_NAMEset by gerrit verification pipeline jobPROJECT_NAMEStringParameterDefinitiontruefalsehudson.plugins.git.GitSCM--ffdefaulta1=default,a2=default,a3=default,a4=default,osmocom-gerritgerrit-osmo-e1d-build » a1=default,a2=default,a3=default,a4=default,osmocom-gerritgerrit-osmo-e1d-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrita1=default,a2=default,a3=default,a4=default,label=osmocom-gerrithttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/true146https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/146/blue146https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/146/Build stability: No recent builds failed.icon-health-80plushealth-80plus.png100falsefalse146https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/146/146https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/146/146https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/146/146https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-e1d-build/a1=default,a2=default,a3=default,a4=default,label=osmocom-gerrit/146/147truefalse