public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: bluez-4.11 + 2.6.27-rc8 + SCO headset -> bluetoothd: connect(): Connection timed out (110)
Date: Sun, 5 Oct 2008 19:50:43 +0200	[thread overview]
Message-ID: <48B8929D-29F9-4352-9C81-E95FDBC09876@gmail.com> (raw)
In-Reply-To: <48E7FB1E.8000504@pook.es>


On Oct 5, 2008, at 1:24, Stuart Pook wrote:
> not for me :-( I am once again getting the "aplay: set_params:979:
> Unable to install hw params:" message after a 40 second delay.
>
> The headset hisses softly to me during these 40 seconds.
>
> The error message from bluetoothd is "connect(): Connection timed  
> out (110)"

This seems to be some other error than the one that was fixed in 4.11.  
Could you try to get a hcidump of when this happens. It might be able  
to tell more about what's going on.

> Sometimes bluetoothd segfaults.

That's something more serious. Could you please try to produce a  
backtrace, either with gdb or valgrind. Thanks!

Johan

  reply	other threads:[~2008-10-05 17:50 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30 21:03 bluez-4.9 + 2.6.27-rc8 + SCO headset -> bluetoothd: connect: Operation not permitted Stuart Pook
2008-09-30 23:26 ` David Sainty
2008-10-01 17:30   ` Stuart Pook
2008-10-04  3:47     ` Luiz Augusto von Dentz
2008-10-04 11:25       ` Stuart Pook
2008-10-04 11:51         ` Marcel Holtmann
2008-10-04 23:24           ` bluez-4.11 + 2.6.27-rc8 + SCO headset -> bluetoothd: connect(): Connection timed out (110) Stuart Pook
2008-10-05 17:50             ` Johan Hedberg [this message]
2008-10-05 19:17               ` Stuart Pook
2008-10-05 20:07               ` bluez-4.11 + 2.6.27-rc8 + SCO headset -> Invalid read of size 4 Stuart Pook
2008-10-06  8:47                 ` Johan Hedberg
2008-10-06 10:52                   ` Johan Hedberg
2008-10-06 18:38                     ` Stuart Pook
2008-10-06 19:56                     ` Stuart Pook
2008-10-06 20:31                       ` Johan Hedberg
2008-10-06 20:56                         ` bluez/git + 2.6.27-rc8 + SCO headset -> SIGSEGV Stuart Pook
2008-10-06 21:03                           ` Marcel Holtmann
2008-10-06 21:10                             ` Stuart Pook
2008-10-06 21:21                               ` Marcel Holtmann
2008-10-06 22:40                                 ` bluez/git + 2.6.27-rc8 + bluetoothd " Stuart Pook
2008-10-07  5:34                                   ` Johan Hedberg
2008-12-06 12:15                                     ` bluez-4.22 + twinkle -> Unable to lock headset Stuart Pook
2008-12-08 18:42                                       ` Luiz Augusto von Dentz
2008-12-09 12:23                                         ` sreevani medhahal
2008-10-06 20:39                   ` bluez/git + 2.6.27-rc8 + Belkin F8T017 -> Can't read class of adapter Stuart Pook
2008-10-06 20:45                     ` Marcel Holtmann
2008-10-06 21:55                       ` Stuart Pook
2008-10-06 22:38                         ` Marcel Holtmann
2008-10-06 23:17                           ` bluez/git + 2.6.27-rc8 + Belkin F8T017 -> works with reset=1 Stuart Pook

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=48B8929D-29F9-4352-9C81-E95FDBC09876@gmail.com \
    --to=johan.hedberg@gmail.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