From: Peter Hurley <phurley@charter.net>
To: linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: [4.48] SDP Discovery not reset on error
Date: Thu, 03 Sep 2009 23:02:47 -0400 [thread overview]
Message-ID: <4AA08357.7050903@charter.net> (raw)
I believe that SDP Discovery initiated during rfcomm_connect is left in
an inconsistent state when there is an error (such as when the remote
device is off).
In the log capture below, an attempt to connect (via
gnome-bluetooth/bluetooth-applet) to the headset fails because the
device is off. When the device is turned back on, and another attempt
is made to connect, SDP discovery fails again (Operation already in
progress).
> Sep 3 21:21:52 dev-wkstn bluetoothd[2724]: State changed /org/bluez/2724/hci0/dev_00_0D_FD_1E_99_30: HEADSET_STATE_DISCONNECTED -> HEADSET_STATE_CONNECT_IN_PROGRESS
> Sep 3 21:21:57 dev-wkstn bluetoothd[2724]: adapter_get_device(00:0D:FD:1E:99:30)
> Sep 3 21:21:57 dev-wkstn bluetoothd[2724]: Unable to get service record: Host is down (112)
> Sep 3 21:21:57 dev-wkstn bluetoothd[2724]: telephony-dummy: device 0x7f71751e8230 disconnected
> Sep 3 21:21:57 dev-wkstn bluetoothd[2724]: State changed /org/bluez/2724/hci0/dev_00_0D_FD_1E_99_30: HEADSET_STATE_CONNECT_IN_PROGRESS -> HEADSET_STATE_DISCONNECTED
> Sep 3 21:23:00 dev-wkstn bluetoothd[2724]: State changed /org/bluez/2724/hci0/dev_00_0D_FD_1E_99_30: HEADSET_STATE_DISCONNECTED -> HEADSET_STATE_CONNECT_IN_PROGRESS
> Sep 3 21:23:00 dev-wkstn bluetoothd[2724]: Unable to get service record: Operation already in progress (114)
> Sep 3 21:23:00 dev-wkstn bluetoothd[2724]: telephony-dummy: device 0x7f71751e8230 disconnected
> Sep 3 21:23:00 dev-wkstn bluetoothd[2724]: State changed /org/bluez/2724/hci0/dev_00_0D_FD_1E_99_30: HEADSET_STATE_CONNECT_IN_PROGRESS -> HEADSET_STATE_DISCONNECTED
Initially I was thinking that bt_cancel_discovery() needed to be called
or that cleanup in one of the failed: targets in the series of functions
and callbacks in common/glib_helper.c was the problem, but after a quick
scan perhaps the problem lies on the SDP server side? Suggestions?
Regards,
Peter Hurley
next reply other threads:[~2009-09-04 3:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 3:02 Peter Hurley [this message]
2009-09-04 6:31 ` [4.48] SDP Discovery not reset on error Johan Hedberg
2009-09-04 15:28 ` Peter Hurley
2009-09-04 15:56 ` Johan Hedberg
2009-09-04 17:49 ` Peter Hurley
2009-09-04 19:41 ` Johan Hedberg
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=4AA08357.7050903@charter.net \
--to=phurley@charter.net \
--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