From: Johan Hedberg <johan.hedberg@gmail.com>
To: Stuart Pook <linux-bluetooth4@pook.es>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: bluez git + Linksys USBBT100 + 2.6.30-rc2 -> Segmentation fault
Date: Mon, 20 Apr 2009 00:38:37 +0300 [thread overview]
Message-ID: <20090419213837.GA6514@jh-x301> (raw)
In-Reply-To: <49EB93C2.3090702@pook.es>
Hi Stuart,
On Sun, Apr 19, 2009, Stuart Pook wrote:
> I did get one error that I had never seen before "Refusing headset":
That comes if a headset is trying to connect to you and there's already
max_connected_headsets headsets connected (this variable defaults to 1 and
can be overrided with the MaxConnected parameter in audio.conf.
> bluetoothd[32401]: Audio API: BT_REQUEST <- BT_START_STREAM
> bluetoothd[32401]: State changed /org/bluez/32401/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_DISCONNECTED -> HEADSET_STATE_CONNECT_IN_PROGRESS
> bluetoothd[32401]: Unable to get service record: Connection timed out (110)
> bluetoothd[32401]: Unable to get a SCO fd
> bluetoothd[32401]: headset_resume_complete: resume failed
> bluetoothd[32401]: Audio API: BT_ERROR -> BT_START_STREAM
> bluetoothd[32401]: telephony-dummy: device 0xb8f2c550 disconnected
> bluetoothd[32401]: State changed /org/bluez/32401/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_CONNECT_IN_PROGRESS -> HEADSET_STATE_DISCONNECTED
> bluetoothd[32401]: Unix client disconnected (fd=13)
> bluetoothd[32401]: Unable to get service record: Connection timed out (110)
> Segmentation fault
Could you please run bluetoothd through valgrind to get a proper
backtrace. This time it should hopefully be more useful than the one we
got from the infinite recursion case (with some luck a fix should be just
a few minutes away from getting the log). Once we have the valgrind trace
I'd also be interested in seeing the output of hcidump for the "Connection
timed out" situation.
> In fact I get the "Too short (1 bytes) IPC packet from bluetoothd" error
> even from bluetoothd 4.36.
If this isn't caused by a bug the only possible reason I can think of as a
cause for it is a mismatch between the alsa plugin and bluetoothd versions.
Btw, you might want to consider trying out pulseaudio 0.9.15. It's worked
pretty flawlessly for me with bluez 4.34 and later versions (though I
haven't actually tested the mono profiles very much with it).
Johan
next prev parent reply other threads:[~2009-04-19 21:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 12:02 bluez 4.34 + Linksys USBBT100 + hcitool scan -> core dump Stuart Pook
2009-04-05 17:04 ` Stuart Pook
2009-04-05 17:22 ` Johan Hedberg
2009-04-19 19:19 ` bluez git + Linksys USBBT100 + 2.6.30-rc2 -> Segmentation fault Stuart Pook
2009-04-19 20:05 ` Johan Hedberg
2009-04-19 21:12 ` Stuart Pook
2009-04-19 21:38 ` Johan Hedberg [this message]
2009-04-19 22:05 ` Stuart Pook
2009-04-20 17:45 ` Stuart Pook
2009-04-05 17:19 ` bluez 4.34 + Linksys USBBT100 + hcitool scan -> core dump Johan Hedberg
2009-04-06 21:20 ` 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=20090419213837.GA6514@jh-x301 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth4@pook.es \
--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