From: Artem Rakhov <arakhov@chromium.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: [A2DP] Incoming connections do not succeed
Date: Wed, 20 Aug 2014 15:52:26 -0700 [thread overview]
Message-ID: <CAD81oNZrVONCOTKtsXn2-A3a8KPy_qzU0HU3oO6Xw+FR5NqpQA@mail.gmail.com> (raw)
In-Reply-To: <CAD81oNZYeobbhMawvhrjTFSTY-aqEXYh9x3aTSOoH8u1Y6nHDQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2578 bytes --]
Hello,
I found the way to use avtest for testing incoming connections from the
speaker. If anyone is interested: stopped bluetoothd, powered BT back to
on, used "avtest --reject 0". Also had to change avtest to answer like
source instead of sink, which is set by default.
Incoming connections to avtest are always successful. And logs are very
similar (attached). I think the main difference is that the bluetoothd
requires authorization, while avtest does not.
Thanks,
Artem
On Mon, Aug 18, 2014 at 12:11 AM, Artem Rakhov <arakhov@chromium.org> wrote:
> Hi Luiz,
>
> I have also tried kernel 3.14, it didn't help.
> How can I use avinfo for test? Looks like it shows only basic
> information for the device. And it works fine with the speaker.
> I tried to use avtest: when I try to connect to the speaker,
> everything seems to be working good. Is there any way to use it to
> test incoming connections?
>
> Thanks,
> Artem
>
> On Sun, Aug 10, 2014 at 12:32 AM, Luiz Augusto von Dentz
> <luiz.dentz@gmail.com> wrote:
> > Hi Artem,
> >
> > On Fri, Aug 8, 2014 at 10:32 AM, Artem Rakhov <arakhov@chromium.org>
> wrote:
> >> Hi Marcel,
> >>
> >> Please find Packet Logger's btsnoop log in the attachment.
> >>
> >> So far I have 2 observations:
> >> 1. Mac does not require any authorization (most likely it's not the
> cause)
> >> 2. I found another BT speaker which works properly. At first, I'm
> >> seeing the same behavior: speaker initiates connection, BlueZ sends
> >> Configure Request (with no MTU), then speaker disconnects. But after
> >> that the device tries to initiate connection for the second time, and
> >> this time it is successful: after BlueZ sends Configure Request with
> >> no MTU, speaker answers with another Configure Request (with some
> >> MTU), and connection is established normally. Is it possible, that
> >> BlueZ is doing something wrong, but then this new speaker tries
> >> something else, while the old one does not?
> >
> > I could not find anything l2cap related in this logs, but I notice
> > there a LE scanning ongoing perhaps you have should try disabling it
> > with Disconnect method for now. Anyway A2DP code is not really
> > involved with L2CAP connection setup so we would have to look at the
> > kernel changes but I quick check doesn't show anything and you said
> > you have tried with 3.10 so Im afraid this is only reproducible with
> > some specific device.
> >
> > Btw, if you want to really isolate the problem you can try to connect
> > using avinfo or l2test directly.
> >
> >
> > --
> > Luiz Augusto von Dentz
>
[-- Attachment #1.2: Type: text/html, Size: 3420 bytes --]
[-- Attachment #2: btmon_avtest --]
[-- Type: application/octet-stream, Size: 18928 bytes --]
luetooth monitor ver 5.19
= New Index: 3C:77:E6:60:5C:B2 (BR/EDR,USB,hci0) [hci0] 0.456259
> HCI Event: Vendor (0xff) plen 2 [hci0] 22.527472
81 00 ..
> HCI Event: Connect Request (0x04) plen 10 [hci0] 22.528472
Address: 10:B7:F6:01:31:ED (OUI 10-B7-F6)
Class: 0x240404
Major class: Audio/Video (headset, speaker, stereo, video, vcr)
Minor class: Wearable Headset Device
Rendering (Printing, Speaker)
Audio (Speaker, Microphone, Headset)
Link type: ACL (0x01)
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7 [hci0] 22.528565
Address: 10:B7:F6:01:31:ED (OUI 10-B7-F6)
Role: Slave (0x01)
> HCI Event: Command Status (0x0f) plen 4 [hci0] 22.529462
Accept Connection Request (0x01|0x0009) ncmd 1
Status: Success (0x00)
> HCI Event: Vendor (0xff) plen 2 [hci0] 22.576536
81 01 ..
> HCI Event: Vendor (0xff) plen 7 [hci0] 22.577469
82 00 00 01 01 15 00 .......
> HCI Event: Connect Complete (0x03) plen 11 [hci0] 22.578469
Status: Success (0x00)
Handle: 21
Address: 10:B7:F6:01:31:ED (OUI 10-B7-F6)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2 [hci0] 22.578641
Handle: 21
> HCI Event: Command Status (0x0f) plen 4 [hci0] 22.579463
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
> HCI Event: Read Remote Supported Features (0x0b) plen 11 [hci0] 22.605538
Status: Success (0x00)
Handle: 21
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83
3 slot packets
5 slot packets
Encryption
Slot offset
Timing accuracy
Role switch
Hold mode
Sniff mode
Park state
Power control requests
Channel quality driven data rate (CQDDR)
SCO link
HV2 packets
HV3 packets
u-law log synchronous data
A-law log synchronous data
CVSD synchronous data
Paging parameter negotiation
Power control
Transparent synchronous data
Broadcast Encryption
Enhanced Data Rate ACL 2 Mbps mode
Enhanced Data Rate ACL 3 Mbps mode
Enhanced inquiry scan
Interlaced inquiry scan
Interlaced page scan
RSSI with inquiry results
Extended SCO link (EV3 packets)
EV4 packets
EV5 packets
AFH capable slave
AFH classification slave
3-slot Enhanced Data Rate ACL packets
5-slot Enhanced Data Rate ACL packets
Sniff subrating
Pause encryption
AFH capable master
AFH classification master
Enhanced Data Rate eSCO 2 Mbps mode
Enhanced Data Rate eSCO 3 Mbps mode
3-slot Enhanced Data Rate eSCO packets
Extended Inquiry Response
Secure Simple Pairing
Encapsulated PDU
Non-flushable Packet Boundary Flag
Link Supervision Timeout Changed Event
Inquiry TX Power Level
Extended features
< HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3 [hci0] 22.605584
Handle: 21
Page: 1
> HCI Event: Command Status (0x0f) plen 4 [hci0] 22.606460
Read Remote Extended Features (0x01|0x001c) ncmd 1
Status: Success (0x00)
> HCI Event: Read Remote Extended Features (0x23) plen 13 [hci0] 22.615477
Status: Success (0x00)
Handle: 21
Page: 1/1
Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Secure Simple Pairing (Host Support)
< HCI Command: Remote Name Request (0x01|0x0019) plen 10 [hci0] 22.615583
Address: 10:B7:F6:01:31:ED (OUI 10-B7-F6)
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x0000
> HCI Event: Vendor (0xff) plen 2 [hci0] 22.616462
81 00 ..
> HCI Event: Command Status (0x0f) plen 4 [hci0] 22.617463
Remote Name Request (0x01|0x0019) ncmd 1
Status: Success (0x00)
> HCI Event: Link Key Request (0x17) plen 6 [hci0] 22.654535
Address: 10:B7:F6:01:31:ED (OUI 10-B7-F6)
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22 [hci0] 22.654580
Address: 10:B7:F6:01:31:ED (OUI 10-B7-F6)
Link key: 9a1e116ffd4baad792d15c680b35f152
> HCI Event: Command Complete (0x0e) plen 10 [hci0] 22.657473
Link Key Request Reply (0x01|0x000b) ncmd 1
Status: Success (0x00)
Address: 10:B7:F6:01:31:ED (OUI 10-B7-F6)
> HCI Event: Vendor (0xff) plen 2 [hci0] 22.659466
81 01 ..
> HCI Event: Remote Name Req Complete (0x07) plen 255 [hci0] 22.676479
Status: Success (0x00)
Address: 10:B7:F6:01:31:ED (OUI 10-B7-F6)
Name: Monster Clarity
@ Device Connected: 10:B7:F6:01:31:ED (0) flags 0x0000
10 09 4d 6f 6e 73 74 65 72 20 43 6c 61 72 69 74 ..Monster Clarit
79 04 0d 04 04 24 y....$
> HCI Event: Encryption Change (0x08) plen 4 [hci0] 22.729470
Status: Success (0x00)
Handle: 21
Encryption: Enabled with E0 (0x01)
> ACL Data RX: Handle 21 flags 0x02 dlen 12 [hci0] 22.741045
L2CAP: Connection Request (0x02) ident 2 len 4
PSM: 25 (0x0019)
Source CID: 65
< ACL Data TX: Handle 21 flags 0x00 dlen 16 [hci0] 22.741104
L2CAP: Connection Response (0x03) ident 2 len 8
Destination CID: 64
Source CID: 65
Result: Connection pending (0x0001)
Status: No further information available (0x0000)
< ACL Data TX: Handle 21 flags 0x00 dlen 10 [hci0] 22.741111
L2CAP: Information Request (0x0a) ident 1 len 2
Type: Extended features supported (0x0002)
> HCI Event: Vendor (0xff) plen 4 [hci0] 22.741466
86 03 15 00 ....
> HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 22.750463
Num handles: 1
Handle: 21
Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 22.751462
Num handles: 1
Handle: 21
Count: 1
> ACL Data RX: Handle 21 flags 0x02 dlen 16 [hci0] 22.757325
L2CAP: Information Response (0x0b) ident 1 len 8
Type: Extended features supported (0x0002)
Result: Success (0x0000)
Features: 0x00000000
< ACL Data TX: Handle 21 flags 0x00 dlen 16 [hci0] 22.757384
L2CAP: Connection Response (0x03) ident 2 len 8
Destination CID: 64
Source CID: 65
Result: Connection successful (0x0000)
Status: No further information available (0x0000)
< ACL Data TX: Handle 21 flags 0x00 dlen 12 [hci0] 22.757389
L2CAP: Configure Request (0x04) ident 2 len 4
Destination CID: 65
Flags: 0x0000
> HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 22.766471
Num handles: 1
Handle: 21
Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 22.767464
Num handles: 1
Handle: 21
Count: 1
> ACL Data RX: Handle 21 flags 0x02 dlen 16 [hci0] 22.783656
L2CAP: Configure Request (0x04) ident 3 len 8
Destination CID: 64
Flags: 0x0000
Option: Maximum Transmission Unit (0x01)
MTU: 895
< ACL Data TX: Handle 21 flags 0x00 dlen 18 [hci0] 22.783723
L2CAP: Configure Response (0x05) ident 3 len 10
Source CID: 65
Flags: 0x0000
Result: Success (0x0000)
Option: Maximum Transmission Unit (0x01)
MTU: 895
> ACL Data RX: Handle 21 flags 0x02 dlen 14 [hci0] 22.793532
L2CAP: Configure Response (0x05) ident 2 len 6
Source CID: 64
Flags: 0x0000
Result: Success (0x0000)
> HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 22.795469
Num handles: 1
Handle: 21
Count: 1
> ACL Data RX: Handle 21 flags 0x02 dlen 6 [hci0] 22.823472
Channel: 64 len 2 [PSM 25 mode 0] {chan 0}
10 01 ..
< ACL Data TX: Handle 21 flags 0x00 dlen 8 [hci0] 22.823644
Channel: 65 len 4 [PSM 25 mode 0] {chan 0}
12 01 04 00 ....
> HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 22.846535
Num handles: 1
Handle: 21
Count: 1
> ACL Data RX: Handle 21 flags 0x02 dlen 7 [hci0] 22.868472
Channel: 64 len 3 [PSM 25 mode 0] {chan 0}
20 02 04 ..
< ACL Data TX: Handle 21 flags 0x00 dlen 16 [hci0] 22.868659
Channel: 65 len 12 [PSM 25 mode 0] {chan 0}
22 02 01 00 07 06 00 00 22 15 02 33 "......."..3
> HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 22.892465
Num handles: 1
Handle: 21
Count: 1
> ACL Data RX: Handle 21 flags 0x02 dlen 18 [hci0] 22.934721
Channel: 64 len 14 [PSM 25 mode 0] {chan 0}
30 03 04 04 01 00 07 06 00 00 22 15 02 33 0........."..3
< ACL Data TX: Handle 21 flags 0x00 dlen 6 [hci0] 22.934848
Channel: 65 len 2 [PSM 25 mode 0] {chan 0}
32 03 2.
> HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 22.957466
Num handles: 1
Handle: 21
Count: 1
> ACL Data RX: Handle 21 flags 0x02 dlen 7 [hci0] 22.977206
Channel: 64 len 3 [PSM 25 mode 0] {chan 0}
40 06 04 @..
< ACL Data TX: Handle 21 flags 0x00 dlen 6 [hci0] 22.977276
Channel: 65 len 2 [PSM 25 mode 0] {chan 0}
42 06 B.
> HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 23.001471
Num handles: 1
Handle: 21
Count: 1
> ACL Data RX: Handle 21 flags 0x02 dlen 12 [hci0] 23.031050
L2CAP: Connection Request (0x02) ident 4 len 4
PSM: 25 (0x0019)
Source CID: 66
< ACL Data TX: Handle 21 flags 0x00 dlen 16 [hci0] 23.031137
L2CAP: Connection Response (0x03) ident 4 len 8
Destination CID: 65
Source CID: 66
Result: Connection successful (0x0000)
Status: No further information available (0x0000)
< ACL Data TX: Handle 21 flags 0x00 dlen 12 [hci0] 23.031147
L2CAP: Configure Request (0x04) ident 3 len 4
Destination CID: 66
Flags: 0x0000
> HCI Event: Vendor (0xff) plen 4 [hci0] 23.031458
86 03 15 00 ....
> HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 23.053469
Num handles: 1
Handle: 21
Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 23.055466
Num handles: 1
Handle: 21
Count: 1
> ACL Data RX: Handle 21 flags 0x02 dlen 16 [hci0] 23.079849
L2CAP: Configure Request (0x04) ident 5 len 8
Destination CID: 65
Flags: 0x0000
Option: Maximum Transmission Unit (0x01)
MTU: 895
< ACL Data TX: Handle 21 flags 0x00 dlen 18 [hci0] 23.079898
L2CAP: Configure Response (0x05) ident 5 len 10
Source CID: 66
Flags: 0x0000
Result: Success (0x0000)
Option: Maximum Transmission Unit (0x01)
MTU: 895
> ACL Data RX: Handle 21 flags 0x02 dlen 14 [hci0] 23.089835
L2CAP: Configure Response (0x05) ident 3 len 6
Source CID: 65
Flags: 0x0000
Result: Success (0x0000)
> HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 23.091465
Num handles: 1
Handle: 21
Count: 1
> HCI Event: Link Supervision Timeout Changed (0x38) plen 4 [hci0] 23.206472
Handle: 21
Timeout: 10080.000 msec (0x3f00)
> ACL Data RX: Handle 21 flags 0x02 dlen 7 [hci0] 23.219721
Channel: 64 len 3 [PSM 25 mode 0] {chan 0}
50 07 04 P..
< ACL Data TX: Handle 21 flags 0x00 dlen 6 [hci0] 23.219831
Channel: 65 len 2 [PSM 25 mode 0] {chan 0}
52 07 R.
> HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 23.233466
Num handles: 1
Handle: 21
Count: 1
> ACL Data RX: Handle 21 flags 0x02 dlen 12 [hci0] 23.282281
L2CAP: Connection Request (0x02) ident 6 len 4
PSM: 23 (0x0017)
Source CID: 67
< ACL Data TX: Handle 21 flags 0x00 dlen 16 [hci0] 23.282363
L2CAP: Connection Response (0x03) ident 6 len 8
Destination CID: 0
Source CID: 67
Result: Connection refused - PSM not supported (0x0002)
Status: No further information available (0x0000)
> HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 23.306540
Num handles: 1
Handle: 21
Count: 1
[-- Attachment #3: btmon_bluetoothd --]
[-- Type: application/octet-stream, Size: 12380 bytes --]
Bluetooth monitor ver 5.19
= New Index: 3C:77:E6:60:5C:B2 (BR/EDR,USB,hci0) [hci0] 0.564246
> HCI Event: Vendor (0xff) plen 2 [hci0] 21.526832
81 00 ..
> HCI Event: Connect Request (0x04) plen 10 [hci0] 21.527763
Address: 10:B7:F6:01:31:ED (OUI 10-B7-F6)
Class: 0x240404
Major class: Audio/Video (headset, speaker, stereo, video, vcr)
Minor class: Wearable Headset Device
Rendering (Printing, Speaker)
Audio (Speaker, Microphone, Headset)
Link type: ACL (0x01)
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7 [hci0] 21.527823
Address: 10:B7:F6:01:31:ED (OUI 10-B7-F6)
Role: Master (0x00)
> HCI Event: Command Status (0x0f) plen 4 [hci0] 21.528754
Accept Connection Request (0x01|0x0009) ncmd 1
Status: Success (0x00)
> HCI Event: Role Change (0x12) plen 8 [hci0] 21.680833
Status: Success (0x00)
Address: 10:B7:F6:01:31:ED (OUI 10-B7-F6)
Role: Master (0x00)
> HCI Event: Vendor (0xff) plen 2 [hci0] 21.752830
81 01 ..
> HCI Event: Vendor (0xff) plen 7 [hci0] 21.753762
82 00 00 00 01 15 00 .......
> HCI Event: Connect Complete (0x03) plen 11 [hci0] 21.754761
Status: Success (0x00)
Handle: 21
Address: 10:B7:F6:01:31:ED (OUI 10-B7-F6)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2 [hci0] 21.754922
Handle: 21
> HCI Event: Command Status (0x0f) plen 4 [hci0] 21.755754
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
> HCI Event: Read Remote Supported Features (0x0b) plen 11 [hci0] 21.791757
Status: Success (0x00)
Handle: 21
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83
3 slot packets
5 slot packets
Encryption
Slot offset
Timing accuracy
Role switch
Hold mode
Sniff mode
Park state
Power control requests
Channel quality driven data rate (CQDDR)
SCO link
HV2 packets
HV3 packets
u-law log synchronous data
A-law log synchronous data
CVSD synchronous data
Paging parameter negotiation
Power control
Transparent synchronous data
Broadcast Encryption
Enhanced Data Rate ACL 2 Mbps mode
Enhanced Data Rate ACL 3 Mbps mode
Enhanced inquiry scan
Interlaced inquiry scan
Interlaced page scan
RSSI with inquiry results
Extended SCO link (EV3 packets)
EV4 packets
EV5 packets
AFH capable slave
AFH classification slave
3-slot Enhanced Data Rate ACL packets
5-slot Enhanced Data Rate ACL packets
Sniff subrating
Pause encryption
AFH capable master
AFH classification master
Enhanced Data Rate eSCO 2 Mbps mode
Enhanced Data Rate eSCO 3 Mbps mode
3-slot Enhanced Data Rate eSCO packets
Extended Inquiry Response
Secure Simple Pairing
Encapsulated PDU
Non-flushable Packet Boundary Flag
Link Supervision Timeout Changed Event
Inquiry TX Power Level
Extended features
< HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3 [hci0] 21.791806
Handle: 21
Page: 1
> HCI Event: Command Status (0x0f) plen 4 [hci0] 21.792750
Read Remote Extended Features (0x01|0x001c) ncmd 1
Status: Success (0x00)
> HCI Event: Read Remote Extended Features (0x23) plen 13 [hci0] 21.801761
Status: Success (0x00)
Handle: 21
Page: 1/1
Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Secure Simple Pairing (Host Support)
< HCI Command: Remote Name Request (0x01|0x0019) plen 10 [hci0] 21.801798
Address: 10:B7:F6:01:31:ED (OUI 10-B7-F6)
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x0000
> HCI Event: Vendor (0xff) plen 2 [hci0] 21.802759
81 00 ..
> HCI Event: Command Status (0x0f) plen 4 [hci0] 21.803769
Remote Name Request (0x01|0x0019) ncmd 1
Status: Success (0x00)
> HCI Event: Vendor (0xff) plen 2 [hci0] 21.825755
81 01 ..
> HCI Event: Remote Name Req Complete (0x07) plen 255 [hci0] 21.842744
Status: Success (0x00)
Address: 10:B7:F6:01:31:ED (OUI 10-B7-F6)
Name: Monster Clarity
@ Device Connected: 10:B7:F6:01:31:ED (0) flags 0x0000
10 09 4d 6f 6e 73 74 65 72 20 43 6c 61 72 69 74 ..Monster Clarit
79 04 0d 04 04 24 y....$
> HCI Event: Link Key Request (0x17) plen 6 [hci0] 21.879776
Address: 10:B7:F6:01:31:ED (OUI 10-B7-F6)
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22 [hci0] 21.879877
Address: 10:B7:F6:01:31:ED (OUI 10-B7-F6)
Link key: 9a1e116ffd4baad792d15c680b35f152
> HCI Event: Command Complete (0x0e) plen 10 [hci0] 21.882760
Link Key Request Reply (0x01|0x000b) ncmd 1
Status: Success (0x00)
Address: 10:B7:F6:01:31:ED (OUI 10-B7-F6)
> HCI Event: Encryption Change (0x08) plen 4 [hci0] 21.996829
Status: Success (0x00)
Handle: 21
Encryption: Enabled with E0 (0x01)
> ACL Data RX: Handle 21 flags 0x02 dlen 12 [hci0] 21.997576
L2CAP: Connection Request (0x02) ident 2 len 4
PSM: 25 (0x0019)
Source CID: 65
< ACL Data TX: Handle 21 flags 0x00 dlen 16 [hci0] 21.997644
L2CAP: Connection Response (0x03) ident 2 len 8
Destination CID: 64
Source CID: 65
Result: Connection pending (0x0001)
Status: No further information available (0x0000)
< ACL Data TX: Handle 21 flags 0x00 dlen 10 [hci0] 21.997652
L2CAP: Information Request (0x0a) ident 1 len 2
Type: Extended features supported (0x0002)
> HCI Event: Vendor (0xff) plen 4 [hci0] 21.997755
86 03 15 00 ....
> HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 22.000760
Num handles: 1
Handle: 21
Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 22.001757
Num handles: 1
Handle: 21
Count: 1
> ACL Data RX: Handle 21 flags 0x02 dlen 16 [hci0] 22.030118
L2CAP: Information Response (0x0b) ident 1 len 8
Type: Extended features supported (0x0002)
Result: Success (0x0000)
Features: 0x00000000
< ACL Data TX: Handle 21 flags 0x00 dlen 16 [hci0] 22.030160
L2CAP: Connection Response (0x03) ident 2 len 8
Destination CID: 64
Source CID: 65
Result: Connection pending (0x0001)
Status: Authorization pending (0x0002)
< ACL Data TX: Handle 21 flags 0x00 dlen 16 [hci0] 22.030595
L2CAP: Connection Response (0x03) ident 2 len 8
Destination CID: 64
Source CID: 65
Result: Connection successful (0x0000)
Status: No further information available (0x0000)
< ACL Data TX: Handle 21 flags 0x00 dlen 12 [hci0] 22.030735
L2CAP: Configure Request (0x04) ident 2 len 4
Destination CID: 65
Flags: 0x0000
> HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 22.032754
Num handles: 1
Handle: 21
Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 22.033752
Num handles: 1
Handle: 21
Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 22.035751
Num handles: 1
Handle: 21
Count: 1
> ACL Data RX: Handle 21 flags 0x02 dlen 12 [hci0] 22.085097
L2CAP: Disconnection Request (0x06) ident 3 len 4
Destination CID: 64
Source CID: 65
< ACL Data TX: Handle 21 flags 0x00 dlen 12 [hci0] 22.085139
L2CAP: Disconnection Response (0x07) ident 3 len 4
Destination CID: 64
Source CID: 65
> HCI Event: Number of Completed Packets (0x13) plen 5 [hci0] 22.087762
Num handles: 1
Handle: 21
Count: 1
> HCI Event: Vendor (0xff) plen 7 [hci0] 22.354831
82 00 01 00 01 15 00 .......
> HCI Event: Disconnect Complete (0x05) plen 4 [hci0] 22.355759
Status: Success (0x00)
Handle: 21
Reason: Remote User Terminated Connection (0x13)
@ Device Disconnected: 10:B7:F6:01:31:ED (0) reason 3
next prev parent reply other threads:[~2014-08-20 22:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-26 1:33 [A2DP] Incoming connections do not succeed Artem Rakhov
2014-07-28 8:21 ` Luiz Augusto von Dentz
2014-07-29 0:24 ` Artem Rakhov
2014-07-29 5:16 ` Artem Rakhov
2014-07-29 5:29 ` Marcel Holtmann
2014-08-08 7:32 ` Artem Rakhov
2014-08-10 7:32 ` Luiz Augusto von Dentz
2014-08-11 6:07 ` Michal Labedzki
2014-08-18 7:11 ` Artem Rakhov
2014-08-20 22:52 ` Artem Rakhov [this message]
2014-08-20 22:54 ` Artem Rakhov
2014-08-21 6:42 ` Artem Rakhov
2014-08-21 8:38 ` Luiz Augusto von Dentz
2014-08-21 13:33 ` Marcel Holtmann
2014-08-21 13:53 ` Luiz Augusto von Dentz
2014-08-21 14:28 ` Marcel Holtmann
2014-08-21 19:16 ` Artem Rakhov
2014-08-21 20:24 ` Marcel Holtmann
2014-08-21 21:31 ` Artem Rakhov
2014-08-27 1:11 ` Artem Rakhov
2014-08-27 2:08 ` Marcel Holtmann
2014-08-27 6:33 ` Artem Rakhov
2014-08-27 18:34 ` Luiz Augusto von Dentz
2014-08-28 11:19 ` Luiz Augusto von Dentz
2014-08-28 20:37 ` Marcel Holtmann
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=CAD81oNZrVONCOTKtsXn2-A3a8KPy_qzU0HU3oO6Xw+FR5NqpQA@mail.gmail.com \
--to=arakhov@chromium.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--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 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.