LinuxLists.cc - Intel 7260 bluetooth malfunction when it is connected to EHCI bus

[permalink] [raw]

Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus

Hi Hui,

>>>>> The problem is:
>>>>> On the machine which has Intel 7260 BT module, i use it to connect a bluetooth headset,
>>>>> it can successfully scan and connect to the headset, when i play sound to the bt headset,
>>>>> the problem comes, if the bt module is connected to the XHCI, it can work very well.
>>>>>
>>>>> u@u-Lenovo-B4400:~$ lsusb -t
>>>>> 1-7:1.0: No such file or directory
>>>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>>>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>>>>> |__ Port 6: Dev 8, If 0, Class=HID, Driver=usbhid, 1.5M
>>>>> |__ Port 7: Dev 2, If 0, Class=vend., Driver=, 12M
>>>>> |__ Port 11: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>> |__ Port 11: Dev 3, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>>
>>>>> But if the bt module is connected to the EHCI, it always fails to play sound.
>>>>>
>>>>> u@u-Lenovo-B4400:~$ lsusb -t
>>>>> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>>>>> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>>>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
>>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
>>>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
>>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
>>>>> |__ Port 5: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>> |__ Port 5: Dev 3, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>> |__ Port 6: Dev 4, If 0, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
>>>>> |__ Port 6: Dev 4, If 1, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
>>>> can you paste /sys/kernel/debug/usb/devices here.
>>>>
>>>> If the uvcvideo driver is also using ISOC URBs, we might have just exhausted the bandwidth of the USB bus here or these two devices just do not play nice with each other.
>>>>
>>>> Try to unload the uvcvideo driver and try it again.
>>> Thanks for your reply, follow your instruction, i totally disabled the camera from the BIOS, then the usb tree like this,
>>> u@u-Lenovo-B4400:~$ lsusb -t
>>> 1-1.3:1.0: No such file or directory
>>> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>>> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
>>> |__ Port 2: Dev 3, If 0, Class=HID, Driver=usbhid, 1.5M
>>> |__ Port 3: Dev 4, If 0, Class=vend., Driver=, 12M
>>> |__ Port 5: Dev 5, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>> |__ Port 5: Dev 5, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>> u@u-Lenovo-B4400:~$ uname -a
>>> Linux u-Lenovo-B4400 3.12.0-031200rc6-generic #201310191635 SMP Sat Oct 19 20:36:43 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>>>
>>> I re-did the test, the result is same as before, after the headset is connected and i play audio, no sound is heard from the headset.
>>> And hciconfig output shows still no SCO packets received by BT driver.
>>> u@u-Lenovo-B4400:~$ hciconfig
>>> hci0: Type: BR/EDR Bus: USB
>>> BD Address: 00:15:00:CC:2D:D2 ACL MTU: 1021:5 SCO MTU: 96:5
>>> UP RUNNING PSCAN
>>> RX bytes:5853 acl:61 sco:0 events:298 errors:0
>>> TX bytes:19212 acl:68 sco:1 commands:179 errors:0
>> this is strange. The only reason I can think of is that you do not have the firmware installed and or it is not loaded correctly. Does dmesg give any indication that something failed here.
> I can confirm the firmware file is the /lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq, and it is in the filesystem. And from the dmesg, the firmware was successfully loaded.
>
> [ 8.600217] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
> [ 8.653635] kvm: disabled by bios
> [ 8.672981] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xd00123/0x840300/0x126c00
> [ 8.707034] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input13
> [ 8.717725] Registered led device: phy0-led
> [ 8.722730] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
> [ 8.752626] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
>
>> Since this is a 3.12 kernel it should have native support for Intel specific setup routing. Any chance you can run btmon -w <file> before plugging the device into the bus. Maybe something goes wrong with the setup routine on EHCI.
> Do you mean the hcidump file i just sent in my previous email.

I do not get this. I specifically asked to run ?btmon -w <file>? before plugging in the device. I want to see the early setup process here. What would I do with a hcidump trace.

Regards

Marcel

2013-10-31 05:29:06

[permalink] [raw]

Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus

On 10/31/2013 03:44 AM, Marcel Holtmann wrote:
> Hi Hui,
>
>>>> The problem is:
>>>> On the machine which has Intel 7260 BT module, i use it to connect a bluetooth headset,
>>>> it can successfully scan and connect to the headset, when i play sound to the bt headset,
>>>> the problem comes, if the bt module is connected to the XHCI, it can work very well.
>>>>
>>>> u@u-Lenovo-B4400:~$ lsusb -t
>>>> 1-7:1.0: No such file or directory
>>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>>>> |__ Port 6: Dev 8, If 0, Class=HID, Driver=usbhid, 1.5M
>>>> |__ Port 7: Dev 2, If 0, Class=vend., Driver=, 12M
>>>> |__ Port 11: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>> |__ Port 11: Dev 3, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>
>>>> But if the bt module is connected to the EHCI, it always fails to play sound.
>>>>
>>>> u@u-Lenovo-B4400:~$ lsusb -t
>>>> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>>>> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
>>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
>>>> |__ Port 5: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>> |__ Port 5: Dev 3, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>> |__ Port 6: Dev 4, If 0, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
>>>> |__ Port 6: Dev 4, If 1, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
>>> can you paste /sys/kernel/debug/usb/devices here.
>>>
>>> If the uvcvideo driver is also using ISOC URBs, we might have just exhausted the bandwidth of the USB bus here or these two devices just do not play nice with each other.
>>>
>>> Try to unload the uvcvideo driver and try it again.
>> Thanks for your reply, follow your instruction, i totally disabled the camera from the BIOS, then the usb tree like this,
>> u@u-Lenovo-B4400:~$ lsusb -t
>> 1-1.3:1.0: No such file or directory
>> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
>> |__ Port 2: Dev 3, If 0, Class=HID, Driver=usbhid, 1.5M
>> |__ Port 3: Dev 4, If 0, Class=vend., Driver=, 12M
>> |__ Port 5: Dev 5, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>> |__ Port 5: Dev 5, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>> u@u-Lenovo-B4400:~$ uname -a
>> Linux u-Lenovo-B4400 3.12.0-031200rc6-generic #201310191635 SMP Sat Oct 19 20:36:43 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>>
>> I re-did the test, the result is same as before, after the headset is connected and i play audio, no sound is heard from the headset.
>> And hciconfig output shows still no SCO packets received by BT driver.
>> u@u-Lenovo-B4400:~$ hciconfig
>> hci0: Type: BR/EDR Bus: USB
>> BD Address: 00:15:00:CC:2D:D2 ACL MTU: 1021:5 SCO MTU: 96:5
>> UP RUNNING PSCAN
>> RX bytes:5853 acl:61 sco:0 events:298 errors:0
>> TX bytes:19212 acl:68 sco:1 commands:179 errors:0
> this is strange. The only reason I can think of is that you do not have the firmware installed and or it is not loaded correctly. Does dmesg give any indication that something failed here.
I can confirm the firmware file is the
/lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq, and it is in the
filesystem. And from the dmesg, the firmware was successfully loaded.

[ 8.600217] Bluetooth: hci0: Intel Bluetooth firmware file:
intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
[ 8.653635] kvm: disabled by bios
[ 8.672981] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1,
id: 0x1e2b1, caps: 0xd00123/0x840300/0x126c00
[ 8.707034] input: SynPS/2 Synaptics TouchPad as
/devices/platform/i8042/serio1/input/input13
[ 8.717725] Registered led device: phy0-led
[ 8.722730] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[ 8.752626] Bluetooth: hci0: Intel Bluetooth firmware patch completed
and activated

> Since this is a 3.12 kernel it should have native support for Intel specific setup routing. Any chance you can run btmon -w <file> before plugging the device into the bus. Maybe something goes wrong with the setup routine on EHCI.
Do you mean the hcidump file i just sent in my previous email.

In case some of you can't receive the attachment, i decode the log file
here:

u@u-Lenovo-K4450:~$ hcidump -r lenovo-k4450-bt-ascii-hex.log
HCI sniffer - Bluetooth packet analyzer ver 2.2
btsnoop version: 1 datalink type: 1002
> HCI Event: Connect Request (0x04) plen 10
bdaddr 78:F7:BE:08:5E:DF class 0x240404 type ACL
> HCI Event: Command Status (0x0f) plen 4
Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
status 0x00 handle 256 bdaddr 78:F7:BE:08:5E:DF type ACL encrypt 0x00
> HCI Event: Command Status (0x0f) plen 4
Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
> HCI Event: Read Remote Supported Features (0x0b) plen 11
status 0x00 handle 256
Features: 0xbf 0xfe 0x8f 0xfe 0x9b 0xff 0x79 0x87
> HCI Event: Command Status (0x0f) plen 4
Read Remote Extended Features (0x01|0x001c) status 0x00 ncmd 1
> HCI Event: Read Remote Extended Features (0x23) plen 13
status 0x00 handle 256 page 1 max 0
Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> HCI Event: Command Status (0x0f) plen 4
Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
> HCI Event: Remote Name Req Complete (0x07) plen 255
status 0x00 bdaddr 78:F7:BE:08:5E:DF name 'HM1700'
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Negative Reply (0x01|0x000c) ncmd 1
status 0x00 bdaddr 78:F7:BE:08:5E:DF
> HCI Event: Command Complete (0x0e) plen 10
IO Capability Request Reply (0x01|0x002b) ncmd 1
status 0x00 bdaddr 78:F7:BE:08:5E:DF
> HCI Event: Command Complete (0x0e) plen 10
User Confirmation Request Negative Reply (0x01|0x002d) ncmd 1
status 0x00 bdaddr 78:F7:BE:08:5E:DF
> HCI Event: Disconn Complete (0x05) plen 4
status 0x00 handle 256 reason 0x13
Reason: Remote User Terminated Connection
> HCI Event: Command Status (0x0f) plen 4
Inquiry (0x01|0x0001) status 0x00 ncmd 2
> HCI Event: Extended Inquiry Result (0x2f) plen 255
bdaddr 78:F7:BE:08:5E:DF mode 1 clkoffset 0x0391 class 0x240404
rssi -52
Unknown type 0x48 with 8 bytes data
Shortened local name: '..'
> HCI Event: Command Complete (0x0e) plen 4
Inquiry Cancel (0x01|0x0002) ncmd 2
status 0x00
> HCI Event: Command Status (0x0f) plen 4
Create Connection (0x01|0x0005) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
status 0x00 handle 256 bdaddr 78:F7:BE:08:5E:DF type ACL encrypt 0x00
> HCI Event: Command Status (0x0f) plen 4
Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
> HCI Event: Read Remote Supported Features (0x0b) plen 11
status 0x00 handle 256
Features: 0xbf 0xfe 0x8f 0xfe 0x9b 0xff 0x79 0x87
> HCI Event: Command Status (0x0f) plen 4
Read Remote Extended Features (0x01|0x001c) status 0x00 ncmd 1
> HCI Event: Read Remote Extended Features (0x23) plen 13
status 0x00 handle 256 page 1 max 0
Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> HCI Event: Command Status (0x0f) plen 4
Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
> HCI Event: Remote Name Req Complete (0x07) plen 255
status 0x00 bdaddr 78:F7:BE:08:5E:DF name 'HM1700'
> HCI Event: Command Status (0x0f) plen 4
Authentication Requested (0x01|0x0011) status 0x00 ncmd 1
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Negative Reply (0x01|0x000c) ncmd 1
status 0x00 bdaddr 78:F7:BE:08:5E:DF
> HCI Event: Command Complete (0x0e) plen 10
IO Capability Request Reply (0x01|0x002b) ncmd 1
status 0x00 bdaddr 78:F7:BE:08:5E:DF
> HCI Event: Command Complete (0x0e) plen 10
User Confirmation Request Reply (0x01|0x002c) ncmd 1
status 0x00 bdaddr 78:F7:BE:08:5E:DF
> HCI Event: Auth Complete (0x06) plen 3
status 0x00 handle 256
> HCI Event: Command Status (0x0f) plen 4
Set Connection Encryption (0x01|0x0013) status 0x00 ncmd 1
> HCI Event: Encrypt Change (0x08) plen 4
status 0x00 handle 256 encrypt 0x01
> HCI Event: Command Status (0x0f) plen 4
Setup Synchronous Connection (0x01|0x0028) status 0x00 ncmd 1
> HCI Event: Synchronous Connect Complete (0x2c) plen 17
status 0x00 handle 257 bdaddr 78:F7:BE:08:5E:DF type eSCO
Air mode: CVSD
> HCI Event: Command Status (0x0f) plen 4
Disconnect (0x01|0x0006) status 0x00 ncmd 1
> HCI Event: Disconn Complete (0x05) plen 4
status 0x00 handle 257 reason 0x16
Reason: Connection Terminated by Local Host
> HCI Event: Command Status (0x0f) plen 4
Setup Synchronous Connection (0x01|0x0028) status 0x00 ncmd 1
> HCI Event: Synchronous Connect Complete (0x2c) plen 17
status 0x00 handle 257 bdaddr 78:F7:BE:08:5E:DF type eSCO
Air mode: CVSD
> HCI Event: Command Status (0x0f) plen 4
Disconnect (0x01|0x0006) status 0x00 ncmd 1

Regards,
Hui.

>
> Regards
>
> Marcel
>
>

2013-10-31 05:15:42

[permalink] [raw]

Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus

On 10/31/2013 03:36 AM, Tedd Ho-Jeong An wrote:
>
> On Wednesday, October 30, 2013 10:51:20 AM Hui Wang wrote:
>
> > On 10/29/2013 07:16 PM, Marcel Holtmann wrote:
>
> > > Hi Hui,
>
> > >
>
> > >> The problem is:
>
> > >> On the machine which has Intel 7260 BT module, i use it to connect a
>
> > >> bluetooth headset, it can successfully scan and connect to the
> headset,
>
> > >> when i play sound to the bt headset, the problem comes, if the bt
> module
>
> > >> is connected to the XHCI, it can work very well.
>
> > >>
>
> > >> u@u-Lenovo-B4400:~$ lsusb -t
>
> > >> 1-7:1.0: No such file or directory
>
> > >> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>
<snip>
>
> >
>
> > > Regards
>
> > >
>
> > > Marcel
>
> Hi Hui,
>
> Could you capture the HCI dump and send to me? Also, what's the
> platform/machine are you using for testing?
>
> Regards,
>
> Tedd
>

Hi Tedd,

The attachment is the log generated by hcidump, i used below commands to
generate the log,

$hcidump -w ./lenovo-k4450-bt-ascii-hex.log -X -t

Then i start the bluetooth scan from the ubuntu bluetooth applet

it found the hm1700 headset, then it connected the headset successfully

play sound to the headset, can't hear any sound

Ctrl+C to terminate the hcidump

I have three machines on which install the intel 7260 BT module
(8087:07dc), and BT module firmware version is 370710018002030d2e, and
those modules are connected to the EHCI bus, they all have the same
problem when i want them to work with the BT headset. The three machines
are lenovo b4400, lenovo k4450 and lenovo m4400s.

I also have dozens of other machines on which the 7260 BT modules are
connected to XHCI, they all work well to play sound to a headset.

So do you think it is a firmware issue?

Regards,
Hui.

Attachments:

lenovo-k4450-bt-ascii-hex.log (2.01 kB)

2013-10-30 19:44:35

[permalink] [raw]

Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus

Hi Hui,

