From: Oliver Joos <oliver.joos@hispeed.ch>
To: linux-bluetooth@vger.kernel.org
Subject: [Regression] bluetoohd 4.85 and later fails to connect properly
Date: Fri, 23 Dec 2011 00:42:34 +0100 [thread overview]
Message-ID: <1324597354.7632.42.camel@oliverhp> (raw)
[-- Attachment #1: Type: text/plain, Size: 1975 bytes --]
Hi everyone,
(I'm glad to post my first message here on linux-bluetooth)
I collect facts about why various Bluetooth adapters stopped working
with bluez since 2011. We have several Laptops with Broadcom 2035
adapters "03f0:011d" (chip says BCM92035NMD) where Bluetooth does not
work anymore since Ubuntu 11.04 (bluez 4.91). Pairing works, but data
transfer does not. Same issue with my mobile (Symbian S60v3.1), my
headset and my mini keyboard. Also affected are Android phones and other
common Bluetooth adapters like Cambridge Silicon Radio "0a12:0001".
See details from other victims on https://bugs.launchpad.net/bugs/839157
With the help of Nikolay Kachanov (he posted here on August 4th) I found
that if I replace the package bluez 4.91 with 4.84 then everything works
as expected. bluez 4.91 even works if only "/usr/sbin/bluetoothd" is
replaced by the one from 4.84, whereas 4.85 does not work anymore.
So IMO the regression occurred in bluetoothd 4.85.
I have attached all logs I made using bluez_4.84-0ubuntu1_i386.deb and
bluez_4.85-0ubuntu1_i386.deb. With the bluetooth-applet I stopped the
bluetooth service, the deleted /var/lib/bluetooth/, replaced bluetoothd,
restarted service, did pairing (which always works!) and then tried to
connect my mobile (which fails with 4.85).
To me one interesting difference is in bluetoothd_4.8x.log where
"plugins/hciops.c:link_key_request()" is missing with 4.85.
And an even more suspicious difference is in hcidump-Xt_4.8x.log here:
With bluetoothd 4.84 (which works):
< HCI Command: Create Connection (0x01|0x0005) plen 13
0000: 8d 68 6b 9a 1c 00 18 cc 01 00 ed f3 01 .hk..........
With bluetoothd 4.85 (which fails):
< HCI Command: Create Connection (0x01|0x0005) plen 13
0000: 8d 68 6b 9a 1c 00 18 cc 01 00 78 b6 01 .hk.......x..
Now I hope that someone on this list has an idea where this bug hides.
Please just ask if additional info would be helpful!
With kind regards,
+++ Oliver
[-- Attachment #2: bluez-4.8x-logs.tar.gz --]
[-- Type: application/x-compressed-tar, Size: 18908 bytes --]
next reply other threads:[~2011-12-22 23:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 23:42 Oliver Joos [this message]
2012-01-13 13:53 ` [Regression] bluetoohd 4.85 and later fails to connect properly Oliver Joos
2012-01-13 14:07 ` Daniel Wagner
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=1324597354.7632.42.camel@oliverhp \
--to=oliver.joos@hispeed.ch \
--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;
as well as URLs for NNTP newsgroup(s).