Project

General

Profile

Actions

Bug #1742

closed

Regression in egprs patch series

Added by pierre.baudry almost 8 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
High
Assignee:
Target version:
-
Start date:
06/02/2016
Due date:
% Done:

0%

Spec Reference:

Description

Original mailing list thread : http://lists.osmocom.org/pipermail/openbsc/2016-May/009125.html / http://lists.osmocom.org/pipermail/openbsc/2016-June/009329.html

I haven't been able to use gprs service since egprs merge (4f8438a6cd0f34bb22493b13154e382983bbda01).

The first issue is the T6169 timeout during TBF assignment. A bissection showed that commit f1a7b8fc6651f92a8b7f3f27b7ca05d07f4e44e0 introduced this specific bug ; but even with this commit reverted, the gprs service is still unreliable.

I am now bissecting d87e1d6ab747423d3668c74d16201a5d967accf0..f1a7b8fc6651f92a8b7f3f27b7ca05d07f4e44e0 and testing at each step connection and reliability on a end user device.

un-duplicating issues:

  • Please refer to #1756 for why the WAIT_ASSIGN state in f1a7b8fc66 breaks GPRS completely.
  • Discuss reliability after revert of f1a7b8fc66 here.

Related issues

Related to OsmoPCU - Bug #1756: regression: "tbf: Add state WAIT_ASSIGN"Closedlaforge06/16/2016

Actions
Related to OsmoGSMTester - Feature #2820: test GPRS with two (or more) subscribersResolvedpespin01/07/2018

Actions
Related to OsmoPCU - Bug #2890: OsmoPCU TTCN-3 test suite not executed by jenkinsResolvedlaforge01/27/2018

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)