>>> The problem is:
>>> On the machine which has Intel 7260 BT module, i use it to connect a bluetooth headset,
>>> it can successfully scan and connect to the headset, when i play sound to the bt headset,
>>> the problem comes, if the bt module is connected to the XHCI, it can work very well.
>>>
>>> u@u-Lenovo-B4400:~$ lsusb -t
>>> 1-7:1.0: No such file or directory
>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>>> |__ Port 6: Dev 8, If 0, Class=HID, Driver=usbhid, 1.5M
>>> |__ Port 7: Dev 2, If 0, Class=vend., Driver=, 12M
>>> |__ Port 11: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>> |__ Port 11: Dev 3, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>
>>> But if the bt module is connected to the EHCI, it always fails to play sound.
>>>
>>> u@u-Lenovo-B4400:~$ lsusb -t
>>> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>>> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
>>> |__ Port 5: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>> |__ Port 5: Dev 3, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>> |__ Port 6: Dev 4, If 0, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
>>> |__ Port 6: Dev 4, If 1, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
>> can you paste /sys/kernel/debug/usb/devices here.
>>
>> If the uvcvideo driver is also using ISOC URBs, we might have just exhausted the bandwidth of the USB bus here or these two devices just do not play nice with each other.
>>
>> Try to unload the uvcvideo driver and try it again.
> Thanks for your reply, follow your instruction, i totally disabled the camera from the BIOS, then the usb tree like this,
> u@u-Lenovo-B4400:~$ lsusb -t
> 1-1.3:1.0: No such file or directory
> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
> |__ Port 2: Dev 3, If 0, Class=HID, Driver=usbhid, 1.5M
> |__ Port 3: Dev 4, If 0, Class=vend., Driver=, 12M
> |__ Port 5: Dev 5, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
> |__ Port 5: Dev 5, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
> u@u-Lenovo-B4400:~$ uname -a
> Linux u-Lenovo-B4400 3.12.0-031200rc6-generic #201310191635 SMP Sat Oct 19 20:36:43 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>
> I re-did the test, the result is same as before, after the headset is connected and i play audio, no sound is heard from the headset.
> And hciconfig output shows still no SCO packets received by BT driver.
> u@u-Lenovo-B4400:~$ hciconfig
> hci0: Type: BR/EDR Bus: USB
> BD Address: 00:15:00:CC:2D:D2 ACL MTU: 1021:5 SCO MTU: 96:5
> UP RUNNING PSCAN
> RX bytes:5853 acl:61 sco:0 events:298 errors:0
> TX bytes:19212 acl:68 sco:1 commands:179 errors:0

this is strange. The only reason I can think of is that you do not have the firmware installed and or it is not loaded correctly. Does dmesg give any indication that something failed here.

Since this is a 3.12 kernel it should have native support for Intel specific setup routing. Any chance you can run btmon -w <file> before plugging the device into the bus. Maybe something goes wrong with the setup routine on EHCI.

Regards

Marcel

2013-10-30 19:36:21

by An, Tedd

[permalink] [raw]

Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus

On Wednesday, October 30, 2013 10:51:20 AM Hui Wang wrote:
> On 10/29/2013 07:16 PM, Marcel Holtmann wrote:
> > Hi Hui,
> >
> >> The problem is:
> >> On the machine which has Intel 7260 BT module, i use it to connect a
> >> bluetooth headset, it can successfully scan and connect to the headset,
> >> when i play sound to the bt headset, the problem comes, if the bt module
> >> is connected to the XHCI, it can work very well.
> >>
> >> u@u-Lenovo-B4400:~$ lsusb -t
> >> 1-7:1.0: No such file or directory
> >> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
> >> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
> >>
> >> |__ Port 6: Dev 8, If 0, Class=HID, Driver=usbhid, 1.5M
> >> |__ Port 7: Dev 2, If 0, Class=vend., Driver=, 12M
> >> |__ Port 11: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet
> >> |handled', Driver=btusb, 12M __ Port 11: Dev 3, If 1,
> >> |Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M>>
> >> But if the bt module is connected to the EHCI, it always fails to play
> >> sound.
> >>
> >> u@u-Lenovo-B4400:~$ lsusb -t
> >> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
> >> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
> >> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
> >>
> >> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
> >>
> >> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
> >>
> >> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
> >> |
> >> |__ Port 5: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet
> >> |handled', Driver=btusb, 12M __ Port 5: Dev 3, If 1,
> >> |Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
> >> |__ Port 6: Dev 4, If 0, Class='bInterfaceClass 0x0e not yet
> >> |handled', Driver=uvcvideo, 480M __ Port 6: Dev 4, If 1,
> >> |Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo,
> >> |480M>
> > can you paste /sys/kernel/debug/usb/devices here.
> >
> > If the uvcvideo driver is also using ISOC URBs, we might have just
> > exhausted the bandwidth of the USB bus here or these two devices just do
> > not play nice with each other.
> >
> > Try to unload the uvcvideo driver and try it again.
>
> Thanks for your reply, follow your instruction, i totally disabled the
> camera from the BIOS, then the usb tree like this,
> u@u-Lenovo-B4400:~$ lsusb -t
> 1-1.3:1.0: No such file or directory
> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
>
> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
>
> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
>
> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
> |
> |__ Port 2: Dev 3, If 0, Class=HID, Driver=usbhid, 1.5M
> |__ Port 3: Dev 4, If 0, Class=vend., Driver=, 12M
> |__ Port 5: Dev 5, If 0, Class='bInterfaceClass 0xe0 not yet
>
> handled', Driver=btusb, 12M
>
> |__ Port 5: Dev 5, If 1, Class='bInterfaceClass 0xe0 not yet
>
> handled', Driver=btusb, 12M
> u@u-Lenovo-B4400:~$ uname -a
> Linux u-Lenovo-B4400 3.12.0-031200rc6-generic #201310191635 SMP Sat Oct
> 19 20:36:43 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>
> I re-did the test, the result is same as before, after the headset is
> connected and i play audio, no sound is heard from the headset.
> And hciconfig output shows still no SCO packets received by BT driver.
> u@u-Lenovo-B4400:~$ hciconfig
> hci0: Type: BR/EDR Bus: USB
> BD Address: 00:15:00:CC:2D:D2 ACL MTU: 1021:5 SCO MTU: 96:5
> UP RUNNING PSCAN
> RX bytes:5853 acl:61 sco:0 events:298 errors:0
> TX bytes:19212 acl:68 sco:1 commands:179 errors:0
>
> This is the debug output of "sudo cat /sys/kernel/debug/usb/devices"
> after those operations,
> u@u-Lenovo-B4400:~$ sudo cat /sys/kernel/debug/usb/devices
>
> T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=5000 MxCh= 4
> B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
> D: Ver= 3.00 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1
> P: Vendor=1d6b ProdID=0003 Rev= 3.05
> S: Manufacturer=Linux 3.12.0-rc6-WR5.0.1.4_standard+ xhci_hcd
> S: Product=xHCI Host Controller
> S: SerialNumber=0000:00:14.0
> C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
> I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
> E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms
>
> T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=14
> B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
> D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
> P: Vendor=1d6b ProdID=0002 Rev= 3.05
> S: Manufacturer=Linux 3.12.0-rc6-WR5.0.1.4_standard+ xhci_hcd
> S: Product=xHCI Host Controller
> S: SerialNumber=0000:00:14.0
> C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
> I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
> E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms
>
> T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 3
> B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
> D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
> P: Vendor=1d6b ProdID=0002 Rev= 3.05
> S: Manufacturer=Linux 3.12.0-rc6-WR5.0.1.4_standard+ ehci_hcd
> S: Product=EHCI Host Controller

2013-10-30 02:51:20

[permalink] [raw]

Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus

On 10/29/2013 07:16 PM, Marcel Holtmann wrote:
> Hi Hui,
>
>> The problem is:
>> On the machine which has Intel 7260 BT module, i use it to connect a bluetooth headset,
>> it can successfully scan and connect to the headset, when i play sound to the bt headset,
>> the problem comes, if the bt module is connected to the XHCI, it can work very well.
>>
>> u@u-Lenovo-B4400:~$ lsusb -t
>> 1-7:1.0: No such file or directory
>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>> |__ Port 6: Dev 8, If 0, Class=HID, Driver=usbhid, 1.5M
>> |__ Port 7: Dev 2, If 0, Class=vend., Driver=, 12M
>> |__ Port 11: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>> |__ Port 11: Dev 3, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>
>> But if the bt module is connected to the EHCI, it always fails to play sound.
>>
>> u@u-Lenovo-B4400:~$ lsusb -t
>> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
>> |__ Port 5: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>> |__ Port 5: Dev 3, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>> |__ Port 6: Dev 4, If 0, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
>> |__ Port 6: Dev 4, If 1, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
> can you paste /sys/kernel/debug/usb/devices here.
>
> If the uvcvideo driver is also using ISOC URBs, we might have just exhausted the bandwidth of the USB bus here or these two devices just do not play nice with each other.
>
> Try to unload the uvcvideo driver and try it again.
Thanks for your reply, follow your instruction, i totally disabled the
camera from the BIOS, then the usb tree like this,
u@u-Lenovo-B4400:~$ lsusb -t
1-1.3:1.0: No such file or directory
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
|__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
|__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
|__ Port 2: Dev 3, If 0, Class=HID, Driver=usbhid, 1.5M
|__ Port 3: Dev 4, If 0, Class=vend., Driver=, 12M
|__ Port 5: Dev 5, If 0, Class='bInterfaceClass 0xe0 not yet
handled', Driver=btusb, 12M
|__ Port 5: Dev 5, If 1, Class='bInterfaceClass 0xe0 not yet
handled', Driver=btusb, 12M
u@u-Lenovo-B4400:~$ uname -a
Linux u-Lenovo-B4400 3.12.0-031200rc6-generic #201310191635 SMP Sat Oct
19 20:36:43 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

I re-did the test, the result is same as before, after the headset is
connected and i play audio, no sound is heard from the headset.
And hciconfig output shows still no SCO packets received by BT driver.
u@u-Lenovo-B4400:~$ hciconfig
hci0: Type: BR/EDR Bus: USB
BD Address: 00:15:00:CC:2D:D2 ACL MTU: 1021:5 SCO MTU: 96:5
UP RUNNING PSCAN
RX bytes:5853 acl:61 sco:0 events:298 errors:0
TX bytes:19212 acl:68 sco:1 commands:179 errors:0

This is the debug output of "sudo cat /sys/kernel/debug/usb/devices"
after those operations,
u@u-Lenovo-B4400:~$ sudo cat /sys/kernel/debug/usb/devices

T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=5000 MxCh= 4
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 3.00 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1
P: Vendor=1d6b ProdID=0003 Rev= 3.05
S: Manufacturer=Linux 3.12.0-rc6-WR5.0.1.4_standard+ xhci_hcd
S: Product=xHCI Host Controller
S: SerialNumber=0000:00:14.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms

T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=14
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev= 3.05
S: Manufacturer=Linux 3.12.0-rc6-WR5.0.1.4_standard+ xhci_hcd
S: Product=xHCI Host Controller
S: SerialNumber=0000:00:14.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms

T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 3
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev= 3.05
S: Manufacturer=Linux 3.12.0-rc6-WR5.0.1.4_standard+ ehci_hcd
S: Product=EHCI Host Controller
S: SerialNumber=0000:00:1d.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms

T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 8
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=8087 ProdID=8000 Rev= 0.05
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms

T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 3
B: Alloc= 4/800 us ( 1%), #Int= 3, #Iso= 1
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev= 3.05
S: Manufacturer=Linux 3.12.0-rc6-WR5.0.1.4_standard+ ehci_hcd
S: Product=EHCI Host Controller
S: SerialNumber=0000:00:1a.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms

T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 6
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=8087 ProdID=8008 Rev= 0.05
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=256ms

T: Bus=01 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#= 3 Spd=1.5 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0461 ProdID=4d22 Rev= 2.00
S: Product=USB Optical Mouse
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=10ms

T: Bus=01 Lev=02 Prnt=02 Port=02 Cnt=02 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=ff(vend.) Sub=11 Prot=ff MxPS= 8 #Cfgs= 1
P: Vendor=138a ProdID=0011 Rev= 0.78
S: SerialNumber=7ffcdfda8afe
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 4 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=83(I) Atr=03(Int.) MxPS= 8 Ivl=4ms

T: Bus=01 Lev=02 Prnt=02 Port=04 Cnt=03 Dev#= 5 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=8087 ProdID=07dc Rev= 0.01
C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=1ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
I:* If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms

Thanks,
Hui.

>
> Regards
>
> Marcel
>
>
>

2013-10-29 11:16:58

[permalink] [raw]

Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus

Hi Hui,

> The problem is:
> On the machine which has Intel 7260 BT module, i use it to connect a bluetooth headset,
> it can successfully scan and connect to the headset, when i play sound to the bt headset,
> the problem comes, if the bt module is connected to the XHCI, it can work very well.
>
> u@u-Lenovo-B4400:~$ lsusb -t
> 1-7:1.0: No such file or directory
> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
> |__ Port 6: Dev 8, If 0, Class=HID, Driver=usbhid, 1.5M
> |__ Port 7: Dev 2, If 0, Class=vend., Driver=, 12M
> |__ Port 11: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
> |__ Port 11: Dev 3, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>
> But if the bt module is connected to the EHCI, it always fails to play sound.
>
> u@u-Lenovo-B4400:~$ lsusb -t
> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
> |__ Port 5: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
> |__ Port 5: Dev 3, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
> |__ Port 6: Dev 4, If 0, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
> |__ Port 6: Dev 4, If 1, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M

can you paste /sys/kernel/debug/usb/devices here.

If the uvcvideo driver is also using ISOC URBs, we might have just exhausted the bandwidth of the USB bus here or these two devices just do not play nice with each other.

Try to unload the uvcvideo driver and try it again.

Regards

Marcel

2013-11-26 09:11:47

by Michal Labedzki

[permalink] [raw]

Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus

Bug is now fixed in "svn path=3D/trunk/; revision=3D53525". You can wait
for next development (1.11.3) or stable (1.12), however you can build
Wireshark from sources (should be easy - like BlueZ: git clone
http://code.wireshark.org/git/wireshark; ./autogen; ./configure; make;
./wireshark) or via "private" sources like:
$ sudo add-apt-repository ppa:dreibh/ppa
$ sudo apt-get update
$ sudo apt-get install wireshark

