linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>,
	Gustavo Padovan <gustavo@padovan.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: 3.19-rc1 refuse connection from bluetooth headset
Date: Wed, 24 Dec 2014 18:15:12 +0100	[thread overview]
Message-ID: <201412241815.12922@pali> (raw)

[-- Attachment #1: Type: text/plain, Size: 1909 bytes --]

Hello,

now I installed 3.19-rc1 kernel and my bluetooth headset was refused to connect automatically. I need to start 
connection manually from laptop (and then it working). Before when I started bluetooth headset it automatically 
connected and I did not have to do anything. Now with 3.19-rc1 kernel I need to do connection manually and I see 
error messages in hcidump:

 $ sudo hcidump 
 HCI sniffer - Bluetooth packet analyzer ver 2.2
 device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
 > HCI Event: Connect Request (0x04) plen 10
     bdaddr <HEADSET_ADDRESS> class 0x240404 type ACL
 < HCI Command: Reject Connection Request (0x01|0x000a) plen 7
     bdaddr <HEADSET_ADDRESS> reason 0x0f
     Reason: Connection Rejected due to Unacceptable BD_ADDR
 > HCI Event: Command Status (0x0f) plen 4
     Reject Connection Request (0x01|0x000a) status 0x00 ncmd 1
 > HCI Event: Connect Complete (0x03) plen 11
     status 0x0f handle 34 bdaddr <HEADSET_ADDRESS> type ACL encrypt 0x00
     Error: Connection Rejected due to Unacceptable BD_ADDR
 > HCI Event: Connect Request (0x04) plen 10
     bdaddr <HEADSET_ADDRESS> class 0x240404 type ACL
 < HCI Command: Reject Connection Request (0x01|0x000a) plen 7
     bdaddr <HEADSET_ADDRESS> reason 0x0f
     Reason: Connection Rejected due to Unacceptable BD_ADDR
 > HCI Event: Command Status (0x0f) plen 4
     Reject Connection Request (0x01|0x000a) status 0x00 ncmd 1
 > HCI Event: Connect Complete (0x03) plen 11
    status 0x0f handle 35 bdaddr <HEADSET_ADDRESS> type ACL encrypt 0x00
    Error: Connection Rejected due to Unacceptable BD_ADDR

(real address of my bluetooth headset was replaced by <HEADSET_ADDRESS>)

Can you inspect why new kernel refuse connection from my bluetooth headset?

I'm still using bluez 4.98 (which is in Ubuntu 12.04), I did not do any update.

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2014-12-24 17:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-24 17:15 Pali Rohár [this message]
2014-12-24 17:36 ` 3.19-rc1 refuse connection from bluetooth headset Johan Hedberg
2014-12-24 18:32   ` Pali Rohár
2014-12-24 18:37     ` Johan Hedberg
2014-12-24 18:41       ` Pali Rohár
2015-02-12 11:22         ` Ethan
2015-02-12 11:34           ` Johan Hedberg

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=201412241815.12922@pali \
    --to=pali.rohar@gmail.com \
    --cc=gustavo@padovan.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.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).