mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 19:07:23 +0300	[thread overview]
Message-ID: <20130610160723.GA18282@x220.P-661HNU-F1> (raw)
In-Reply-To: <20130610133834.GA4058@amd.pavel.ucw.cz>

Hi Pavel,

On Mon, Jun 10, 2013, Pavel Machek wrote:
> I ran hcidump, while I did hciconfig hci0 up on other console.
> 
> root@amd:~# hcidump hci0
> HCI sniffer - Bluetooth packet analyzer ver 1.42
> device: hci0 snap_len: 1028 filter: 0xffffffff
> < HCI Command: Reset (0x03|0x0003) plen 0
> > HCI Event: Command Complete (0x0e) plen 4
> < HCI Command: Read Local Supported Features (0x04|0x0003) plen 0
> > HCI Event: Command Complete (0x0e) plen 12
> < HCI Command: Read Local Version Information (0x04|0x0001) plen 0
> > HCI Event: Command Complete (0x0e) plen 12
> < HCI Command: Read BD ADDR (0x04|0x0009) plen 0
> > HCI Event: Command Complete (0x0e) plen 10
> < HCI Command: Read Buffer Size (0x04|0x0005) plen 0
> > HCI Event: Command Complete (0x0e) plen 11
> < HCI Command: Read Class of Device (0x03|0x0023) plen 0
> > HCI Event: Command Complete (0x0e) plen 7
> < HCI Command: Read Local Name (0x03|0x0014) plen 0
> > HCI Event: Command Complete (0x0e) plen 252
> < HCI Command: Read Voice Setting (0x03|0x0025) plen 0
> > HCI Event: Command Complete (0x0e) plen 6
> < HCI Command: Set Event Filter (0x03|0x0005) plen 1
> > HCI Event: Command Complete (0x0e) plen 4
> < HCI Command: Write Connection Accept Timeout (0x03|0x0016) plen 2
> > HCI Event: Command Complete (0x0e) plen 4
> < HCI Command: Delete Stored Link Key (0x03|0x0012) plen 7
> > HCI Event: Command Complete (0x0e) plen 4
> 
> Hope this helps,

It gives a better idea but is still lacking a bit of information since
hcidump is by default quite restrictive in what it outputs. Could you
try once more, but this time pass the -X and -V command line switches to
hcidump. It should make it output the full set of parameters of the HCI
commands and events. What I'd also ask is if you could make an
additional binary HCI log in the btsnoop format so that we could analyze
the log with btmon (which has better decoders than hcidump). You get
hcidump to do this by passing "-B -w <filename>" as parameters and can
verify that the produced file is correct by running hcidump -r <file>.

Johan

  reply	other threads:[~2013-06-10 16:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-10  9:29 Pavel Machek
2013-06-10 10:05 ` Johan Hedberg
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 [this message]
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=20130610160723.GA18282@x220.P-661HNU-F1 \
    --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

all inboxes | Powered by JetHome®