On 8 November 2013 12:17, Michal Labedzki <[email protected]> wrote=
:
> Hello,
>
> Could you create a bug for Wireshark? (capture log are welcome)
> https://bugs.wireshark.org/bugzilla/buglist.cgi?resolution=3D---&query_fo=
rmat=3Dadvanced&list_id=3D11313
>
> I check and that is right. There are two commands shares the same
> code. "Setup Synchronous Connection" and "Accept Synchronous
> Connection Request". But second one should be different. I can fix
> that.
> Also I recommend to try latest development Wireshark - it is generally st=
able.
>
> On 8 November 2013 02:43, Hui Wang <[email protected]> wrote:
>> On 11/07/2013 06:07 PM, Stevie Trujillo wrote:
>>>
>>> On Thu, 07 Nov 2013 11:45:53 +0800
>>> Hui Wang <[email protected]> wrote:
>>>
>>>> Do you know any tools can decode the log generated by usbmon?
>>>
>>> Hmm, I never actually used the usbmon program. I did "modprobe usbmon",
>>> then Wireshark shows usbmon{1..4} (one for each bus) as an interface
>>> like eth0 for ethernet. http://wiki.wireshark.org/CaptureSetup/USB
>>>
>>> If it's difficult to compare two captures in Wireshark (I don't know an=
y
>>> other method than visual inspection), tshark (Wireshark's "command-line
>>> counter-part") is able to decode to stdout. Maybe one can run the diff
>>> program on that. The output seems a bit terse however.
>>>
>>> Please be aware: in my Wireshark (1.10.2) one of the of the SCO setup
>>> packets are decoded slightly wrong. It looks like Wireshark is missing
>>> a BDADDR in the beginning, so all the other fields get shifted.
>>>
>>>
>> Thanks for sharing this knowledge, i will have a try according to your
>> instructions.
>>
>> Regards,
>> Hui.
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-bluetoot=
h"
>> in
>> the body of a message to [email protected]
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
> --
>
> Pozdrawiam / Best regards
> -------------------------------------------------------------------------=
------------------------------------
> Micha=C5=82 =C5=81ab=C4=99dzki, Software Engineer
> Tieto Corporation
>
> Product Development Services
>
> http://www.tieto.com / http://www.tieto.pl
> ---
> ASCII: Michal Labedzki
> location: Swobodna 1 Street, 50-088 Wroc=C5=82aw, Poland
> room: 5.01 (desk next to 5.08)
> ---
> Please note: The information contained in this message may be legally
> privileged and confidential and protected from disclosure. If the
> reader of this message is not the intended recipient, you are hereby
> notified that any unauthorised use, distribution or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, please notify us immediately by replying to
> the message and deleting it from your computer. Thank You.
> ---
> Please consider the environment before printing this e-mail.
> ---
> Tieto Poland sp=C3=B3=C5=82ka z ograniczon=C4=85 odpowiedzialno=C5=9Bci=
=C4=85 z siedzib=C4=85 w
> Szczecinie, ul. Malczewskiego 26. Zarejestrowana w S=C4=85dzie Rejonowym
> Szczecin-Centrum w Szczecinie, XIII Wydzia=C5=82 Gospodarczy Krajowego
> Rejestru S=C4=85dowego pod numerem 0000124858. NIP: 8542085557. REGON:
> 812023656. Kapita=C5=82 zak=C5=82adowy: 4 271500 PLN

--=20

Pozdrawiam / Best regards
---------------------------------------------------------------------------=
----------------------------------
Micha=C5=82 =C5=81ab=C4=99dzki, Software Engineer
Tieto Corporation

Product Development Services

http://www.tieto.com / http://www.tieto.pl
---
ASCII: Michal Labedzki
location: Swobodna 1 Street, 50-088 Wroc=C5=82aw, Poland
room: 5.01 (desk next to 5.08)
---
Please note: The information contained in this message may be legally
privileged and confidential and protected from disclosure. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorised use, distribution or copying of this
communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to
the message and deleting it from your computer. Thank You.
---
Please consider the environment before printing this e-mail.
---
Tieto Poland sp=C3=B3=C5=82ka z ograniczon=C4=85 odpowiedzialno=C5=9Bci=C4=
=85 z siedzib=C4=85 w
Szczecinie, ul. Malczewskiego 26. Zarejestrowana w S=C4=85dzie Rejonowym
Szczecin-Centrum w Szczecinie, XIII Wydzia=C5=82 Gospodarczy Krajowego
Rejestru S=C4=85dowego pod numerem 0000124858. NIP: 8542085557. REGON:
812023656. Kapita=C5=82 zak=C5=82adowy: 4 271500 PLN

2013-11-08 11:17:00

by Michal Labedzki

[permalink] [raw]

Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus

Hello,

Could you create a bug for Wireshark? (capture log are welcome)
https://bugs.wireshark.org/bugzilla/buglist.cgi?resolution=3D---&query_form=
at=3Dadvanced&list_id=3D11313

I check and that is right. There are two commands shares the same
code. "Setup Synchronous Connection" and "Accept Synchronous
Connection Request". But second one should be different. I can fix
that.
Also I recommend to try latest development Wireshark - it is generally stab=
le.

On 8 November 2013 02:43, Hui Wang <[email protected]> wrote:
> On 11/07/2013 06:07 PM, Stevie Trujillo wrote:
>>
>> On Thu, 07 Nov 2013 11:45:53 +0800
>> Hui Wang <[email protected]> wrote:
>>
>>> Do you know any tools can decode the log generated by usbmon?
>>
>> Hmm, I never actually used the usbmon program. I did "modprobe usbmon",
>> then Wireshark shows usbmon{1..4} (one for each bus) as an interface
>> like eth0 for ethernet. http://wiki.wireshark.org/CaptureSetup/USB
>>
>> If it's difficult to compare two captures in Wireshark (I don't know any
>> other method than visual inspection), tshark (Wireshark's "command-line
>> counter-part") is able to decode to stdout. Maybe one can run the diff
>> program on that. The output seems a bit terse however.
>>
>> Please be aware: in my Wireshark (1.10.2) one of the of the SCO setup
>> packets are decoded slightly wrong. It looks like Wireshark is missing
>> a BDADDR in the beginning, so all the other fields get shifted.
>>
>>
> Thanks for sharing this knowledge, i will have a try according to your
> instructions.
>
> Regards,
> Hui.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth=
"
> in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html

--=20

Pozdrawiam / Best regards
---------------------------------------------------------------------------=
----------------------------------
Micha=C5=82 =C5=81ab=C4=99dzki, Software Engineer
Tieto Corporation

Product Development Services

http://www.tieto.com / http://www.tieto.pl
---
ASCII: Michal Labedzki
location: Swobodna 1 Street, 50-088 Wroc=C5=82aw, Poland
room: 5.01 (desk next to 5.08)
---
Please note: The information contained in this message may be legally
privileged and confidential and protected from disclosure. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorised use, distribution or copying of this
communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to
the message and deleting it from your computer. Thank You.
---
Please consider the environment before printing this e-mail.
---
Tieto Poland sp=C3=B3=C5=82ka z ograniczon=C4=85 odpowiedzialno=C5=9Bci=C4=
=85 z siedzib=C4=85 w
Szczecinie, ul. Malczewskiego 26. Zarejestrowana w S=C4=85dzie Rejonowym
Szczecin-Centrum w Szczecinie, XIII Wydzia=C5=82 Gospodarczy Krajowego
Rejestru S=C4=85dowego pod numerem 0000124858. NIP: 8542085557. REGON:
812023656. Kapita=C5=82 zak=C5=82adowy: 4 271500 PLN

2013-11-08 01:43:33

[permalink] [raw]

Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus

On 11/07/2013 06:07 PM, Stevie Trujillo wrote:
> On Thu, 07 Nov 2013 11:45:53 +0800
> Hui Wang <[email protected]> wrote:
>
>> Do you know any tools can decode the log generated by usbmon?
> Hmm, I never actually used the usbmon program. I did "modprobe usbmon",
> then Wireshark shows usbmon{1..4} (one for each bus) as an interface
> like eth0 for ethernet. http://wiki.wireshark.org/CaptureSetup/USB
>
> If it's difficult to compare two captures in Wireshark (I don't know any
> other method than visual inspection), tshark (Wireshark's "command-line
> counter-part") is able to decode to stdout. Maybe one can run the diff
> program on that. The output seems a bit terse however.
>
> Please be aware: in my Wireshark (1.10.2) one of the of the SCO setup
> packets are decoded slightly wrong. It looks like Wireshark is missing
> a BDADDR in the beginning, so all the other fields get shifted.
>
>
Thanks for sharing this knowledge, i will have a try according to your
instructions.

Regards,
Hui.

2013-11-07 10:07:19

[permalink] [raw]

Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus

On Thu, 07 Nov 2013 11:45:53 +0800
Hui Wang <[email protected]> wrote:

> Do you know any tools can decode the log generated by usbmon?

Hmm, I never actually used the usbmon program. I did "modprobe usbmon",
then Wireshark shows usbmon{1..4} (one for each bus) as an interface
like eth0 for ethernet. http://wiki.wireshark.org/CaptureSetup/USB

If it's difficult to compare two captures in Wireshark (I don't know any
other method than visual inspection), tshark (Wireshark's "command-line
counter-part") is able to decode to stdout. Maybe one can run the diff
program on that. The output seems a bit terse however.

Please be aware: in my Wireshark (1.10.2) one of the of the SCO setup
packets are decoded slightly wrong. It looks like Wireshark is missing
a BDADDR in the beginning, so all the other fields get shifted.

2013-11-07 03:45:53

[permalink] [raw]

Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus

On 11/06/2013 02:44 AM, Stevie Trujillo wrote:
> On Tue, 05 Nov 2013 10:32:05 +0800
> Hui Wang <[email protected]> wrote:
>
>> Thanks for your input, I don't know the answer of your question, but
>> at least the camera works well on the EHCI bus, and camera transfers
>> the ISO packets over EHCI bus.
> Hello again! Have you tried comparing usbmon output (I used Wireshark)
> when running on EHCI and XHCI? My bluetooth card is inside the
> computer, so I'm only able to do EHCI.
>
> I see 1 ISO come in right after the SCO thing opens. It has some
> error stuff inside (ENOSPC). No idea how it is supposed to behave,
> since I can't compare with a good one.
>
> Sorry if this is a stupid idea :P
>
Do you know any tools can decode the log generated by usbmon?

Regards,
Hui.

2013-11-05 18:44:31

[permalink] [raw]

Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus

On Tue, 05 Nov 2013 10:32:05 +0800
Hui Wang <[email protected]> wrote:

> Thanks for your input, I don't know the answer of your question, but
> at least the camera works well on the EHCI bus, and camera transfers
> the ISO packets over EHCI bus.

Hello again! Have you tried comparing usbmon output (I used Wireshark)
when running on EHCI and XHCI? My bluetooth card is inside the
computer, so I'm only able to do EHCI.

I see 1 ISO come in right after the SCO thing opens. It has some
error stuff inside (ENOSPC). No idea how it is supposed to behave,
since I can't compare with a good one.

Sorry if this is a stupid idea :P

2013-11-05 02:32:05

[permalink] [raw]

Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus

On 11/04/2013 09:15 PM, Stevie Trujillo wrote:
> Hello, I've been trying to use my computer as "handsfree" with
> "Hands-Free Profile" using "Intel Corporation Centrino Wireless-N
> 1030". I accept() the BTPROTO_SCO socket, but never recv() any
> data. Your post looked similar!
>
> When googling I found this:
>
> http://www.netbsd.org/docs/guide/en/chap-bluetooth.html#chap-bluetooth-audio
> SCO Audio will not work with ehci(4) USB controllers, since support
> for Isochronous data over EHCI is missing in NetBSD.
>
> Does Linux support this? (I have no idea what it means)

Hi Stevie,

Thanks for your input, I don't know the answer of your question, but at
least the camera works well on the EHCI bus, and camera transfers the
ISO packets over EHCI bus.

Regards,
Hui.
>
> I'm sorry if this mail is somewhat broken. I could only find your email
> on "gmane" and it had encrypted all your email addresses!
>
> On Mon, 04 Nov 2013 13:59:35 +0800
> Hui Wang <[email protected]> wrote:
>
>> On 11/03/2013 03:05 AM, Marcel Holtmann wrote:
>>> Hi Hui,
>>>
>> <snip>
>>>> The attachment lenovo-k4450-btmon-v1.log is the log of intel 7260
>>>> init procedure + scan headset + connect headset + play sound.
>>> I looked through the logs and the controller init is just fine. So
>>> in theory this should route the SCO audio frames over HCI. For some
>>> reason it does not and I have no idea why not.
>>>
>>> That it makes a different between EHCI and XHCI is strange. I can
>>> not explain this. Maybe Tedd can help you since I have no further
>>> insights in our chips at this moment.
>> Thanks Marcel for your kind help and analysis.
>>
>> Tedd, did you reproduce this issue on the machines with intel 7260 BT
>> module connected to the EHCI bus? Did you have any idea on this issue?
>

2013-11-04 13:15:39

[permalink] [raw]

Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus

Hello, I've been trying to use my computer as "handsfree" with
"Hands-Free Profile" using "Intel Corporation Centrino Wireless-N
1030". I accept() the BTPROTO_SCO socket, but never recv() any
data. Your post looked similar!

When googling I found this:

http://www.netbsd.org/docs/guide/en/chap-bluetooth.html#chap-bluetooth-audio
SCO Audio will not work with ehci(4) USB controllers, since support
for Isochronous data over EHCI is missing in NetBSD.

Does Linux support this? (I have no idea what it means)

I'm sorry if this mail is somewhat broken. I could only find your email
on "gmane" and it had encrypted all your email addresses!

On Mon, 04 Nov 2013 13:59:35 +0800
Hui Wang <[email protected]> wrote:

> On 11/03/2013 03:05 AM, Marcel Holtmann wrote:
> > Hi Hui,
> >
> <snip>
> >>
> >> The attachment lenovo-k4450-btmon-v1.log is the log of intel 7260
> >> init procedure + scan headset + connect headset + play sound.
> > I looked through the logs and the controller init is just fine. So
> > in theory this should route the SCO audio frames over HCI. For some
> > reason it does not and I have no idea why not.
> >
> > That it makes a different between EHCI and XHCI is strange. I can
> > not explain this. Maybe Tedd can help you since I have no further
> > insights in our chips at this moment.
>
> Thanks Marcel for your kind help and analysis.
>
> Tedd, did you reproduce this issue on the machines with intel 7260 BT
> module connected to the EHCI bus? Did you have any idea on this issue?

2013-11-04 05:59:35

[permalink] [raw]

Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus

On 11/03/2013 03:05 AM, Marcel Holtmann wrote:
> Hi Hui,
>
<snip>
>>
>> The attachment lenovo-k4450-btmon-v1.log is the log of intel 7260 init procedure + scan headset + connect headset + play sound.
> I looked through the logs and the controller init is just fine. So in theory this should route the SCO audio frames over HCI. For some reason it does not and I have no idea why not.
>
> That it makes a different between EHCI and XHCI is strange. I can not explain this. Maybe Tedd can help you since I have no further insights in our chips at this moment.

Thanks Marcel for your kind help and analysis.

Tedd, did you reproduce this issue on the machines with intel 7260 BT
module connected to the EHCI bus? Did you have any idea on this issue?

Thanks,
Hui.

>
> Regards
>
> Marcel
>
>

2013-11-02 19:05:58

[permalink] [raw]

Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus

Hi Hui,

>>>>>>>>> The problem is:
>>>>>>>>> On the machine which has Intel 7260 BT module, i use it to connect a bluetooth headset,
>>>>>>>>> it can successfully scan and connect to the headset, when i play sound to the bt headset,
>>>>>>>>> the problem comes, if the bt module is connected to the XHCI, it can work very well.
>>>>>>>>>
>>>>>>>>> u@u-Lenovo-B4400:~$ lsusb -t
>>>>>>>>> 1-7:1.0: No such file or directory
>>>>>>>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>>>>>>>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>>>>>>>>> |__ Port 6: Dev 8, If 0, Class=HID, Driver=usbhid, 1.5M
>>>>>>>>> |__ Port 7: Dev 2, If 0, Class=vend., Driver=, 12M
>>>>>>>>> |__ Port 11: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>>>>>> |__ Port 11: Dev 3, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>>>>>>
>>>>>>>>> But if the bt module is connected to the EHCI, it always fails to play sound.
>>>>>>>>>
>>>>>>>>> u@u-Lenovo-B4400:~$ lsusb -t
>>>>>>>>> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>>>>>>>>> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>>>>>>>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
>>>>>>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
>>>>>>>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
>>>>>>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
>>>>>>>>> |__ Port 5: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>>>>>> |__ Port 5: Dev 3, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>>>>>> |__ Port 6: Dev 4, If 0, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
>>>>>>>>> |__ Port 6: Dev 4, If 1, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
>>>>>>>> can you paste /sys/kernel/debug/usb/devices here.
>>>>>>>>
>>>>>>>> If the uvcvideo driver is also using ISOC URBs, we might have just exhausted the bandwidth of the USB bus here or these two devices just do not play nice with each other.
>>>>>>>>
>>>>>>>> Try to unload the uvcvideo driver and try it again.
>>>>>>> Thanks for your reply, follow your instruction, i totally disabled the camera from the BIOS, then the usb tree like this,
>>>>>>> u@u-Lenovo-B4400:~$ lsusb -t
>>>>>>> 1-1.3:1.0: No such file or directory
>>>>>>> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>>>>>>> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>>>>>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
>>>>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
>>>>>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
>>>>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
>>>>>>> |__ Port 2: Dev 3, If 0, Class=HID, Driver=usbhid, 1.5M
>>>>>>> |__ Port 3: Dev 4, If 0, Class=vend., Driver=, 12M
>>>>>>> |__ Port 5: Dev 5, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>>>> |__ Port 5: Dev 5, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>>>> u@u-Lenovo-B4400:~$ uname -a
>>>>>>> Linux u-Lenovo-B4400 3.12.0-031200rc6-generic #201310191635 SMP Sat Oct 19 20:36:43 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>>>>>>>
>>>>>>> I re-did the test, the result is same as before, after the headset is connected and i play audio, no sound is heard from the headset.
>>>>>>> And hciconfig output shows still no SCO packets received by BT driver.
>>>>>>> u@u-Lenovo-B4400:~$ hciconfig
>>>>>>> hci0: Type: BR/EDR Bus: USB
>>>>>>> BD Address: 00:15:00:CC:2D:D2 ACL MTU: 1021:5 SCO MTU: 96:5
>>>>>>> UP RUNNING PSCAN
>>>>>>> RX bytes:5853 acl:61 sco:0 events:298 errors:0
>>>>>>> TX bytes:19212 acl:68 sco:1 commands:179 errors:0
>>>>>> this is strange. The only reason I can think of is that you do not have the firmware installed and or it is not loaded correctly. Does dmesg give any indication that something failed here.
>>>>> I can confirm the firmware file is the /lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq, and it is in the filesystem. And from the dmesg, the firmware was successfully loaded.
>>>>>
>>>>> [ 8.600217] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
>>>>> [ 8.653635] kvm: disabled by bios
>>>>> [ 8.672981] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xd00123/0x840300/0x126c00
>>>>> [ 8.707034] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input13
>>>>> [ 8.717725] Registered led device: phy0-led
>>>>> [ 8.722730] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
>>>>> [ 8.752626] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
>>>>>
>>>>>> Since this is a 3.12 kernel it should have native support for Intel specific setup routing. Any chance you can run btmon -w <file> before plugging the device into the bus. Maybe something goes wrong with the setup routine on EHCI.
>>>>> Do you mean the hcidump file i just sent in my previous email.
>>>> I do not get this. I specifically asked to run ?btmon -w <file>? before plugging in the device. I want to see the early setup process here. What would I do with a hcidump trace.
>>> The attachment is the logfile generated by "btmon -w <file>". And the logfile was generated by below steps,
>>>
>>> 1) boot up the system into the ubuntu desktop
>>> 2) open a terminal and run "sudo btmon -w ~/lenovo-m4400s-btmon.log"
>>> 3) open bluetooth applet and click adding a new device, the bluetooth begin to scan devices
>>> 4) power up the bt headset
>>> 5) laptop bt module find the headset and connect it successfully
>>> 6) open the sound applet, choose bt headset as output device, play sound, but no sound can be heard from bt headset
>>> 7) Ctrl+C to terminate the "btmon -w <file>"
>>>
>>> In case you can't receive the attachment, i decode the logfile and paste the content here.
>> what I need is to see the 7260 controller init. So you need to start btmon -w <file> before the 7260 gets attached to the USB bus or before btusb.ko driver gets loaded.
> Understand now.
>
> The attachment lenovo-k4450-btmon-v0.log is the log of intel 7260 init procedure, generated by "btmon -w <file>; insmod btusb.ko; ctrl+c terminate the btmon".
>
> The attachment lenovo-k4450-btmon-v1.log is the log of intel 7260 init procedure + scan headset + connect headset + play sound.

I looked through the logs and the controller init is just fine. So in theory this should route the SCO audio frames over HCI. For some reason it does not and I have no idea why not.

That it makes a different between EHCI and XHCI is strange. I can not explain this. Maybe Tedd can help you since I have no further insights in our chips at this moment.

Regards

Marcel

2013-11-01 09:18:12

[permalink] [raw]

Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus

On 11/01/2013 03:49 PM, Marcel Holtmann wrote:
> Hi Hui,
>
>>>>>>>> The problem is:
>>>>>>>> On the machine which has Intel 7260 BT module, i use it to connect a bluetooth headset,
>>>>>>>> it can successfully scan and connect to the headset, when i play sound to the bt headset,
>>>>>>>> the problem comes, if the bt module is connected to the XHCI, it can work very well.
>>>>>>>>
>>>>>>>> u@u-Lenovo-B4400:~$ lsusb -t
>>>>>>>> 1-7:1.0: No such file or directory
>>>>>>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>>>>>>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>>>>>>>> |__ Port 6: Dev 8, If 0, Class=HID, Driver=usbhid, 1.5M
>>>>>>>> |__ Port 7: Dev 2, If 0, Class=vend., Driver=, 12M
>>>>>>>> |__ Port 11: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>>>>> |__ Port 11: Dev 3, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>>>>>
>>>>>>>> But if the bt module is connected to the EHCI, it always fails to play sound.
>>>>>>>>
>>>>>>>> u@u-Lenovo-B4400:~$ lsusb -t
>>>>>>>> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>>>>>>>> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>>>>>>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
>>>>>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
>>>>>>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
>>>>>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
>>>>>>>> |__ Port 5: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>>>>> |__ Port 5: Dev 3, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>>>>> |__ Port 6: Dev 4, If 0, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
>>>>>>>> |__ Port 6: Dev 4, If 1, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
>>>>>>> can you paste /sys/kernel/debug/usb/devices here.
>>>>>>>
>>>>>>> If the uvcvideo driver is also using ISOC URBs, we might have just exhausted the bandwidth of the USB bus here or these two devices just do not play nice with each other.
>>>>>>>
>>>>>>> Try to unload the uvcvideo driver and try it again.
>>>>>> Thanks for your reply, follow your instruction, i totally disabled the camera from the BIOS, then the usb tree like this,
>>>>>> u@u-Lenovo-B4400:~$ lsusb -t
>>>>>> 1-1.3:1.0: No such file or directory
>>>>>> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>>>>>> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>>>>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
>>>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
>>>>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
>>>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
>>>>>> |__ Port 2: Dev 3, If 0, Class=HID, Driver=usbhid, 1.5M
>>>>>> |__ Port 3: Dev 4, If 0, Class=vend., Driver=, 12M
>>>>>> |__ Port 5: Dev 5, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>>> |__ Port 5: Dev 5, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>>> u@u-Lenovo-B4400:~$ uname -a
>>>>>> Linux u-Lenovo-B4400 3.12.0-031200rc6-generic #201310191635 SMP Sat Oct 19 20:36:43 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>>>>>>
>>>>>> I re-did the test, the result is same as before, after the headset is connected and i play audio, no sound is heard from the headset.
>>>>>> And hciconfig output shows still no SCO packets received by BT driver.
>>>>>> u@u-Lenovo-B4400:~$ hciconfig
>>>>>> hci0: Type: BR/EDR Bus: USB
>>>>>> BD Address: 00:15:00:CC:2D:D2 ACL MTU: 1021:5 SCO MTU: 96:5
>>>>>> UP RUNNING PSCAN
>>>>>> RX bytes:5853 acl:61 sco:0 events:298 errors:0
>>>>>> TX bytes:19212 acl:68 sco:1 commands:179 errors:0
>>>>> this is strange. The only reason I can think of is that you do not have the firmware installed and or it is not loaded correctly. Does dmesg give any indication that something failed here.
>>>> I can confirm the firmware file is the /lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq, and it is in the filesystem. And from the dmesg, the firmware was successfully loaded.
>>>>
>>>> [ 8.600217] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
>>>> [ 8.653635] kvm: disabled by bios
>>>> [ 8.672981] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xd00123/0x840300/0x126c00
>>>> [ 8.707034] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input13
>>>> [ 8.717725] Registered led device: phy0-led
>>>> [ 8.722730] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
>>>> [ 8.752626] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
>>>>
>>>>> Since this is a 3.12 kernel it should have native support for Intel specific setup routing. Any chance you can run btmon -w <file> before plugging the device into the bus. Maybe something goes wrong with the setup routine on EHCI.
>>>> Do you mean the hcidump file i just sent in my previous email.
>>> I do not get this. I specifically asked to run ?btmon -w <file>? before plugging in the device. I want to see the early setup process here. What would I do with a hcidump trace.
>> The attachment is the logfile generated by "btmon -w <file>". And the logfile was generated by below steps,
>>
>> 1) boot up the system into the ubuntu desktop
>> 2) open a terminal and run "sudo btmon -w ~/lenovo-m4400s-btmon.log"
>> 3) open bluetooth applet and click adding a new device, the bluetooth begin to scan devices
>> 4) power up the bt headset
>> 5) laptop bt module find the headset and connect it successfully
>> 6) open the sound applet, choose bt headset as output device, play sound, but no sound can be heard from bt headset
>> 7) Ctrl+C to terminate the "btmon -w <file>"
>>
>> In case you can't receive the attachment, i decode the logfile and paste the content here.
> what I need is to see the 7260 controller init. So you need to start btmon -w <file> before the 7260 gets attached to the USB bus or before btusb.ko driver gets loaded.
Understand now.

The attachment lenovo-k4450-btmon-v0.log is the log of intel 7260 init
procedure, generated by "btmon -w <file>; insmod btusb.ko; ctrl+c
terminate the btmon".

The attachment lenovo-k4450-btmon-v1.log is the log of intel 7260 init
procedure + scan headset + connect headset + play sound.

If anything is wrong, please let me know.

Thanks,
Hui.

> Regards
>
> Marcel
>
>
>

Attachments:

lenovo-k4450-btmon-v0.log (23.45 kB)
lenovo-k4450-btmon-v1.log (34.07 kB)
Download all attachments

2013-11-01 07:49:34

[permalink] [raw]

Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus

Hi Hui,

>>>>>>> The problem is:
>>>>>>> On the machine which has Intel 7260 BT module, i use it to connect a bluetooth headset,
>>>>>>> it can successfully scan and connect to the headset, when i play sound to the bt headset,
>>>>>>> the problem comes, if the bt module is connected to the XHCI, it can work very well.
>>>>>>>
>>>>>>> u@u-Lenovo-B4400:~$ lsusb -t
>>>>>>> 1-7:1.0: No such file or directory
>>>>>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>>>>>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>>>>>>> |__ Port 6: Dev 8, If 0, Class=HID, Driver=usbhid, 1.5M
>>>>>>> |__ Port 7: Dev 2, If 0, Class=vend., Driver=, 12M
>>>>>>> |__ Port 11: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>>>> |__ Port 11: Dev 3, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>>>>
>>>>>>> But if the bt module is connected to the EHCI, it always fails to play sound.
>>>>>>>
>>>>>>> u@u-Lenovo-B4400:~$ lsusb -t
>>>>>>> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>>>>>>> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>>>>>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
>>>>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
>>>>>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
>>>>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
>>>>>>> |__ Port 5: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>>>> |__ Port 5: Dev 3, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>>>> |__ Port 6: Dev 4, If 0, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
>>>>>>> |__ Port 6: Dev 4, If 1, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
>>>>>> can you paste /sys/kernel/debug/usb/devices here.
>>>>>>
>>>>>> If the uvcvideo driver is also using ISOC URBs, we might have just exhausted the bandwidth of the USB bus here or these two devices just do not play nice with each other.
>>>>>>
>>>>>> Try to unload the uvcvideo driver and try it again.
>>>>> Thanks for your reply, follow your instruction, i totally disabled the camera from the BIOS, then the usb tree like this,
>>>>> u@u-Lenovo-B4400:~$ lsusb -t
>>>>> 1-1.3:1.0: No such file or directory
>>>>> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>>>>> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>>>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
>>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
>>>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
>>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
>>>>> |__ Port 2: Dev 3, If 0, Class=HID, Driver=usbhid, 1.5M
>>>>> |__ Port 3: Dev 4, If 0, Class=vend., Driver=, 12M
>>>>> |__ Port 5: Dev 5, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>> |__ Port 5: Dev 5, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>> u@u-Lenovo-B4400:~$ uname -a
>>>>> Linux u-Lenovo-B4400 3.12.0-031200rc6-generic #201310191635 SMP Sat Oct 19 20:36:43 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>>>>>
>>>>> I re-did the test, the result is same as before, after the headset is connected and i play audio, no sound is heard from the headset.
>>>>> And hciconfig output shows still no SCO packets received by BT driver.
>>>>> u@u-Lenovo-B4400:~$ hciconfig
>>>>> hci0: Type: BR/EDR Bus: USB
>>>>> BD Address: 00:15:00:CC:2D:D2 ACL MTU: 1021:5 SCO MTU: 96:5
>>>>> UP RUNNING PSCAN
>>>>> RX bytes:5853 acl:61 sco:0 events:298 errors:0
>>>>> TX bytes:19212 acl:68 sco:1 commands:179 errors:0
>>>> this is strange. The only reason I can think of is that you do not have the firmware installed and or it is not loaded correctly. Does dmesg give any indication that something failed here.
>>> I can confirm the firmware file is the /lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq, and it is in the filesystem. And from the dmesg, the firmware was successfully loaded.
>>>
>>> [ 8.600217] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
>>> [ 8.653635] kvm: disabled by bios
>>> [ 8.672981] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xd00123/0x840300/0x126c00
>>> [ 8.707034] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input13
>>> [ 8.717725] Registered led device: phy0-led
>>> [ 8.722730] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
>>> [ 8.752626] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
>>>
>>>> Since this is a 3.12 kernel it should have native support for Intel specific setup routing. Any chance you can run btmon -w <file> before plugging the device into the bus. Maybe something goes wrong with the setup routine on EHCI.
>>> Do you mean the hcidump file i just sent in my previous email.
>> I do not get this. I specifically asked to run ?btmon -w <file>? before plugging in the device. I want to see the early setup process here. What would I do with a hcidump trace.
>
> The attachment is the logfile generated by "btmon -w <file>". And the logfile was generated by below steps,
>
> 1) boot up the system into the ubuntu desktop
> 2) open a terminal and run "sudo btmon -w ~/lenovo-m4400s-btmon.log"
> 3) open bluetooth applet and click adding a new device, the bluetooth begin to scan devices
> 4) power up the bt headset
> 5) laptop bt module find the headset and connect it successfully
> 6) open the sound applet, choose bt headset as output device, play sound, but no sound can be heard from bt headset
> 7) Ctrl+C to terminate the "btmon -w <file>"
>
> In case you can't receive the attachment, i decode the logfile and paste the content here.

what I need is to see the 7260 controller init. So you need to start btmon -w <file> before the 7260 gets attached to the USB bus or before btusb.ko driver gets loaded.

Regards

Marcel

2013-11-01 02:39:58

[permalink] [raw]

Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus

