All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: oFono exits on new voicecall with disconnected system bus
Date: Thu, 20 Jan 2011 15:55:51 +0100	[thread overview]
Message-ID: <1295535351.3873.294.camel@aeonflux> (raw)
In-Reply-To: <AANLkTimkw+axiW_5=FiiTeu0AS2C0M74kroGui789mWs@mail.gmail.com>

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

Hi Nicola,

> that's happen with oFono 0.38 on freerunner with debian sid on the
> first incoming/outgoing call:
> 
> ofonod[6232]: drivers/calypsomodem/voicecall.c:cpi_notify() id:1,
> msgtype:0, direction:1, mode:0
> ofonod[6232]: drivers/calypsomodem/voicecall.c:cpi_notify() Len > 0
> ofonod[6232]: drivers/calypsomodem/voicecall.c:cpi_notify() type obtained
> ofonod[6232]: drivers/calypsomodem/voicecall.c:cpi_notify()
> num:+xxxxxxxxxxxx, type:145
> ofonod[6232]: drivers/calypsomodem/voicecall.c:cpi_notify() cause:892800, line:0
> ofonod[6232]: src/voicecall.c:ofono_voicecall_notify() Got a voicecall
> event, status: 4, id: 1, number: +xxxxxxxxxxx
> ofonod[6232]: src/voicecall.c:ofono_voicecall_notify() Did not find a
> call with id: 1
> ofonod[6232]: System bus has disconnected!

this happens if something in a D-Bus message is corrupted and the D-Bus
daemon complains. The result is that it kicks us off the bus.

You need to track down which D-Bus API call causes this. Wild assumption
is that it is either a wrong message parameter or an invalid object
path.

Regards

Marcel



  reply	other threads:[~2011-01-20 14:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20 14:51 oFono exits on new voicecall with disconnected system bus Nicola Mfb
2011-01-20 14:55 ` Marcel Holtmann [this message]
2011-01-21  9:04   ` Nicola Mfb
2011-01-21 10:29     ` Marcel Holtmann
2011-01-21 11:33       ` Nicola Mfb
2011-01-21 12:03         ` Marcel Holtmann
2011-01-21 12:10         ` Marcel Holtmann
2011-01-21 14:04           ` Nicola Mfb

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=1295535351.3873.294.camel@aeonflux \
    --to=marcel@holtmann.org \
    --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.