Open Source Telephony
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 7/8] netreg: adapt CMER and CIEV for telit
Date: Thu, 16 Aug 2012 00:57:42 -0500	[thread overview]
Message-ID: <502C8BD6.1080001@gmail.com> (raw)
In-Reply-To: <502C99C4.1060902@hale.at>

[-- Attachment #1: Type: text/plain, Size: 1657 bytes --]

Hi Christopher,

>>
>> That looks a bit strange. Can you rm -rf /var/lib/ofono, rerun oFono
>> and see if that message persists?
>
> I did that but the message still shows up:
>
> ...
> Aug 8 11:40:00 mx31tt01 daemon.info ofonod[622]: Aux: >
> AT+CRSM=176,28486,0,0,17\r
> Aug 8 11:40:00 mx31tt01 daemon.info ofonod[622]: Aux: < \r\n+CRSM:
> 144,0,FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF\r\n\r\nOK\r\n
> Aug 8 11:40:00 mx31tt01 daemon.debug ofonod[622]:
> drivers/atmodem/sim.c:at_crsm_read_cb() crsm_read_cb: 90, 00, 17
> Aug 8 11:40:00 mx31tt01 daemon.debug ofonod[622]:
> src/simfs.c:sim_fs_op_read_block_cb() bufoff: 0, dataoff: 0, tocopy: 17
> Aug 8 11:40:00 mx31tt01 daemon.err ofonod[622]: EFspn read successfully,
> but couldn't parse
> ...
>
> I hardly know anything about SIM FS yet, can you tell me the
> consequences of this please.
>

Consequence of removing /var/lib/ofono or of the error message?

If the former, then that is a heavy-handed way of clearing all settings 
oFono stores on disk, including the sim EF cache.  In your previous log 
the contents of EFspn were being read from cache.  So I just told you to 
wipe the cache so the contents show up in the AT log.  Otherwise I'd 
have to give you complicated directions on how to read the contents ;) 
If you want to know more about the EF cache itself, just ask me on IRC 
some time.

For the error message, it was actually a bug I fixed in commit 
54de04a828d945e8f081c7cd99161881736666b8.  The error message was being 
printed, yet things still worked correctly (by luck.)  You should not be 
seeing that message pop up again.

Regards,
-Denis

  reply	other threads:[~2012-08-16  5:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 13:23 [PATCH 7/8] netreg: adapt CMER and CIEV for telit Christopher Vogl
2012-08-13 16:25 ` Denis Kenzior
2012-08-14 14:16   ` Christopher Vogl
2012-08-14  6:46     ` Denis Kenzior
2012-08-16  6:57       ` Christopher Vogl
2012-08-16  5:57         ` Denis Kenzior [this message]
2012-09-06  9:25   ` [PATCH 2/2] netreg: Add telit version for ciev notification christopher.vogl
2012-09-06  9:25     ` [PATCH 1/2] netreg: Query and select supported CMER modes christopher.vogl
2012-09-06  9:36   ` [PATCH 2/2] netreg: Add telit version for ciev notification christopher.vogl
2012-09-06  9:49   ` christopher.vogl
2012-09-06  9:49     ` [PATCH 1/2] netreg: Query and select supported CMER modes christopher.vogl
2012-09-12  4:22       ` Denis Kenzior
2012-09-12  4:24     ` [PATCH 2/2] netreg: Add telit version for ciev notification Denis Kenzior
2012-09-12  8:13       ` Christopher Vogl
2012-09-12 13:53         ` Denis Kenzior
2012-09-12 15:07           ` Christopher Vogl

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=502C8BD6.1080001@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox