Comment 12 for bug 1467640

Revision history for this message
Tony Espy (awe) wrote :

Next clue... I disabled network-manager via a manual upstart override file, and rebooted. When I try to activate a GPRS context directly via the ofono script ( /usr/share/ofono/scripts ) 'activate-context', an error is returned:

Error activating /ril_0/context1: org.ofono.Error.Failed: Operation failed

At the same time, I see the following syslog error messages from ofono:

Jun 26 15:46:39 ofonod[1518]: ril_setup_data_call_cb: no DNS in context of type 1
Jun 26 15:46:39 ofonod[1518]: ril_gprs_context_deactivate_primary: couldn't remove call_list listener for apn: nxtgenphone.
Jun 26 15:46:39 ofonod[1518]: ril_deactivate_data_call_cb: reply failure for apn: nxtgenphone - GENERIC_FAILURE

Here's the corresponding ril trace:

ofonod[12095]: [0,0143]> RIL_REQUEST_SETUP_DATA_CALL (13,0,nxtgenphone,,,0,IP)
ofonod[12095]: [0,0143]< RIL_REQUEST_SETUP_DATA_CALL {version=9,num=1 [status=65535,retry=-1,cid=0,active=0,type=,ifname=,address=,dns=,gateways=]}

So the DATA_CALL is clearly failing.

And yet another clue from the logcat radio log whenever I try to activate a context:

E/RILQ ( 1160): (0/20): [main] qcril_data_request_setup_data_call: unable to get dsi hndl
E/RILQ ( 1160): (0/20): [main] qcril_data_request_setup_data_call: qcril_data_request_setup_data_call: EXIT with FAILURE
E/RILQ ( 1160): (0/20): [main] qcril_data_request_deactivate_data_call: no valid CID [-1] match found
E/RILQ ( 1160): (0/20): [main] qcril_data_response_generic_failure: qcril_data_response_generic_failure: ENTRY
E/RILQ ( 1160): (0/20): [main] qcril_data_response_generic_failure: qcril_data_response_generic_failure: EXIT
E/RILQ ( 1160): (0/20): [main] qcril_data_request_deactivate_data_call: qcril_data_request_deact_data_call: EXIT with err

This might be related to the following kernel error in the syslog:

Jun 26 15:42:46 ubuntu-phablet kernel: [ 13.529528] mipi_dsi_controller_cfg: DSI status=8 failed

My bet is that the data failure is related to the "unable to get dsi hndl" error, not the devices being re-named. The next thing we should try and reverting the device-rename to see allows data calls to be made.