ofonod segfaulting in a loop on n4

Bug #1206537 reported by Steve Langasek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
touch-preview-images
Invalid
Undecided
Unassigned
ofono (Ubuntu)
Invalid
Undecided
Tony Espy

Bug Description

On my n4, ofonod is crashing in a loop (ofono 1.12phablet10). Since this is an unofficial package, I can't submit the crash report to errors.u.c (and it currently wouldn't get retraced here anyway). But I can attach the apport crash file.

Revision history for this message
Steve Langasek (vorlon) wrote :
Tony Espy (awe)
Changed in ofono (Ubuntu):
assignee: nobody → Tony Espy (awe)
Revision history for this message
Tony Espy (awe) wrote :

@Steve

I can't make sense of the crash, which is a segfault caused by a strlen call in libdbus, however the rest of stack trace is corrupted.

Could you try to enable debug logging for onfod and then attach your syslog to the bug?

The other separate debug output that would help would be to stop both ofono and network-manager via upstart, then start ofonod in the foreground ( capturing it's output via script ) like this:

# OFONO_RIL_TRACE=y ofonod -n -P atmodem

and then if it doesn't crash at first, try enabling network-manager again via initctl.

Revision history for this message
Steve Langasek (vorlon) wrote :

here's the output from an ofono crash (which is immediate):

# OFONO_RIL_TRACE=y ofonod -n -P atmodem
ofonod[9085]: oFono version 1.12
ofonod[9085]: Excluding AT modem driver
ofonod[9085]: [UNSOL]< UNSOL_RIL_CONNECTED
ofonod[9085]: [0001]> RIL_REQUEST_GET_SIM_STATUS
ofonod[9085]: [0001]< RIL_REQUEST_GET_SIM_STATUS (card_state=1,universal_pin_state=0,gsm_umts_index=0,cdma_index=-1,ims_index=-1, [app_type=2,app_state=-1,perso_substate=2,aid_ptr=a0000000871002ff4994208903100000,app_label_ptr=,pin1_replaced=0,pin1=3,pin2=1],}
ofonod[9085]: [0002]> RIL_REQUEST_RADIO_POWER (1)
ofonod[9085]: [0002]< RIL_REQUEST_RADIO_POWER
ofonod[9085]: [0003]> RIL_REQUEST_GET_SIM_STATUS
ofonod[9085]: [0003]< RIL_REQUEST_GET_SIM_STATUS (card_state=1,universal_pin_state=0,gsm_umts_index=0,cdma_index=-1,ims_index=-1, [app_type=2,app_state=-1,perso_substate=2,aid_ptr=a0000000871002ff4994208903100000,app_label_ptr=,pin1_replaced=0,pin1=3,pin2=1],}
ofonod[9085]: [0004]> RIL_REQUEST_SIM_IO (cmd=0xC0,efid=0x2FE2,path=3F00,0,0,15,(null),pin2=(null),aid=a0000000871002ff4994208903100000)
ofonod[9085]: [0004]< RIL_REQUEST_SIM_IO (sw1=0x90,sw2=0x00,0000000a2fe2040000000005020000)
ofonod[9085]: [0005]> RIL_REQUEST_SIM_IO (cmd=0xB0,efid=0x2FE2,path=3F00,0,0,10,(null),pin2=(null),aid=a0000000871002ff4994208903100000)
ofonod[9085]: [0005]< RIL_REQUEST_SIM_IO (sw1=0x90,sw2=0x00,984403411774225623f3)
ofonod[9085]: [0006]> RIL_REQUEST_SIM_IO (cmd=0xC0,efid=0x6F05,path=3F007FFF,0,0,15,(null),pin2=(null),aid=a0000000871002ff4994208903100000)
ofonod[9085]: [0006]< RIL_REQUEST_SIM_IO failed GENERIC_FAILURE
ofonod[9085]: [0007]> RIL_REQUEST_SIM_IO (cmd=0xC0,efid=0x2F05,path=3F00,0,0,15,(null),pin2=(null),aid=a0000000871002ff4994208903100000)
ofonod[9085]: [0007]< RIL_REQUEST_SIM_IO (sw1=0x90,sw2=0x00,000000082f05040000000005020000)
ofonod[9085]: [0008]> RIL_REQUEST_SIM_IO (cmd=0xB0,efid=0x2F05,path=3F00,0,0,8,(null),pin2=(null),aid=a0000000871002ff4994208903100000)
ofonod[9085]: [0008]< RIL_REQUEST_SIM_IO (sw1=0x90,sw2=0x00,656effffffffffff)
ofonod[9085]: Querying PIN authentication state failed
Segmentation fault (core dumped)

Revision history for this message
Steve Langasek (vorlon) wrote :

And here's the syslog generated by the same command; dunno if that includes the debugging info you expect.

Tony Espy (awe)
Changed in touch-preview-images:
status: New → Incomplete
Changed in ofono (Ubuntu):
status: New → Incomplete
Revision history for this message
Tony Espy (awe) wrote :

I changed the Status of this to Invalid for both tasks as it's been incomplete for more than 9 months, and no new reports have surfaced.

Changed in touch-preview-images:
status: Incomplete → Invalid
Changed in ofono (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.