From: Johan Hedberg <johan.hedberg@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
kernel list <linux-kernel@vger.kernel.org>,
marcel@holtmann.org, gustavo@padovan.org,
linux-bluetooth@vger.kernel.org
Subject: Re: 3.10-rc: bluetooth disappeared on thinkpad x60 (regression)
Date: Mon, 10 Jun 2013 13:05:19 +0300 [thread overview]
Message-ID: <20130610100519.GA9816@x220.ger.corp.intel.com> (raw)
In-Reply-To: <20130610092907.GA5487@amd.pavel.ucw.cz>
Hi Pavel,
On Mon, Jun 10, 2013, Pavel Machek wrote:
> root@amd:~# hciconfig hci0 up
> Can't init device hci0: Operation not supported (95)
> root@amd:~# hcitool inq
> Inquiring ...
> Inquiry failed.: No such device
> root@amd:~#
Could you take logs of the HCI traffic that happens when you try this.
You can use the btmon tool from BlueZ for it. Based on a quick look at
the code it seems like this particular error could only come if one of
the HCI commands used for device initialization fails.
The Bluetooth HCI init sequence is constructed using only commands that
should be expected to work assuming the hardware follows the
specification, but occasionally we do encounter Bluetooth hardware that
is broken in one way or another and needs a work around to the sequence.
E.g. recently we added a couple of extra commands to read some new
parameters from the hardware, commands that are mandatory for hardware
beyond a specific version (something we check for), but could be that
the chip on the X60 doesn't support these.
Anyway, once we see what exactly is failing in the HCI logs we can make
an adjustment to the conditions that the failing commands depend on,
which in the worst case will be a device specific quirk based on the USB
id of your hardware.
Johan
next prev parent reply other threads:[~2013-06-10 10:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 9:29 3.10-rc: bluetooth disappeared on thinkpad x60 (regression) Pavel Machek
2013-06-10 10:05 ` Johan Hedberg [this message]
2013-06-10 11:04 ` Pavel Machek
2013-06-10 11:59 ` Johan Hedberg
2013-06-10 13:38 ` Pavel Machek
2013-06-10 16:07 ` Johan Hedberg
2013-06-10 19:37 ` Pavel Machek
2013-06-11 7:22 ` Johan Hedberg
2013-06-11 10:20 ` Johan Hedberg
2013-06-12 11:23 ` Pavel Machek
2013-06-13 7:23 ` Johan Hedberg
2013-06-13 8:04 ` Johan Hedberg
2013-06-13 8:45 ` Pavel Machek
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=20130610100519.GA9816@x220.ger.corp.intel.com \
--to=johan.hedberg@gmail.com \
--cc=gustavo@padovan.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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).