public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Jeremy Jackson <jerj@coplanar.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: btusb regression on commands unsupported by adapter
Date: Fri, 18 Dec 2009 13:53:26 -0800	[thread overview]
Message-ID: <1261173206.4041.89.camel@localhost.localdomain> (raw)
In-Reply-To: <1261158272.4932.184.camel@ragnarok>

Hi Jeremy,

> I've posted more details here for userspace diagnosis/workaround,
> 
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/377225
> 
> Some (older?) BT adapters don't support the commands 'Read Default Link
> Policy Settings' 
> 	'Write Default Link Policy Settings'
> 
> as shown by # hciconfig hci0 commands
> 
> This appears be one cause of the infamous kernel message: hci0: command
> tx timeout.  This in turn causes bluetoothd to give up and take down the
> interface.
> 
> If you kill bluetoothd, and manually # hciconfig hci0 up, you can
> discover and inq devices no problem.
> 
> I made a patch to disable the offending command, and the above mentioned
> bug report I gave instructions to gather data on adapter BT version,
> supported features, and supported commands.  Hopefully some user reports
> can be used to make use of the command conditional on actual adapter
> support.
> 
> The question for kernel side is, regression, or corrected behaviour?

this is basically a bluetoothd issue. We should be reading the list of
supported commands and then either issue or not issue this command. Feel
free to write a patch for that.

Regards

Marcel



  reply	other threads:[~2009-12-18 21:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18 17:44 btusb regression on commands unsupported by adapter Jeremy Jackson
2009-12-18 21:53 ` Marcel Holtmann [this message]
2009-12-23 13:51   ` Stefan Seyfried

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=1261173206.4041.89.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=jerj@coplanar.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