linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "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:04:23 +0200	[thread overview]
Message-ID: <20130610110423.GA8834@amd.pavel.ucw.cz> (raw)
In-Reply-To: <20130610100519.GA9816@x220.ger.corp.intel.com>

Hi!

> > 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.

Where can I get btmon? I tried 

root@amd:~# apt-get install bluez-utils

but it is not there. (Can I just add printk somewhere?)

> 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.

I don't expect strace is enough?

set_thread_area({entry_number:-1 -> 6, base_addr:0xb7624b20,
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0,
limit_in_pages:1, seg_not_present:0, useable:1}) = 0
mprotect(0xb7766000, 8192, PROT_READ)   = 0
mprotect(0xb77b2000, 4096, PROT_READ)   = 0
munmap(0xb7782000, 76642)               = 0
socket(PF_BLUETOOTH, SOCK_RAW, 1)       = 3
ioctl(3, 0x800448d3, 0xb77cc420)        = 0
ioctl(3, 0x400448c9, 0)                 = -1 EOPNOTSUPP (Operation not
supported)
write(2, "Can't init device hci0: Operatio"..., 53Can't init device
hci0: Operation not supported (95)
) = 53
exit_group(1)                           = ?
root@amd:~# btmon

Thanks,
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2013-06-10 11:04 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
2013-06-10 11:04   ` Pavel Machek [this message]
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=20130610110423.GA8834@amd.pavel.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=gustavo@padovan.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --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).