On 10/31/2013 05:49 PM, Marcel Holtmann wrote:
> Hi Hui,
>
>>>>>> The problem is:
>>>>>> On the machine which has Intel 7260 BT module, i use it to connect a bluetooth headset,
>>>>>> it can successfully scan and connect to the headset, when i play sound to the bt headset,
>>>>>> the problem comes, if the bt module is connected to the XHCI, it can work very well.
>>>>>>
>>>>>> u@u-Lenovo-B4400:~$ lsusb -t
>>>>>> 1-7:1.0: No such file or directory
>>>>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>>>>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>>>>>> |__ Port 6: Dev 8, If 0, Class=HID, Driver=usbhid, 1.5M
>>>>>> |__ Port 7: Dev 2, If 0, Class=vend., Driver=, 12M
>>>>>> |__ Port 11: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>>> |__ Port 11: Dev 3, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>>>
>>>>>> But if the bt module is connected to the EHCI, it always fails to play sound.
>>>>>>
>>>>>> u@u-Lenovo-B4400:~$ lsusb -t
>>>>>> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>>>>>> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>>>>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
>>>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
>>>>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
>>>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
>>>>>> |__ Port 5: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>>> |__ Port 5: Dev 3, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>>>> |__ Port 6: Dev 4, If 0, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
>>>>>> |__ Port 6: Dev 4, If 1, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
>>>>> can you paste /sys/kernel/debug/usb/devices here.
>>>>>
>>>>> If the uvcvideo driver is also using ISOC URBs, we might have just exhausted the bandwidth of the USB bus here or these two devices just do not play nice with each other.
>>>>>
>>>>> Try to unload the uvcvideo driver and try it again.
>>>> Thanks for your reply, follow your instruction, i totally disabled the camera from the BIOS, then the usb tree like this,
>>>> u@u-Lenovo-B4400:~$ lsusb -t
>>>> 1-1.3:1.0: No such file or directory
>>>> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>>>> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
>>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
>>>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
>>>> |__ Port 2: Dev 3, If 0, Class=HID, Driver=usbhid, 1.5M
>>>> |__ Port 3: Dev 4, If 0, Class=vend., Driver=, 12M
>>>> |__ Port 5: Dev 5, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>> |__ Port 5: Dev 5, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
>>>> u@u-Lenovo-B4400:~$ uname -a
>>>> Linux u-Lenovo-B4400 3.12.0-031200rc6-generic #201310191635 SMP Sat Oct 19 20:36:43 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>>>>
>>>> I re-did the test, the result is same as before, after the headset is connected and i play audio, no sound is heard from the headset.
>>>> And hciconfig output shows still no SCO packets received by BT driver.
>>>> u@u-Lenovo-B4400:~$ hciconfig
>>>> hci0: Type: BR/EDR Bus: USB
>>>> BD Address: 00:15:00:CC:2D:D2 ACL MTU: 1021:5 SCO MTU: 96:5
>>>> UP RUNNING PSCAN
>>>> RX bytes:5853 acl:61 sco:0 events:298 errors:0
>>>> TX bytes:19212 acl:68 sco:1 commands:179 errors:0
>>> this is strange. The only reason I can think of is that you do not have the firmware installed and or it is not loaded correctly. Does dmesg give any indication that something failed here.
>> I can confirm the firmware file is the /lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq, and it is in the filesystem. And from the dmesg, the firmware was successfully loaded.
>>
>> [ 8.600217] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
>> [ 8.653635] kvm: disabled by bios
>> [ 8.672981] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xd00123/0x840300/0x126c00
>> [ 8.707034] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input13
>> [ 8.717725] Registered led device: phy0-led
>> [ 8.722730] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
>> [ 8.752626] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
>>
>>> Since this is a 3.12 kernel it should have native support for Intel specific setup routing. Any chance you can run btmon -w <file> before plugging the device into the bus. Maybe something goes wrong with the setup routine on EHCI.
>> Do you mean the hcidump file i just sent in my previous email.
> I do not get this. I specifically asked to run ?btmon -w <file>? before plugging in the device. I want to see the early setup process here. What would I do with a hcidump trace.
Hi Marcel,

The attachment is the logfile generated by "btmon -w <file>". And the
logfile was generated by below steps,

1) boot up the system into the ubuntu desktop
2) open a terminal and run "sudo btmon -w ~/lenovo-m4400s-btmon.log"
3) open bluetooth applet and click adding a new device, the bluetooth
begin to scan devices
4) power up the bt headset
5) laptop bt module find the headset and connect it successfully
6) open the sound applet, choose bt headset as output device, play
sound, but no sound can be heard from bt headset
7) Ctrl+C to terminate the "btmon -w <file>"

In case you can't receive the attachment, i decode the logfile and paste
the content here.

Thanks,
Hui.

