2013/3/28 Freedreamer <[email protected]> > > > 2013/3/28 Denis Kenzior <[email protected]> > >> Hi, >> >> Please do not top-post on this mailing list. >> >> >> On 03/28/2013 08:43 AM, Freedreamer wrote: >> >>> sorry did not over the mail.... >>> >>> about ppp , Is that normal that I have to config these parameters? >>> >>> >> Yes, this is normal. oFono expects another daemon (e.g. ConnMan, >> NetworkManager) to configure the network interfaces. >> >> Regards, >> -Denis >> >> > Hi guys, > > Sorry again! I'm a newbie in mailing list. > Thanks for ppp issue I understand. I tried my code (that worked on x86) on > the embedded ARM board but we have problem , here the logs: > ofonod[16939]: drivers/atmodem/sim.c:at_crsm_read_cb() crsm_read_cb: 90, > 00, 15 > ofonod[16939]: src/simfs.c:sim_fs_op_read_block_cb() bufoff: 0, dataoff: > 0, tocopy: 15 > ofonod[16939]: MUX: waking up writer > ofonod[16939]: MUX: creating source: 0x14a0390, channel: 0x148a6a0, > writer: 4, reader: 0 > ofonod[16939]: MUX: can write data > ofonod[16939]: MUX: checking channel for write: 0x148ac50 > ofonod[16939]: MUX: checking channel for write: 0x148a6a0 > ofonod[16939]: MUX: dispatching write sources: 0x148a6a0 > ofonod[16939]: MUX: checking source: 0x14a0390 > ofonod[16939]: MUX: dispatching source: 0x14a0390 > ofonod[16939]: Chat2: > AT+CRSM=192,28474\r > ofonod[16939]: MUX: removing source: 0x14a0390 > ofonod[16939]: MUX: checking source: 0x149eb80 > ofonod[16939]: MUX: checking channel for write: 0x1488ec0 > ofonod[16939]: MUX: dispatching write sources: 0x1488ec0 > ofonod[16939]: MUX: checking source: 0x148aaf0 > ofonod[16939]: MUX: checking channel for write: 0x1490430 > ofonod[16939]: MUX: dispatching write sources: 0x1490430 > ofonod[16939]: MUX: checking source: 0x148ad60 > ofonod[16939]: Chat1: Wakeup got no response > ofonod[16939]: Aborting (signal 11) [ofonod] > ofonod[16939]: ++++++++ backtrace ++++++++ > > I suspect that should be a syncronization issue between the virtual > channel. Any idea? > > > Hi , got new information. I start gdb and backtrace and i found where is the seg fault. The function "decode_at_error" doesn't check if *error or *final are NULL... and in my case they are. if I put a check in the function it remains stuck waiting AT cmd reply....
any help is appreciated. Marco below the logs: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffff7dbb740 (LWP 13322)] 0x000000000045d1be in decode_at_error () Missing separate debuginfos, use: debuginfo-install bluez-libs-4.101-6.fc18.x86_64 dbus-libs-1.6.8-2.fc18.x86_64 glib2-2.34.2-2.fc18.x86_64 glibc-2.16-28.fc18.x86_64 libgcc-4.7.2-8.fc18.x86_64 systemd-libs-197-1.fc18.2.x86_64 (gdb) backtrace #0 0x000000000045d1be in decode_at_error () #1 0x000000000045c6b0 in attr_cb () #2 0x000000000043fc28 in at_chat_finish_command () #3 0x000000000043fcb9 in wakeup_no_response () #4 0x00000034e56485db in g_timeout_dispatch () from /lib64/libglib-2.0.so.0 #5 0x00000034e5647a55 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #6 0x00000034e5647d88 in g_main_context_iterate.isra.24 () from /lib64/libglib-2.0.so.0 #7 0x00000034e5648182 in g_main_loop_run () from /lib64/libglib-2.0.so.0 #8 0x000000000040f5f2 in main () ofonod[16255]: MUX: received data ofonod[16255]: MUX: deliver_data: dlc: 4 ofonod[16255]: MUX: dispatching sources for channel: 0xdd98b0 ofonod[16255]: MUX: checking source: 0xdd9980 ofonod[16255]: MUX: dispatching source: 0xdd9980 ofonod[16255]: Chat4: < \r\n+CGEV: NW DETACH\r\n ofonod[16255]: Chat1: Wakeup got no response ofonod[16255]: drivers/atmodem/atutil.c:decode_at_error() decode_at_error null pointer ofonod[16255]: Chat1: Wakeup got no response ofonod[16255]: Chat1: Wakeup got no response ofonod[16255]: Chat1: Wakeup got no response ofonod[16255]: Chat1: Wakeup got no response ofonod[16255]: Chat1: Wakeup got no response
_______________________________________________ ofono mailing list [email protected] http://lists.ofono.org/listinfo/ofono
