From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 203643] [REGRESSION][BISECTED] Sixaxis gamepad no longer connects via Bluetooth
Date: Wed, 22 May 2019 19:11:46 +0000 [thread overview]
Message-ID: <bug-203643-62941-1hBEfs3owA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203643-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203643
Andriy Perevortkin (irherder@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |irherder@gmail.com
--- Comment #10 from Andriy Perevortkin (irherder@gmail.com) ---
Sadly the RFC patch above does not fix it for me, the revert does
The device is edifier w330nb headset.
hcidump fragment of failed connection:
> HCI Event: Link Key Request (0x17) plen 6
bdaddr 5C:C6:E9:11:B1:20
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
bdaddr 5C:C6:E9:11:B1:20 key 9290EB1424E3A352C43F17C8499A3670
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Reply (0x01|0x000b) ncmd 1
status 0x00 bdaddr 5C:C6:E9:11:B1:20
> HCI Event: Encrypt Change (0x08) plen 4
status 0x00 handle 256 encrypt 0x01
< HCI Command: Read Encryption Key Size (0x05|0x0008) plen 2
> ACL data: handle 256 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 25 scid 0x0580
< ACL data: handle 256 flags 0x00 dlen 16
L2CAP(s): Connect rsp: dcid 0x0000 scid 0x0580 result 3 status 0
Connection refused - security block
> HCI Event: Command Complete (0x0e) plen 7
Read Encryption Key Size (0x05|0x0008) ncmd 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 256 packets 1
> HCI Event: Disconn Complete (0x05) plen 4
status 0x00 handle 256 reason 0x13
Reason: Remote User Terminated Connection
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-05-22 19:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 17:35 [Bug 203643] New: [REGRESSION][BISECTED] Sixaxis gamepad no longer connects via Bluetooth bugzilla-daemon
2019-05-18 22:10 ` [Bug 203643] " bugzilla-daemon
2019-05-18 23:42 ` bugzilla-daemon
2019-05-21 20:23 ` bugzilla-daemon
2019-05-21 20:45 ` bugzilla-daemon
2019-05-21 20:47 ` bugzilla-daemon
2019-05-21 20:49 ` bugzilla-daemon
2019-05-21 23:10 ` bugzilla-daemon
2019-05-22 0:16 ` bugzilla-daemon
2019-05-22 13:34 ` bugzilla-daemon
2019-05-22 19:11 ` bugzilla-daemon [this message]
2019-05-22 20:30 ` bugzilla-daemon
2019-05-23 7:58 ` bugzilla-daemon
2019-05-23 8:38 ` bugzilla-daemon
2019-05-29 14:04 ` bugzilla-daemon
2019-05-30 17:22 ` bugzilla-daemon
2019-06-05 4:59 ` bugzilla-daemon
2019-06-05 18:58 ` bugzilla-daemon
2019-06-07 8:33 ` bugzilla-daemon
2019-06-07 16:11 ` bugzilla-daemon
2019-06-25 16:33 ` bugzilla-daemon
2019-07-01 10:51 ` bugzilla-daemon
2019-07-01 12:26 ` bugzilla-daemon
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=bug-203643-62941-1hBEfs3owA@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.