public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Brock Denson <Brock.Denson@csr.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: bluez 4.x questions, SCO stops
Date: Fri, 8 May 2009 00:25:08 +0300	[thread overview]
Message-ID: <20090507212508.GA23276@jh-x301> (raw)
In-Reply-To: <79DD16001F75DB4EB7DE37CDD687BB2001B7238D@dalamsexb02.AMERICAS.ROOT.PRI>

Hi Brock,

On Thu, May 07, 2009, Brock Denson wrote:
> I am having a problem with SCO stopping after 1 minute that I would
> really appreciate some help with.  I can connect to the headset, query
> responses, etc, but when I start sco either via a dbus-send command or
> with the test-telephony play <> command then after 30 seconds I get a
> dbus timeout and then 30 more seconds later the SCO will stop.  I have
> air-traced the session and can see that the host is sending silence
> while SCO is being transmitted, so it seems functional, but I am sure I
> am missing something.  I have included just about everything I can think
> of below in the hopes that someone has a few minutes to point out the
> problem.  Distribution is FC10.

You've got several occurences of the following in the logs:
bluetoothd[25721]: connect(): Connection timed out (110)

I'm pretty sure that's coming for the SCO socket and I recall there being
a related kernel bug which got fixed some time back. You might want to try
with the latest 2.6.30-rc kernel or one of Marcel's git trees (e.g.
bluetooth-testing). Those should have the issue fixed.

Johan

  reply	other threads:[~2009-05-07 21:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07 21:01 bluez 4.x questions, SCO stops Brock Denson
2009-05-07 21:25 ` Johan Hedberg [this message]
2009-05-07 22:00   ` Brock Denson
2009-05-07 23:59   ` Brock Denson
2009-05-11 18:45     ` [PATCH] Fix introspection issue in gdbus Denis Kenzior
2009-05-11 18:51       ` Marcel Holtmann

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=20090507212508.GA23276@jh-x301 \
    --to=johan.hedberg@gmail.com \
    --cc=Brock.Denson@csr.com \
    --cc=linux-bluetooth@vger.kernel.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