=================================================================================================
Bluetooth monitor ver 5.9
= New Index (BR/EDR,USB,hci0) [hci0] 0.218046
> HCI Event (0x04) plen 10 [hci0] 2.886816
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
Class: 0x240404
Major class: Audio/Video (headset, speaker, stereo, video, vcr)
Minor class: 0x01
Rendering (Printing, Speaker)
Audio (Speaker, Microphone, Headset)
Link type: ACL (0x01)
< HCI Command (0x01|0x0009) plen 7 [hci0] 2.887014
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
Role: Master (0x00)
> HCI Event (0x0f) plen 4 [hci0] 2.887807
Accept Connection Request (0x01|0x0009) ncmd 1
Status: Success (0x00)
> HCI Event (0x12) plen 8 [hci0] 3.028749
Status: Success (0x00)
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
Role: Master (0x00)
> HCI Event (0x03) plen 11 [hci0] 3.034733
Status: Success (0x00)
Handle: 256
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command (0x01|0x001b) plen 2 [hci0] 3.034808
Handle: 256
> HCI Event (0x0f) plen 4 [hci0] 3.035730
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
> HCI Event (0x1b) plen 3 [hci0] 3.041745
Handle: 256
Max slots: 5
> HCI Event (0x0b) plen 11 [hci0] 3.043740
Status: Success (0x00)
Handle: 256
Features: 0xbf 0xfe 0x8f 0xfe 0x9b 0xff 0x79 0x87
3 slot packets
5 slot packets
Encryption
Slot offset
Timing accuracy
Role switch
Sniff mode
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
Erroneous Data Reporting
Non-flushable Packet Boundary Flag
Link Supervision Timeout Changed Event
Inquiry TX Power Level
Enhanced Power Control
Extended features
< HCI Command (0x01|0x001c) plen 3 [hci0] 3.043755
Handle: 256
Page: 1
> ACL Data RX flags 0x02 dlen 12 [hci0] 3.045734
L2CAP: Connection Request (0x02) ident 2 len 4
PSM: 1 (0x0001)
Source CID: 65
> HCI Event (0x0f) plen 4 [hci0] 3.045738
Read Remote Extended Features (0x01|0x001c) ncmd 1
Status: Success (0x00)
< ACL Data TX flags 0x00 dlen 16 [hci0] 3.045762
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 flags 0x00 dlen 10 [hci0] 3.045767
L2CAP: Information Request (0x0a) ident 1 len 2
Type: Extended features supported (0x0002)
> HCI Event (0x23) plen 13 [hci0] 3.049734
Status: Success (0x00)
Handle: 256
Page: 1/0
Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Secure Simple Pairing (Host Support)
< HCI Command (0x01|0x0019) plen 10 [hci0] 3.049745
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x0000
> HCI Event (0x0f) plen 4 [hci0] 3.050721
Remote Name Request (0x01|0x0019) ncmd 1
Status: Success (0x00)
> HCI Event (0x13) plen 5 [hci0] 3.051735
Num handles: 1
Handle: 256
Count: 1
> HCI Event (0x13) plen 5 [hci0] 3.056726
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 16 [hci0] 3.056969
L2CAP: Information Response (0x0b) ident 1 len 8
Type: Extended features supported (0x0002)
Result: Success (0x0000)
Features: 0x00000200
Unicast Connectionless Data Reception
< ACL Data TX flags 0x00 dlen 10 [hci0] 3.056995
L2CAP: Command Reject (0x01) ident 1 len 2
Reason: Command not understood (0x0000)
> HCI Event (0x13) plen 5 [hci0] 3.061726
Num handles: 1
Handle: 256
Count: 1
> HCI Event (0x07) plen 255 [hci0] 3.070718
Status: Success (0x00)
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
Name: HM1700
< ACL Data TX flags 0x00 dlen 16 [hci0] 7.047684
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 flags 0x00 dlen 12 [hci0] 7.047708
L2CAP: Configure Request (0x04) ident 2 len 4
Destination CID: 65
Flags: 0x0000
> HCI Event (0x13) plen 5 [hci0] 7.051758
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 16 [hci0] 7.052502
L2CAP: Configure Request (0x04) ident 3 len 8
Destination CID: 64
Flags: 0x0000
Option: Maximum Transmission Unit (0x01)
MTU: 64
< ACL Data TX flags 0x00 dlen 18 [hci0] 7.052550
L2CAP: Configure Response (0x05) ident 3 len 10
Source CID: 65
Flags: 0x0000
Result: Success (0x0000)
Option: Maximum Transmission Unit (0x01)
MTU: 64
> HCI Event (0x13) plen 5 [hci0] 7.052733
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 14 [hci0] 7.053751
L2CAP: Configure Response (0x05) ident 2 len 6
Source CID: 64
Flags: 0x0000
Result: Success (0x0000)
> HCI Event (0x13) plen 5 [hci0] 7.056754
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 31 [hci0] 7.057249
Channel: 64 len 27 [PSM 1 mode 0] {chan 0}
SDP: Service Search Attribute Request (0x06) tid 0 len 22
Search pattern: [len 5]
Sequence (6) with 3 bytes [8 extra bits] len 5
UUID (3) with 2 bytes [0 extra bits] len 3
Handsfree Audio Gateway (0x111f)
Max record count: 48
Attribute list: [len 14]
Sequence (6) with 12 bytes [8 extra bits] len 14
Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
0x0001
Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
0x0004
Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
0x0009
Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
0x0311
Continuation state: 0
< ACL Data TX flags 0x00 dlen 68 [hci0] 7.057567
Channel: 65 len 64 [PSM 1 mode 0] {chan 0}
SDP: Service Search Attribute Response (0x07) tid 0 len 59
Attribute bytes: 48
Continuation state: 8
5b 10 73 52 30 00 00 00 [.sR0...
> ACL Data RX flags 0x02 dlen 39 [hci0] 7.063746
Channel: 64 len 35 [PSM 1 mode 0] {chan 0}
SDP: Service Search Attribute Request (0x06) tid 1 len 30
Search pattern: [len 5]
Sequence (6) with 3 bytes [8 extra bits] len 5
UUID (3) with 2 bytes [0 extra bits] len 3
Handsfree Audio Gateway (0x111f)
Max record count: 48
Attribute list: [len 14]
Sequence (6) with 12 bytes [8 extra bits] len 14
Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
0x0001
Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
0x0004
Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
0x0009
Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
0x0311
Continuation state: 8
5b 10 73 52 30 00 00 00 [.sR0...
< ACL Data TX flags 0x00 dlen 15 [hci0] 7.063938
Channel: 65 len 11 [PSM 1 mode 0] {chan 0}
SDP: Service Search Attribute Response (0x07) tid 1 len 6
Attribute bytes: 3
Continuation state: 0
Combined attribute bytes: 51
Attribute list: [len 47] {position 0}
Attribute: Service Class ID List (0x0001) [len 2]
UUID (3) with 2 bytes [0 extra bits] len 3
Handsfree Audio Gateway (0x111f)
UUID (3) with 2 bytes [0 extra bits] len 3
Generic Audio (0x1203)
Attribute: Protocol Descriptor List (0x0004) [len 2]
Sequence (6) with 3 bytes [8 extra bits] len 5
UUID (3) with 2 bytes [0 extra bits] len 3
L2CAP (0x0100)
Sequence (6) with 5 bytes [8 extra bits] len 7
UUID (3) with 2 bytes [0 extra bits] len 3
RFCOMM (0x0003)
Unsigned Integer (1) with 1 byte [0 extra bits] len 2
0x0d
Attribute: Bluetooth Profile Descriptor List (0x0009) [len 2]
Sequence (6) with 6 bytes [8 extra bits] len 8
UUID (3) with 2 bytes [0 extra bits] len 3
Handsfree (0x111e)
Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
0x0105
Attribute: Unknown (0x0311) [len 2]
0x0000
> HCI Event (0x13) plen 5 [hci0] 7.064747
Num handles: 1
Handle: 256
Count: 1
> HCI Event (0x13) plen 5 [hci0] 7.067749
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 12 [hci0] 7.068619
L2CAP: Disconnection Request (0x06) ident 4 len 4
Destination CID: 64
Source CID: 65
< ACL Data TX flags 0x00 dlen 12 [hci0] 7.068674
L2CAP: Disconnection Response (0x07) ident 4 len 4
Destination CID: 64
Source CID: 65
> HCI Event (0x13) plen 5 [hci0] 7.072746
Num handles: 1
Handle: 256
Count: 1
> HCI Event (0x17) plen 6 [hci0] 7.074742
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
< HCI Command (0x01|0x000c) plen 6 [hci0] 7.074922
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
> HCI Event (0x0e) plen 10 [hci0] 7.075743
Link Key Request Negative Reply (0x01|0x000c) ncmd 1
Status: Success (0x00)
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
> HCI Event (0x32) plen 9 [hci0] 7.080726
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
IO capability: NoInputNoOutput (0x03)
OOB data: Authentication data not present (0x00)
Authentication: General Bonding - MITM required (0x05)
> HCI Event (0x31) plen 6 [hci0] 7.081716
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
< HCI Command (0x01|0x002b) plen 9 [hci0] 7.081876
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
IO capability: DisplayYesNo (0x01)
OOB data: Authentication data not present (0x00)
Authentication: General Bonding - MITM required (0x05)
> HCI Event (0x0e) plen 10 [hci0] 7.082712
IO Capability Request Reply (0x01|0x002b) ncmd 1
Status: Success (0x00)
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
> HCI Event (0x33) plen 10 [hci0] 7.339625
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
Passkey: 575136
< HCI Command (0x01|0x002d) plen 6 [hci0] 7.339848
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
> HCI Event (0x0e) plen 10 [hci0] 7.340647
User Confirmation Request Neg Reply (0x01|0x002d) ncmd 1
Status: Success (0x00)
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
> HCI Event (0x36) plen 7 [hci0] 7.742431
Status: Authentication Failure (0x05)
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
> HCI Event (0x05) plen 4 [hci0] 7.897336
Status: Success (0x00)
Handle: 256
Reason: Remote User Terminated Connection (0x13)
< HCI Command (0x01|0x0001) plen 5 [hci0] 16.279595
Access code: 0x9e8b33 (General Inquiry)
Length: 10.24s (0x08)
Num responses: 0
> HCI Event (0x0f) plen 4 [hci0] 16.281119
Inquiry (0x01|0x0001) ncmd 2
Status: Success (0x00)
> HCI Event (0x2f) plen 255 [hci0] 17.025785
Num responses: 1
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
Page scan repetition mode: R1 (0x01)
Page period mode: P0 (0x00)
Class: 0x240404
Major class: Audio/Video (headset, speaker, stereo, video, vcr)
Minor class: 0x01
Rendering (Printing, Speaker)
Audio (Speaker, Microphone, Headset)
Clock offset: 0x51f1
RSSI: -44 dBm (0xd4)
Name (complete): HM1700
16-bit Service UUIDs (complete): 5 entries
Headset (0x1108)
Handsfree (0x111e)
Audio Sink (0x110b)
A/V Remote Control (0x110e)
Serial Port (0x1101)
< HCI Command (0x01|0x0002) plen 0 [hci0] 25.122354
> HCI Event (0x0e) plen 4 [hci0] 25.124712
Inquiry Cancel (0x01|0x0002) ncmd 2
Status: Success (0x00)
< HCI Command (0x01|0x0005) plen 13 [hci0] 25.127063
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
Packet type: 0xcc18
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x0000
Role switch: Allow slave (0x01)
> HCI Event (0x0f) plen 4 [hci0] 25.127693
Create Connection (0x01|0x0005) ncmd 1
Status: Success (0x00)
> HCI Event (0x03) plen 11 [hci0] 25.988303
Status: Success (0x00)
Handle: 256
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
Link type: ACL (0x01)
Encryption: Disabled (0x00)
< HCI Command (0x01|0x001b) plen 2 [hci0] 25.988535
Handle: 256
> HCI Event (0x0f) plen 4 [hci0] 25.990330
Read Remote Supported Features (0x01|0x001b) ncmd 1
Status: Success (0x00)
> HCI Event (0x1b) plen 3 [hci0] 25.993260
Handle: 256
Max slots: 5
> HCI Event (0x0b) plen 11 [hci0] 25.996270
Status: Success (0x00)
Handle: 256
Features: 0xbf 0xfe 0x8f 0xfe 0x9b 0xff 0x79 0x87
3 slot packets
5 slot packets
Encryption
Slot offset
Timing accuracy
Role switch
Sniff mode
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
Erroneous Data Reporting
Non-flushable Packet Boundary Flag
Link Supervision Timeout Changed Event
Inquiry TX Power Level
Enhanced Power Control
Extended features
< HCI Command (0x01|0x001c) plen 3 [hci0] 25.996285
Handle: 256
Page: 1
> HCI Event (0x0f) plen 4 [hci0] 25.997267
Read Remote Extended Features (0x01|0x001c) ncmd 1
Status: Success (0x00)
> HCI Event (0x23) plen 13 [hci0] 26.005271
Status: Success (0x00)
Handle: 256
Page: 1/0
Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Secure Simple Pairing (Host Support)
< HCI Command (0x01|0x0019) plen 10 [hci0] 26.005292
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
Page scan repetition mode: R2 (0x02)
Page scan mode: Mandatory (0x00)
Clock offset: 0x0000
> HCI Event (0x0f) plen 4 [hci0] 26.006256
Remote Name Request (0x01|0x0019) ncmd 1
Status: Success (0x00)
> HCI Event (0x07) plen 255 [hci0] 26.025242
Status: Success (0x00)
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
Name: HM1700
< HCI Command (0x01|0x0011) plen 2 [hci0] 26.025266
Handle: 256
> HCI Event (0x0f) plen 4 [hci0] 26.026243
Authentication Requested (0x01|0x0011) ncmd 1
Status: Success (0x00)
> HCI Event (0x17) plen 6 [hci0] 26.027313
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
< HCI Command (0x01|0x000c) plen 6 [hci0] 26.033110
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
> HCI Event (0x0e) plen 10 [hci0] 26.034256
Link Key Request Negative Reply (0x01|0x000c) ncmd 1
Status: Success (0x00)
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
> HCI Event (0x31) plen 6 [hci0] 26.035237
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
< HCI Command (0x01|0x002b) plen 9 [hci0] 26.035287
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
IO capability: DisplayYesNo (0x01)
OOB data: Authentication data not present (0x00)
Authentication: Dedicated Bonding - MITM required (0x03)
> HCI Event (0x0e) plen 10 [hci0] 26.036270
IO Capability Request Reply (0x01|0x002b) ncmd 1
Status: Success (0x00)
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
> HCI Event (0x32) plen 9 [hci0] 26.040267
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
IO capability: NoInputNoOutput (0x03)
OOB data: Authentication data not present (0x00)
Authentication: Dedicated Bonding - MITM not required (0x02)
> HCI Event (0x33) plen 10 [hci0] 26.280169
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
Passkey: 270951
< HCI Command (0x01|0x002c) plen 6 [hci0] 26.285610
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
> HCI Event (0x0e) plen 10 [hci0] 26.287160
User Confirmation Request Reply (0x01|0x002c) ncmd 1
Status: Success (0x00)
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
> HCI Event (0x36) plen 7 [hci0] 26.766879
Status: Success (0x00)
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
> HCI Event (0x18) plen 23 [hci0] 26.782938
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
Link key: de2eb68b175d2935833022b04c121ce2
Key type: Unauthenticated Combination key (0x04)
> HCI Event (0x06) plen 3 [hci0] 26.783870
Status: Success (0x00)
Handle: 256
< HCI Command (0x01|0x0013) plen 3 [hci0] 26.783942
Handle: 256
Encryption: Enabled (0x01)
> HCI Event (0x0f) plen 4 [hci0] 26.784940
Set Connection Encryption (0x01|0x0013) ncmd 1
Status: Success (0x00)
> HCI Event (0x08) plen 4 [hci0] 26.826850
Status: Success (0x00)
Handle: 256
Encryption: Enabled with E0 (0x01)
< ACL Data TX flags 0x00 dlen 10 [hci0] 26.826893
L2CAP: Information Request (0x0a) ident 1 len 2
Type: Extended features supported (0x0002)
> HCI Event (0x13) plen 5 [hci0] 26.830847
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 16 [hci0] 26.831344
L2CAP: Information Response (0x0b) ident 1 len 8
Type: Extended features supported (0x0002)
Result: Success (0x0000)
Features: 0x00000200
Unicast Connectionless Data Reception
< ACL Data TX flags 0x00 dlen 10 [hci0] 26.831381
L2CAP: Command Reject (0x01) ident 1 len 2
Reason: Command not understood (0x0000)
> HCI Event (0x13) plen 5 [hci0] 26.835845
Num handles: 1
Handle: 256
Count: 1
< ACL Data TX flags 0x00 dlen 12 [hci0] 30.831706
L2CAP: Connection Request (0x02) ident 2 len 4
PSM: 1 (0x0001)
Source CID: 64
> HCI Event (0x13) plen 5 [hci0] 30.835877
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 16 [hci0] 30.836841
L2CAP: Connection Response (0x03) ident 2 len 8
Destination CID: 67
Source CID: 64
Result: Connection successful (0x0000)
Status: No further information available (0x0000)
< ACL Data TX flags 0x00 dlen 12 [hci0] 30.836891
L2CAP: Configure Request (0x04) ident 3 len 4
Destination CID: 67
Flags: 0x0000
> ACL Data RX flags 0x02 dlen 16 [hci0] 30.838159
L2CAP: Configure Request (0x04) ident 2 len 8
Destination CID: 64
Flags: 0x0000
Option: Maximum Transmission Unit (0x01)
MTU: 64
< ACL Data TX flags 0x00 dlen 18 [hci0] 30.838224
L2CAP: Configure Response (0x05) ident 2 len 10
Source CID: 67
Flags: 0x0000
Result: Success (0x0000)
Option: Maximum Transmission Unit (0x01)
MTU: 64
> HCI Event (0x13) plen 5 [hci0] 30.840918
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 14 [hci0] 30.841845
L2CAP: Configure Response (0x05) ident 3 len 6
Source CID: 64
Flags: 0x0000
Result: Success (0x0000)
< ACL Data TX flags 0x00 dlen 24 [hci0] 30.842014
Channel: 67 len 20 [PSM 1 mode 0] {chan 0}
SDP: Service Search Attribute Request (0x06) tid 0 len 15
Search pattern: [len 5]
Sequence (6) with 3 bytes [8 extra bits] len 5
UUID (3) with 2 bytes [0 extra bits] len 3
L2CAP (0x0100)
Max record count: 65535
Attribute list: [len 7]
Sequence (6) with 5 bytes [8 extra bits] len 7
Unsigned Integer (1) with 4 bytes [0 extra bits] len 5
0x0000ffff
Continuation state: 0
> HCI Event (0x13) plen 5 [hci0] 30.842845
Num handles: 1
Handle: 256
Count: 1
> HCI Event (0x13) plen 5 [hci0] 30.845847
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 68 [hci0] 30.846904
Channel: 64 len 64 [PSM 1 mode 0] {chan 0}
SDP: Service Search Attribute Response (0x07) tid 0 len 59
Attribute bytes: 54
Continuation state: 2
00 36 .6
< ACL Data TX flags 0x00 dlen 26 [hci0] 30.847135
Channel: 67 len 22 [PSM 1 mode 0] {chan 0}
SDP: Service Search Attribute Request (0x06) tid 1 len 17
Search pattern: [len 5]
Sequence (6) with 3 bytes [8 extra bits] len 5
UUID (3) with 2 bytes [0 extra bits] len 3
L2CAP (0x0100)
Max record count: 65535
Attribute list: [len 7]
Sequence (6) with 5 bytes [8 extra bits] len 7
Unsigned Integer (1) with 4 bytes [0 extra bits] len 5
0x0000ffff
Continuation state: 2
00 36 .6
> HCI Event (0x13) plen 5 [hci0] 30.850887
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 68 [hci0] 30.851837
Channel: 64 len 64 [PSM 1 mode 0] {chan 0}
SDP: Service Search Attribute Response (0x07) tid 1 len 59
Attribute bytes: 54
Continuation state: 2
00 6c .l
< ACL Data TX flags 0x00 dlen 26 [hci0] 30.851969
Channel: 67 len 22 [PSM 1 mode 0] {chan 0}
SDP: Service Search Attribute Request (0x06) tid 2 len 17
Search pattern: [len 5]
Sequence (6) with 3 bytes [8 extra bits] len 5
UUID (3) with 2 bytes [0 extra bits] len 3
L2CAP (0x0100)
Max record count: 65535
Attribute list: [len 7]
Sequence (6) with 5 bytes [8 extra bits] len 7
Unsigned Integer (1) with 4 bytes [0 extra bits] len 5
0x0000ffff
Continuation state: 2
00 6c .l
> HCI Event (0x13) plen 5 [hci0] 30.855867
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 68 [hci0] 30.856899
Channel: 64 len 64 [PSM 1 mode 0] {chan 0}
SDP: Service Search Attribute Response (0x07) tid 2 len 59
Attribute bytes: 54
Continuation state: 2
00 a2 ..
< ACL Data TX flags 0x00 dlen 26 [hci0] 30.857114
Channel: 67 len 22 [PSM 1 mode 0] {chan 0}
SDP: Service Search Attribute Request (0x06) tid 3 len 17
Search pattern: [len 5]
Sequence (6) with 3 bytes [8 extra bits] len 5
UUID (3) with 2 bytes [0 extra bits] len 3
L2CAP (0x0100)
Max record count: 65535
Attribute list: [len 7]
Sequence (6) with 5 bytes [8 extra bits] len 7
Unsigned Integer (1) with 4 bytes [0 extra bits] len 5
0x0000ffff
Continuation state: 2
00 a2 ..
> HCI Event (0x13) plen 5 [hci0] 30.860833
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 68 [hci0] 30.861829
Channel: 64 len 64 [PSM 1 mode 0] {chan 0}
SDP: Service Search Attribute Response (0x07) tid 3 len 59
Attribute bytes: 54
Continuation state: 2
00 d8 ..
< ACL Data TX flags 0x00 dlen 26 [hci0] 30.862014
Channel: 67 len 22 [PSM 1 mode 0] {chan 0}
SDP: Service Search Attribute Request (0x06) tid 4 len 17
Search pattern: [len 5]
Sequence (6) with 3 bytes [8 extra bits] len 5
UUID (3) with 2 bytes [0 extra bits] len 3
L2CAP (0x0100)
Max record count: 65535
Attribute list: [len 7]
Sequence (6) with 5 bytes [8 extra bits] len 7
Unsigned Integer (1) with 4 bytes [0 extra bits] len 5
0x0000ffff
Continuation state: 2
00 d8 ..
> HCI Event (0x13) plen 5 [hci0] 30.865838
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 62 [hci0] 30.866859
Channel: 64 len 58 [PSM 1 mode 0] {chan 0}
SDP: Service Search Attribute Response (0x07) tid 4 len 53
Attribute bytes: 50
Continuation state: 0
Combined attribute bytes: 266
Attribute list: [len 82] {position 0}
Attribute: Service Record Handle (0x0000) [len 2]
0x00010001
Attribute: Service Class ID List (0x0001) [len 2]
UUID (3) with 2 bytes [0 extra bits] len 3
Headset (0x1108)
UUID (3) with 2 bytes [0 extra bits] len 3
Headset HS (0x1131)
UUID (3) with 2 bytes [0 extra bits] len 3
Generic Audio (0x1203)
Attribute: Protocol Descriptor List (0x0004) [len 2]
Sequence (6) with 3 bytes [8 extra bits] len 5
UUID (3) with 2 bytes [0 extra bits] len 3
L2CAP (0x0100)
Sequence (6) with 5 bytes [8 extra bits] len 7
UUID (3) with 2 bytes [0 extra bits] len 3
RFCOMM (0x0003)
Unsigned Integer (1) with 1 byte [0 extra bits] len 2
0x01
Attribute: Browse Group List (0x0005) [len 2]
UUID (3) with 2 bytes [0 extra bits] len 3
Public Browse Root (0x1002)
Attribute: Bluetooth Profile Descriptor List (0x0009) [len 2]
Sequence (6) with 6 bytes [8 extra bits] len 8
UUID (3) with 2 bytes [0 extra bits] len 3
Headset (0x1108)
Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
0x0102
Attribute: Unknown (0x0100) [len 2]
HSP service [len 12]
Attribute: Unknown (0x0302) [len 2]
true
Attribute list: [len 80] {position 1}
Attribute: Service Record Handle (0x0000) [len 2]
0x00010002
Attribute: Service Class ID List (0x0001) [len 2]
UUID (3) with 2 bytes [0 extra bits] len 3
Handsfree (0x111e)
UUID (3) with 2 bytes [0 extra bits] len 3
Generic Audio (0x1203)
Attribute: Protocol Descriptor List (0x0004) [len 2]
Sequence (6) with 3 bytes [8 extra bits] len 5
UUID (3) with 2 bytes [0 extra bits] len 3
L2CAP (0x0100)
Sequence (6) with 5 bytes [8 extra bits] len 7
UUID (3) with 2 bytes [0 extra bits] len 3
RFCOMM (0x0003)
Unsigned Integer (1) with 1 byte [0 extra bits] len 2
0x02
Attribute: Browse Group List (0x0005) [len 2]
UUID (3) with 2 bytes [0 extra bits] len 3
Public Browse Root (0x1002)
Attribute: Bluetooth Profile Descriptor List (0x0009) [len 2]
Sequence (6) with 6 bytes [8 extra bits] len 8
UUID (3) with 2 bytes [0 extra bits] len 3
Handsfree (0x111e)
Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
0x0105
Attribute: Unknown (0x0100) [len 2]
HFP service [len 12]
Attribute: Unknown (0x0311) [len 2]
0x001b
Attribute list: [len 92] {position 2}
Attribute: Service Record Handle (0x0000) [len 2]
0x00010003
Attribute: Service Class ID List (0x0001) [len 2]
UUID (3) with 2 bytes [0 extra bits] len 3
Audio Sink (0x110b)
Attribute: Protocol Descriptor List (0x0004) [len 2]
Sequence (6) with 6 bytes [8 extra bits] len 8
UUID (3) with 2 bytes [0 extra bits] len 3
L2CAP (0x0100)
Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
0x0019
Sequence (6) with 6 bytes [8 extra bits] len 8
UUID (3) with 2 bytes [0 extra bits] len 3
AVDTP (0x0019)
Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
0x0102
Attribute: Browse Group List (0x0005) [len 2]
UUID (3) with 2 bytes [0 extra bits] len 3
Public Browse Root (0x1002)
Attribute: Bluetooth Profile Descriptor List (0x0009) [len 2]
Sequence (6) with 6 bytes [8 extra bits] len 8
UUID (3) with 2 bytes [0 extra bits] len 3
Advanced Audio Distribution (0x110d)
Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
0x0102
Attribute: Unknown (0x0100) [len 2]
Advanced audio service [len 23]
Attribute: Unknown (0x0311) [len 2]
0x0001
< ACL Data TX flags 0x00 dlen 24 [hci0] 30.987030
Channel: 67 len 20 [PSM 1 mode 0] {chan 0}
SDP: Service Search Attribute Request (0x06) tid 5 len 15
Search pattern: [len 5]
Sequence (6) with 3 bytes [8 extra bits] len 5
UUID (3) with 2 bytes [0 extra bits] len 3
PnP Information (0x1200)
Max record count: 65535
Attribute list: [len 7]
Sequence (6) with 5 bytes [8 extra bits] len 7
Unsigned Integer (1) with 4 bytes [0 extra bits] len 5
0x0000ffff
Continuation state: 0
> HCI Event (0x13) plen 5 [hci0] 30.990839
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 67 [hci0] 30.991834
Channel: 64 len 63 [PSM 1 mode 0] {chan 0}
SDP: Service Search Attribute Response (0x07) tid 5 len 58
Attribute bytes: 53
Continuation state: 2
00 35 .5
< ACL Data TX flags 0x00 dlen 26 [hci0] 30.992052
Channel: 67 len 22 [PSM 1 mode 0] {chan 0}
SDP: Service Search Attribute Request (0x06) tid 6 len 17
Search pattern: [len 5]
Sequence (6) with 3 bytes [8 extra bits] len 5
UUID (3) with 2 bytes [0 extra bits] len 3
PnP Information (0x1200)
Max record count: 65535
Attribute list: [len 7]
Sequence (6) with 5 bytes [8 extra bits] len 7
Unsigned Integer (1) with 4 bytes [0 extra bits] len 5
0x0000ffff
Continuation state: 2
00 35 .5
> HCI Event (0x13) plen 5 [hci0] 30.995811
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 29 [hci0] 30.996518
Channel: 64 len 25 [PSM 1 mode 0] {chan 0}
SDP: Service Search Attribute Response (0x07) tid 6 len 20
Attribute bytes: 17
Continuation state: 0
Combined attribute bytes: 70
Attribute list: [len 65] {position 0}
Attribute: Service Record Handle (0x0000) [len 2]
0x00010000
Attribute: Service Class ID List (0x0001) [len 2]
UUID (3) with 2 bytes [0 extra bits] len 3
PnP Information (0x1200)
Attribute: Browse Group List (0x0005) [len 2]
UUID (3) with 2 bytes [0 extra bits] len 3
Public Browse Root (0x1002)
Attribute: Unknown (0x0200) [len 2]
0x0103
Attribute: Unknown (0x0201) [len 2]
0x000f
Attribute: Unknown (0x0202) [len 2]
0x0000
Attribute: Unknown (0x0203) [len 2]
0x0000
Attribute: Unknown (0x0204) [len 2]
true
Attribute: Unknown (0x0205) [len 2]
0x0001
Attribute: Unknown (0x8001) [len 2]
0x0001
< ACL Data TX flags 0x00 dlen 24 [hci0] 31.099275
Channel: 67 len 20 [PSM 1 mode 0] {chan 0}
SDP: Service Search Attribute Request (0x06) tid 7 len 15
Search pattern: [len 5]
Sequence (6) with 3 bytes [8 extra bits] len 5
UUID (3) with 2 bytes [0 extra bits] len 3
Handsfree (0x111e)
Max record count: 65535
Attribute list: [len 7]
Sequence (6) with 5 bytes [8 extra bits] len 7
Unsigned Integer (1) with 4 bytes [0 extra bits] len 5
0x0000ffff
Continuation state: 0
> HCI Event (0x13) plen 5 [hci0] 31.101722
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 67 [hci0] 31.102965
Channel: 64 len 63 [PSM 1 mode 0] {chan 0}
SDP: Service Search Attribute Response (0x07) tid 7 len 58
Attribute bytes: 53
Continuation state: 2
00 35 .5
< ACL Data TX flags 0x00 dlen 26 [hci0] 31.103181
Channel: 67 len 22 [PSM 1 mode 0] {chan 0}
SDP: Service Search Attribute Request (0x06) tid 8 len 17
Search pattern: [len 5]
Sequence (6) with 3 bytes [8 extra bits] len 5
UUID (3) with 2 bytes [0 extra bits] len 3
Handsfree (0x111e)
Max record count: 65535
Attribute list: [len 7]
Sequence (6) with 5 bytes [8 extra bits] len 7
Unsigned Integer (1) with 4 bytes [0 extra bits] len 5
0x0000ffff
Continuation state: 2
00 35 .5
> HCI Event (0x13) plen 5 [hci0] 31.106718
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 44 [hci0] 31.107962
Channel: 64 len 40 [PSM 1 mode 0] {chan 0}
SDP: Service Search Attribute Response (0x07) tid 8 len 35
Attribute bytes: 32
Continuation state: 0
Combined attribute bytes: 85
Attribute list: [len 80] {position 0}
Attribute: Service Record Handle (0x0000) [len 2]
0x00010002
Attribute: Service Class ID List (0x0001) [len 2]
UUID (3) with 2 bytes [0 extra bits] len 3
Handsfree (0x111e)
UUID (3) with 2 bytes [0 extra bits] len 3
Generic Audio (0x1203)
Attribute: Protocol Descriptor List (0x0004) [len 2]
Sequence (6) with 3 bytes [8 extra bits] len 5
UUID (3) with 2 bytes [0 extra bits] len 3
L2CAP (0x0100)
Sequence (6) with 5 bytes [8 extra bits] len 7
UUID (3) with 2 bytes [0 extra bits] len 3
RFCOMM (0x0003)
Unsigned Integer (1) with 1 byte [0 extra bits] len 2
0x02
Attribute: Browse Group List (0x0005) [len 2]
UUID (3) with 2 bytes [0 extra bits] len 3
Public Browse Root (0x1002)
Attribute: Bluetooth Profile Descriptor List (0x0009) [len 2]
Sequence (6) with 6 bytes [8 extra bits] len 8
UUID (3) with 2 bytes [0 extra bits] len 3
Handsfree (0x111e)
Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
0x0105
Attribute: Unknown (0x0100) [len 2]
HFP service [len 12]
Attribute: Unknown (0x0311) [len 2]
0x001b
< ACL Data TX flags 0x00 dlen 12 [hci0] 31.108484
L2CAP: Connection Request (0x02) ident 4 len 4
PSM: 3 (0x0003)
Source CID: 65
> HCI Event (0x13) plen 5 [hci0] 31.111705
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 16 [hci0] 31.112953
L2CAP: Connection Response (0x03) ident 4 len 8
Destination CID: 68
Source CID: 65
Result: Connection successful (0x0000)
Status: No further information available (0x0000)
< ACL Data TX flags 0x00 dlen 16 [hci0] 31.112979
L2CAP: Configure Request (0x04) ident 5 len 8
Destination CID: 68
Flags: 0x0000
Option: Maximum Transmission Unit (0x01)
MTU: 1013
> ACL Data RX flags 0x02 dlen 16 [hci0] 31.116703
L2CAP: Configure Request (0x04) ident 3 len 8
Destination CID: 65
Flags: 0x0000
Option: Maximum Transmission Unit (0x01)
MTU: 1024
> HCI Event (0x13) plen 5 [hci0] 31.116714
Num handles: 1
Handle: 256
Count: 1
< ACL Data TX flags 0x00 dlen 18 [hci0] 31.116742
L2CAP: Configure Response (0x05) ident 3 len 10
Source CID: 68
Flags: 0x0000
Result: Success (0x0000)
Option: Maximum Transmission Unit (0x01)
MTU: 1024
> ACL Data RX flags 0x02 dlen 14 [hci0] 31.117950
L2CAP: Configure Response (0x05) ident 5 len 6
Source CID: 65
Flags: 0x0000
Result: Success (0x0000)
< ACL Data TX flags 0x00 dlen 8 [hci0] 31.118046
Channel: 68 len 4 [PSM 3 mode 0] {chan 1}
03 3f 01 1c .?..
> HCI Event (0x13) plen 5 [hci0] 31.120702
Num handles: 1
Handle: 256
Count: 1
> HCI Event (0x13) plen 5 [hci0] 31.121697
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 8 [hci0] 31.122697
Channel: 65 len 4 [PSM 3 mode 0] {chan 1}
03 73 01 d7 .s..
< ACL Data TX flags 0x00 dlen 18 [hci0] 31.122799
Channel: 68 len 14 [PSM 3 mode 0] {chan 1}
03 ef 15 83 11 04 f0 07 00 f0 03 00 07 70 .............p
> HCI Event (0x13) plen 5 [hci0] 31.126699
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 18 [hci0] 31.127694
Channel: 65 len 14 [PSM 3 mode 0] {chan 1}
01 ef 15 81 11 04 e0 07 00 ff 00 00 07 aa ..............
< ACL Data TX flags 0x00 dlen 8 [hci0] 31.127795
Channel: 68 len 4 [PSM 3 mode 0] {chan 1}
13 3f 01 96 .?..
> HCI Event (0x13) plen 5 [hci0] 31.131699
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 8 [hci0] 31.132691
Channel: 65 len 4 [PSM 3 mode 0] {chan 1}
13 73 01 5d .s.]
< ACL Data TX flags 0x00 dlen 12 [hci0] 31.132733
Channel: 68 len 8 [PSM 3 mode 0] {chan 1}
03 ef 09 e3 05 13 8d 70 .......p
> ACL Data RX flags 0x02 dlen 12 [hci0] 31.134208
L2CAP: Connection Request (0x02) ident 4 len 4
PSM: 1 (0x0001)
Source CID: 69
< ACL Data TX flags 0x00 dlen 16 [hci0] 31.134238
L2CAP: Connection Response (0x03) ident 4 len 8
Destination CID: 66
Source CID: 69
Result: Connection successful (0x0000)
Status: No further information available (0x0000)
< ACL Data TX flags 0x00 dlen 12 [hci0] 31.134242
L2CAP: Configure Request (0x04) ident 6 len 4
Destination CID: 69
Flags: 0x0000
> HCI Event (0x13) plen 5 [hci0] 31.136698
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 12 [hci0] 31.137952
Channel: 65 len 8 [PSM 3 mode 0] {chan 1}
01 ef 09 e1 05 13 8d aa ........
> HCI Event (0x13) plen 5 [hci0] 31.138724
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 12 [hci0] 31.139098
Channel: 65 len 8 [PSM 3 mode 0] {chan 1}
01 ef 09 e3 05 13 8d aa ........
< ACL Data TX flags 0x00 dlen 12 [hci0] 31.139163
Channel: 68 len 8 [PSM 3 mode 0] {chan 1}
03 ef 09 e1 05 13 8d 70 .......p
< ACL Data TX flags 0x00 dlen 9 [hci0] 31.139170
Channel: 68 len 5 [PSM 3 mode 0] {chan 1}
13 ff 01 21 79 ...!y
> HCI Event (0x13) plen 5 [hci0] 31.139726
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 16 [hci0] 31.140473
L2CAP: Configure Request (0x04) ident 5 len 8
Destination CID: 66
Flags: 0x0000
Option: Maximum Transmission Unit (0x01)
MTU: 64
< ACL Data TX flags 0x00 dlen 18 [hci0] 31.140505
L2CAP: Configure Response (0x05) ident 5 len 10
Source CID: 69
Flags: 0x0000
Result: Success (0x0000)
Option: Maximum Transmission Unit (0x01)
MTU: 64
> ACL Data RX flags 0x02 dlen 14 [hci0] 31.141754
L2CAP: Configure Response (0x05) ident 6 len 6
Source CID: 66
Flags: 0x0000
Result: Success (0x0000)
> HCI Event (0x13) plen 5 [hci0] 31.143762
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 20 [hci0] 31.144187
Channel: 65 len 16 [PSM 3 mode 0] {chan 1}
11 ff 17 09 41 54 2b 42 52 53 46 3d 32 37 0d a3 ....AT+BRSF=27..
< ACL Data TX flags 0x00 dlen 22 [hci0] 31.144324
Channel: 68 len 18 [PSM 3 mode 0] {chan 1}
13 ef 1d 0d 0a 2b 42 52 53 46 3a 20 33 35 32 0d .....+BRSF: 352.
0a 65 .e
< ACL Data TX flags 0x00 dlen 14 [hci0] 31.144332
Channel: 68 len 10 [PSM 3 mode 0] {chan 1}
13 ef 0d 0d 0a 4f 4b 0d 0a 65 .....OK..e
> HCI Event (0x13) plen 5 [hci0] 31.144605
Num handles: 1
Handle: 256
Count: 1
> HCI Event (0x13) plen 5 [hci0] 31.145757
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 28 [hci0] 31.146503
Channel: 66 len 24 [PSM 1 mode 0] {chan 2}
SDP: Service Search Attribute Request (0x06) tid 0 len 19
Search pattern: [len 5]
Sequence (6) with 3 bytes [8 extra bits] len 5
UUID (3) with 2 bytes [0 extra bits] len 3
Handsfree Audio Gateway (0x111f)
Max record count: 48
Attribute list: [len 11]
Sequence (6) with 9 bytes [8 extra bits] len 11
Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
0x0001
Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
0x0009
Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
0x0311
Continuation state: 0
< ACL Data TX flags 0x00 dlen 46 [hci0] 31.146720
Channel: 69 len 42 [PSM 1 mode 0] {chan 2}
SDP: Service Search Attribute Response (0x07) tid 0 len 37
Attribute bytes: 34
Attribute list: [len 30] {position 0}
Attribute: Service Class ID List (0x0001) [len 2]
UUID (3) with 2 bytes [0 extra bits] len 3
Handsfree Audio Gateway (0x111f)
UUID (3) with 2 bytes [0 extra bits] len 3
Generic Audio (0x1203)
Attribute: Bluetooth Profile Descriptor List (0x0009) [len 2]
Sequence (6) with 6 bytes [8 extra bits] len 8
UUID (3) with 2 bytes [0 extra bits] len 3
Handsfree (0x111e)
Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
0x0105
Attribute: Unknown (0x0311) [len 2]
0x0000
Continuation state: 0
> HCI Event (0x13) plen 5 [hci0] 31.148755
Num handles: 1
Handle: 256
Count: 1
> HCI Event (0x13) plen 5 [hci0] 31.149755
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 19 [hci0] 31.150250
Channel: 65 len 15 [PSM 3 mode 0] {chan 1}
11 ff 15 02 41 54 2b 43 49 4e 44 3d 3f 0d a3 ....AT+CIND=?..
< ACL Data TX flags 0x00 dlen 141 [hci0] 31.150438
Channel: 68 len 137 [PSM 3 mode 0] {chan 1}
13 ef 08 01 0d 0a 2b 43 49 4e 44 3a 20 28 22 62 ......+CIND: ("b
61 74 74 63 68 67 22 2c 28 30 2d 35 29 29 2c 28 attchg",(0-5)),(
22 73 69 67 6e 61 6c 22 2c 28 30 2d 35 29 29 2c "signal",(0-5)),
28 22 73 65 72 76 69 63 65 22 2c 28 30 2c 31 29 ("service",(0,1)
29 2c 28 22 63 61 6c 6c 22 2c 28 30 2c 31 29 29 ),("call",(0,1))
2c 28 22 63 61 6c 6c 73 65 74 75 70 22 2c 28 30 ,("callsetup",(0
2d 33 29 29 2c 28 22 63 61 6c 6c 68 65 6c 64 22 -3)),("callheld"
2c 28 30 2d 32 29 29 2c 28 22 72 6f 61 6d 22 2c ,(0-2)),("roam",
28 30 2c 31 29 29 0d 0a 65 (0,1))..e
< ACL Data TX flags 0x00 dlen 14 [hci0] 31.150448
Channel: 68 len 10 [PSM 3 mode 0] {chan 1}
13 ef 0d 0d 0a 4f 4b 0d 0a 65 .....OK..e
> HCI Event (0x13) plen 5 [hci0] 31.150729
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 12 [hci0] 31.151699
L2CAP: Disconnection Request (0x06) ident 6 len 4
Destination CID: 66
Source CID: 69
< ACL Data TX flags 0x00 dlen 12 [hci0] 31.151732
L2CAP: Disconnection Response (0x07) ident 6 len 4
Destination CID: 66
Source CID: 69
> HCI Event (0x13) plen 5 [hci0] 31.155700
Num handles: 1
Handle: 256
Count: 1
> HCI Event (0x13) plen 5 [hci0] 31.156717
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 18 [hci0] 31.157715
Channel: 65 len 14 [PSM 3 mode 0] {chan 1}
11 ff 13 02 41 54 2b 43 49 4e 44 3f 0d a3 ....AT+CIND?..
< ACL Data TX flags 0x00 dlen 32 [hci0] 31.157811
Channel: 68 len 28 [PSM 3 mode 0] {chan 1}
13 ef 31 0d 0a 2b 43 49 4e 44 3a 20 35 2c 35 2c ..1..+CIND: 5,5,
31 2c 30 2c 30 2c 30 2c 30 0d 0a 65 1,0,0,0,0..e
< ACL Data TX flags 0x00 dlen 14 [hci0] 31.157820
Channel: 68 len 10 [PSM 3 mode 0] {chan 1}
13 ef 0d 0d 0a 4f 4b 0d 0a 65 .....OK..e
> HCI Event (0x13) plen 5 [hci0] 31.158716
Num handles: 1
Handle: 256
Count: 1
> HCI Event (0x13) plen 5 [hci0] 31.162700
Num handles: 1
Handle: 256
Count: 1
> HCI Event (0x13) plen 5 [hci0] 31.166681
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 25 [hci0] 31.167709
Channel: 65 len 21 [PSM 3 mode 0] {chan 1}
11 ff 21 02 41 54 2b 43 4d 45 52 3d 33 2c 30 2c ..!.AT+CMER=3,0,
30 2c 31 0d a3 0,1..
< ACL Data TX flags 0x00 dlen 14 [hci0] 31.167854
Channel: 68 len 10 [PSM 3 mode 0] {chan 1}
13 ef 0d 0d 0a 4f 4b 0d 0a 65 .....OK..e
> HCI Event (0x13) plen 5 [hci0] 31.171687
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 19 [hci0] 31.197692
Channel: 65 len 15 [PSM 3 mode 0] {chan 1}
11 ff 15 01 41 54 2b 43 43 57 41 3d 31 0d a3 ....AT+CCWA=1..
< ACL Data TX flags 0x00 dlen 14 [hci0] 31.197863
Channel: 68 len 10 [PSM 3 mode 0] {chan 1}
13 ef 0d 0d 0a 4f 4b 0d 0a 65 .....OK..e
> HCI Event (0x13) plen 5 [hci0] 31.201671
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 31 [hci0] 31.203939
Channel: 65 len 27 [PSM 3 mode 0] {chan 1}
11 ff 2d 01 41 54 2b 42 49 41 3d 30 2c 30 2c 31 ..-.AT+BIA=0,0,1
2c 31 2c 31 2c 31 2c 30 2c 0d a3 ,1,1,1,0,..
< ACL Data TX flags 0x00 dlen 17 [hci0] 31.204263
Channel: 68 len 13 [PSM 3 mode 0] {chan 1}
13 ef 13 0d 0a 45 52 52 4f 52 0d 0a 65 .....ERROR..e
> HCI Event (0x13) plen 5 [hci0] 31.208729
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 20 [hci0] 31.208907
Channel: 65 len 16 [PSM 3 mode 0] {chan 1}
11 ff 17 01 41 54 2b 43 42 43 3d 31 30 30 0d a3 ....AT+CBC=100..
< ACL Data TX flags 0x00 dlen 17 [hci0] 31.209194
Channel: 68 len 13 [PSM 3 mode 0] {chan 1}
13 ef 13 0d 0a 45 52 52 4f 52 0d 0a 65 .....ERROR..e
> HCI Event (0x13) plen 5 [hci0] 31.213727
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 19 [hci0] 31.213935
Channel: 65 len 15 [PSM 3 mode 0] {chan 1}
11 ff 15 01 41 54 2b 56 47 53 3d 31 35 0d a3 ....AT+VGS=15..
< ACL Data TX flags 0x00 dlen 14 [hci0] 31.214182
Channel: 68 len 10 [PSM 3 mode 0] {chan 1}
13 ef 0d 0d 0a 4f 4b 0d 0a 65 .....OK..e
> HCI Event (0x13) plen 5 [hci0] 31.218699
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 21 [hci0] 31.218903
Channel: 65 len 17 [PSM 3 mode 0] {chan 1}
11 ff 19 01 41 54 2b 43 4f 50 53 3d 33 2c 30 0d ....AT+COPS=3,0.
a3 .
< ACL Data TX flags 0x00 dlen 14 [hci0] 31.219151
Channel: 68 len 10 [PSM 3 mode 0] {chan 1}
13 ef 0d 0d 0a 4f 4b 0d 0a 65 .....OK..e
> HCI Event (0x13) plen 5 [hci0] 31.223655
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 19 [hci0] 31.223901
Channel: 65 len 15 [PSM 3 mode 0] {chan 1}
11 ff 15 01 41 54 2b 43 4d 45 45 3d 31 0d a3 ....AT+CMEE=1..
< ACL Data TX flags 0x00 dlen 14 [hci0] 31.224044
Channel: 68 len 10 [PSM 3 mode 0] {chan 1}
13 ef 0d 0d 0a 4f 4b 0d 0a 65 .....OK..e
> HCI Event (0x13) plen 5 [hci0] 31.229657
Num handles: 1
Handle: 256
Count: 1
< ACL Data TX flags 0x00 dlen 12 [hci0] 32.913824
L2CAP: Disconnection Request (0x06) ident 7 len 4
Destination CID: 67
Source CID: 64
< ACL Data TX flags 0x00 dlen 12 [hci0] 32.913967
L2CAP: Connection Request (0x02) ident 8 len 4
PSM: 25 (0x0019)
Source CID: 66
> HCI Event (0x13) plen 5 [hci0] 32.917809
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 12 [hci0] 32.918175
L2CAP: Disconnection Response (0x07) ident 7 len 4
Destination CID: 67
Source CID: 64
> HCI Event (0x13) plen 5 [hci0] 32.918799
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 16 [hci0] 32.919548
L2CAP: Connection Response (0x03) ident 8 len 8
Destination CID: 70
Source CID: 66
Result: Connection successful (0x0000)
Status: No further information available (0x0000)
< ACL Data TX flags 0x00 dlen 12 [hci0] 32.919590
L2CAP: Configure Request (0x04) ident 9 len 4
Destination CID: 70
Flags: 0x0000
> ACL Data RX flags 0x02 dlen 16 [hci0] 32.920800
L2CAP: Configure Request (0x04) ident 7 len 8
Destination CID: 66
Flags: 0x0000
Option: Maximum Transmission Unit (0x01)
MTU: 672
< ACL Data TX flags 0x00 dlen 18 [hci0] 32.920846
L2CAP: Configure Response (0x05) ident 7 len 10
Source CID: 70
Flags: 0x0000
Result: Success (0x0000)
Option: Maximum Transmission Unit (0x01)
MTU: 672
> HCI Event (0x13) plen 5 [hci0] 32.923795
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 14 [hci0] 32.924545
L2CAP: Configure Response (0x05) ident 9 len 6
Source CID: 66
Flags: 0x0000
Result: Success (0x0000)
< ACL Data TX flags 0x00 dlen 6 [hci0] 32.924675
Channel: 70 len 2 [PSM 25 mode 0] {chan 2}
00 01 ..
> HCI Event (0x13) plen 5 [hci0] 32.924798
Num handles: 1
Handle: 256
Count: 1
> HCI Event (0x13) plen 5 [hci0] 32.928796
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 8 [hci0] 32.929291
Channel: 66 len 4 [PSM 25 mode 0] {chan 2}
02 01 04 08 ....
< ACL Data TX flags 0x00 dlen 7 [hci0] 32.929397
Channel: 70 len 3 [PSM 25 mode 0] {chan 2}
10 02 04 ...
> HCI Event (0x13) plen 5 [hci0] 32.933791
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 16 [hci0] 32.934578
Channel: 66 len 12 [PSM 25 mode 0] {chan 2}
12 02 01 00 07 06 00 00 ff ff 02 59 ...........Y
< ACL Data TX flags 0x00 dlen 18 [hci0] 32.934704
Channel: 70 len 14 [PSM 25 mode 0] {chan 2}
20 03 04 04 01 00 07 06 00 00 21 15 02 35 .........!..5
> HCI Event (0x13) plen 5 [hci0] 32.938861
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 6 [hci0] 32.939354
Channel: 66 len 2 [PSM 25 mode 0] {chan 2}
22 03 ".
< ACL Data TX flags 0x00 dlen 7 [hci0] 32.939468
Channel: 70 len 3 [PSM 25 mode 0] {chan 2}
30 06 04 0..
> HCI Event (0x13) plen 5 [hci0] 32.943806
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 6 [hci0] 32.944301
Channel: 66 len 2 [PSM 25 mode 0] {chan 2}
32 06 2.
< ACL Data TX flags 0x00 dlen 12 [hci0] 32.944424
L2CAP: Connection Request (0x02) ident 10 len 4
PSM: 25 (0x0019)
Source CID: 64
> HCI Event (0x13) plen 5 [hci0] 32.948804
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 16 [hci0] 32.949551
L2CAP: Connection Response (0x03) ident 10 len 8
Destination CID: 71
Source CID: 64
Result: Connection successful (0x0000)
Status: No further information available (0x0000)
< ACL Data TX flags 0x00 dlen 12 [hci0] 32.949582
L2CAP: Configure Request (0x04) ident 11 len 4
Destination CID: 71
Flags: 0x0000
> ACL Data RX flags 0x02 dlen 20 [hci0] 32.950571
L2CAP: Configure Request (0x04) ident 8 len 12
Destination CID: 64
Flags: 0x0000
Option: Maximum Transmission Unit (0x01)
MTU: 1008
Option: Flush Timeout (0x02)
Flush timeout: 200
< ACL Data TX flags 0x00 dlen 18 [hci0] 32.950597
L2CAP: Configure Response (0x05) ident 8 len 10
Source CID: 71
Flags: 0x0000
Result: Success (0x0000)
Option: Maximum Transmission Unit (0x01)
MTU: 1008
> HCI Event (0x13) plen 5 [hci0] 32.953824
Num handles: 1
Handle: 256
Count: 1
> ACL Data RX flags 0x02 dlen 14 [hci0] 32.954566
L2CAP: Configure Response (0x05) ident 11 len 6
Source CID: 64
Flags: 0x0000
Result: Success (0x0000)
> HCI Event (0x13) plen 5 [hci0] 32.954798
Num handles: 1
Handle: 256
Count: 1
< HCI Command (0x01|0x0028) plen 17 [hci0] 32.964171
Handle: 256
Transmit bandwidth: 8000
Receive bandwidth: 8000
Max latency: 65535
Setting: 0x0060
Retransmission effort: Don't care (0xff)
Packet type: 0x003f
> HCI Event (0x0f) plen 4 [hci0] 32.965775
Setup Synchronous Connection (0x01|0x0028) ncmd 1
Status: Success (0x00)
> HCI Event (0x1b) plen 3 [hci0] 32.969774
Handle: 256
Max slots: 1
> HCI Event (0x2c) plen 17 [hci0] 32.986795
Status: Success (0x00)
Handle: 257
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
Link type: eSCO (0x02)
Transmission interval: 0x0c
Retransmission window: 0x02
RX packet length: 60
TX packet length: 60
Air mode: CVSD (0x02)
< ACL Data TX flags 0x00 dlen 19 [hci0] 32.987649
Channel: 68 len 15 [PSM 3 mode 0] {chan 1}
13 ef 17 0d 0a 2b 56 47 53 3d 31 35 0d 0a 65 .....+VGS=15..e
< ACL Data TX flags 0x00 dlen 19 [hci0] 32.987662
Channel: 68 len 15 [PSM 3 mode 0] {chan 1}
13 ef 17 0d 0a 2b 56 47 4d 3d 31 35 0d 0a 65 .....+VGM=15..e
> HCI Event (0x1b) plen 3 [hci0] 32.991768
Handle: 256
Max slots: 5
> HCI Event (0x13) plen 5 [hci0] 32.992762
Num handles: 1
Handle: 256
Count: 1
< SCO Data TX flags 0x00 dlen 48 [hci0] 32.993934
> HCI Event (0x13) plen 5 [hci0] 32.995762
Num handles: 1
Handle: 256
Count: 1
> HCI Event (0x14) plen 6 [hci0] 37.801432
Status: Success (0x00)
Handle: 256
Mode: Sniff (0x02)
Interval: 247.500 msec (0x018c)
< HCI Command (0x01|0x0006) plen 3 [hci0] 38.011637
Handle: 257
Reason: Remote User Terminated Connection (0x13)
> HCI Event (0x0f) plen 4 [hci0] 38.012251
Disconnect (0x01|0x0006) ncmd 1
Status: Success (0x00)
> HCI Event (0x05) plen 4 [hci0] 38.051233
Status: Success (0x00)
Handle: 257
Reason: Connection Terminated By Local Host (0x16)
> HCI Event (0x14) plen 6 [hci0] 38.057234
Status: Success (0x00)
Handle: 256
Mode: Active (0x00)
Interval: 0.000 msec (0x0000)
> HCI Event (0x14) plen 6 [hci0] 42.803863
Status: Success (0x00)
Handle: 256
Mode: Sniff (0x02)
Interval: 500.000 msec (0x0320)
< HCI Command (0x02|0x0004) plen 2 [hci0] 42.927906
Handle: 256
> HCI Event (0x0f) plen 4 [hci0] 42.928836
Exit Sniff Mode (0x02|0x0004) ncmd 1
Status: Success (0x00)
> HCI Event (0x14) plen 6 [hci0] 43.264703
Status: Success (0x00)
Handle: 256
Mode: Active (0x00)
Interval: 0.000 msec (0x0000)
< HCI Command (0x01|0x0028) plen 17 [hci0] 43.264779
Handle: 256
Transmit bandwidth: 8000
Receive bandwidth: 8000
Max latency: 65535
Setting: 0x0060
Retransmission effort: Don't care (0xff)
Packet type: 0x003f
> HCI Event (0x0f) plen 4 [hci0] 43.265703
Setup Synchronous Connection (0x01|0x0028) ncmd 1
Status: Success (0x00)
> HCI Event (0x1b) plen 3 [hci0] 43.271679
Handle: 256
Max slots: 1
> HCI Event (0x2c) plen 17 [hci0] 43.290665
Status: Success (0x00)
Handle: 257
Address: 78:F7:BE:08:5E:DF (OUI 78-F7-BE)
Link type: eSCO (0x02)
Transmission interval: 0x0c
Retransmission window: 0x02
RX packet length: 60
TX packet length: 60
Air mode: CVSD (0x02)
< ACL Data TX flags 0x00 dlen 19 [hci0] 43.291490
Channel: 68 len 15 [PSM 3 mode 0] {chan 1}
13 ef 17 0d 0a 2b 56 47 53 3d 31 35 0d 0a 65 .....+VGS=15..e
< ACL Data TX flags 0x00 dlen 19 [hci0] 43.291512
Channel: 68 len 15 [PSM 3 mode 0] {chan 1}
13 ef 17 0d 0a 2b 56 47 4d 3d 31 35 0d 0a 65 .....+VGM=15..e
< SCO Data TX flags 0x00 dlen 48 [hci0] 43.295627
< SCO Data TX flags 0x00 dlen 48 [hci0] 43.295850
> HCI Event (0x1b) plen 3 [hci0] 43.296621
Handle: 256
Max slots: 5
> HCI Event (0x13) plen 5 [hci0] 43.297623
Num handles: 1
Handle: 256
Count: 1
> HCI Event (0x13) plen 5 [hci0] 43.298627
Num handles: 1
Handle: 256
Count: 1
> HCI Event (0x14) plen 6 [hci0] 47.786446
Status: Success (0x00)
Handle: 256
Mode: Sniff (0x02)
Interval: 247.500 msec (0x018c)
< HCI Command (0x01|0x0006) plen 3 [hci0] 49.907615
Handle: 257
Reason: Remote User Terminated Connection (0x13)
> HCI Event (0x0f) plen 4 [hci0] 49.908340
Disconnect (0x01|0x0006) ncmd 1
Status: Success (0x00)
> HCI Event (0x05) plen 4 [hci0] 50.015272
Status: Success (0x00)
Handle: 257
Reason: Connection Terminated By Local Host (0x16)
> HCI Event (0x14) plen 6 [hci0] 50.021320
Status: Success (0x00)
Handle: 256
Mode: Active (0x00)
Interval: 0.000 msec (0x0000)
> HCI Event (0x14) plen 6 [hci0] 54.795921
Status: Success (0x00)
Handle: 256
Mode: Sniff (0x02)
Interval: 500.000 msec (0x0320)
>
> Regards
>
> Marcel
>
>
>

Attachments:

lenovo-m4400s-btmon.log (11.52 kB)

2013-12-20 12:30:01