Bug #3834
MS set_mode()/set_current_cs_*() inconsistent results
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
03/12/2019
Due date:
% Done:
0%
Spec Reference:
Description
Calling set_mode() for a given MS results in inconsistent settings:
- it's possible to set current DL MCS higher than max value
- EGPRS and EGPRS_GMSK have the same max DL MCS
- setting EGPRS* mode drops current/max MCS values to unknown
This should be fixed/documented and covered by unit tests. The incomplete implementation for the latter is available in https://gerrit.osmocom.org/c/osmo-pcu/+/13164 but it's not working properly yet due to ASAN bug cause by side effects in GprsMsStorage::ms_idle() which can delete MS which is triggered by GprsMs::detach_tbf() via GprsMs::update_status().
Related issues
History
#1 Updated by msuraev over 1 year ago
- Related to Bug #3827: BSSGP counter group errors in TBF test added
#2 Updated by msuraev over 1 year ago
- Related to Bug #3828: UL (M)CS update errors in TBF test added
#3 Updated by msuraev over 1 year ago
- Related to Bug #3395: Uplink CS/MCS control is broken osmo-pcu is used with osmo-bts-trx/osmo-trx added
#4 Updated by laforge over 1 year ago
- Assignee set to lynxis
