From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: SAGEM HiloNC v2 Driver
Date: Thu, 28 Mar 2013 11:04:30 -0500 [thread overview]
Message-ID: <51546A0E.6020005@gmail.com> (raw)
In-Reply-To: <CAAs3wMijW_8Cm9Af673zHjLBvvg4ZshWLcBrLuiiVfxKyTyVMQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1734 bytes --]
Hi,
> 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?
>
Can you compile oFono with debug information on (export CFLAGS=-O0,
--enable-debug) and see whether you get a better backtrace. This is
pretty hard to debug with the information provided.
Regards,
-Denis
next prev parent reply other threads:[~2013-03-28 16:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAs3wMjcs_Y6-zFVUX2k8uO6_3tV0CLga2Pty0Cb2M9YOf7_xQ@mail.gmail.com>
2013-03-27 6:29 ` SAGEM HiloNC v2 Driver Freedreamer
2013-03-27 14:36 ` Denis Kenzior
2013-03-27 18:06 ` Freedreamer
2013-03-27 19:54 ` Denis Kenzior
2013-03-28 13:40 ` Freedreamer
2013-03-28 13:43 ` Freedreamer
2013-03-28 14:28 ` Denis Kenzior
2013-03-28 15:42 ` Freedreamer
2013-03-28 16:04 ` Denis Kenzior [this message]
2013-03-28 16:32 ` Freedreamer
2013-03-28 19:41 ` Denis Kenzior
2013-03-29 11:24 ` Freedreamer
2013-04-04 12:08 ` Freedreamer
2013-04-04 13:36 ` Denis Kenzior
2013-04-04 17:18 ` Freedreamer
2013-03-26 9:07 Freedreamer
2013-03-26 14:25 ` Denis Kenzior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51546A0E.6020005@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.