Android Tablets Forum banner
1 - 20 of 38 Posts

·
Registered
Joined
·
130 Posts
(See also the previous thread http://www.slatedroid.com/topic/22388-kernel-discussion-for-fview-7-pro-lanyu-910-tablets/ )

The problem is that most of the commands having to do with access the hci0 adapter internal information - getting or setting the name, getting version and revision number, etc. - fail on the tablet with a timeout error. E.g. "hciconfig hci0 version". On other hand, data traffic does seem to work, e.g. "sdptool browse address" or connecting to a rfcomm device do work.

I added some debug output to the drivers and enabled the existing and new debug output. Here's a comparison of debug output from table "Linux version 2.6.32.27 ([email protected])" and host 2.6.38. The 2.6.38 has some modifications to the bluetooth code, but not that much, so these should be comparable.

Update: Come to think of it, I forgot to plug in the USB device from the tablet to the laptop, so the devices are not the same, but the laptop internal USB BT is used - it's "Bus 002 Device 002: ID 03f0:171d Hewlett-Packard Wireless (Bluetooth + WLAN) Interface [Integrated Module]" in lsusb output.

First, the non-working code from the tablet, as it's much shorter. Hci0 is up, and command is "hciconfig hci0 name".

Code:
<br />
<7>[16448.260145] hci_sock_create: sock d28b1200<br />
<7>[16448.260210] hci_sock_ioctl: cmd 800448d3 arg 16234<br />
<7>[16448.260228] hci_dev_get: 0<br />
<7>[16448.260301] hci_sock_create: sock d28b1c80<br />
<7>[16448.260332] hci_sock_bind: sock d28b1c80 sk cc1e7800<br />
<7>[16448.260347] hci_dev_get: 0<br />
<7>[16448.260392] hci_sock_setsockopt: sk cc1e7800, opt 2<br />
<7>[16448.260421] hci_sock_sendmsg: sock d28b1c80 sk cc1e7800<br />
<7>[16448.260460] hci_cmd_task: hci0 cmd 1<br />
<7>[16448.260485] hci_send_frame: hci0 type 1 len 3<br />
<7>[16448.260503] hci_send_to_sock: hdev raw d20c8400 len 3<br />
<7>[16448.260520] btusb_send_frame: hci0<br />
<7>[16448.261977] btusb_tx_complete: hci0 urb c4974ec0 status 0 count 3<br />
<7>[16448.262942] btusb_intr_complete: hci0 urb c4874240 status 0 count 10<br />
<7>[16448.262979] hci_rx_task: hci0<br />
<7>[16448.262993] hci_rx_task: hci0 promisc: 0x1<br />
<7>[16448.263007] hci_send_to_sock: hdev raw d20c8400 len 10<br />
<7>[16448.263021] hci_rx_task: hci0 event packet<br />
<7>[16448.263037] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
<7>[16448.263051] hci_cmd_complete_evt: hci0 ev->opcode 0x1401<br />
<7>[16448.263064] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x82<br />
<7>[16448.263079] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
<7>[16448.263092] hci_cmd_complete_evt: hci0 &ev->opcode-2 0x8<br />
<7>[16448.263106] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
<7>[16448.263120] hci_cmd_complete_evt: hci0 &ev->opcode 0x1<br />
<7>[16448.263134] hci_cmd_complete_evt: hci0 &ev->opcode+1 0x14<br />
<7>[16448.263148] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x12<br />
<7>[16448.263162] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x2<br />
<7>[16448.263176] hci_cmd_complete_evt: hci0 &ev->opcode+4 0xe0<br />
<7>[16448.263192] hci_cmd_complete_evt: hci0 default (non-recognized) opcode 0x1401<br />
<7>[16448.263209] hci_cmd_complete_evt: hci0 opcode 0x1401 (recognized if not twice)<br />
<7>[16448.263226] hci_event_packet: hci0 event 0xe<br />
<7>[16449.261659] hci_sock_setsockopt: sk cc1e7800, opt 2<br />
<7>[16449.262235] hci_sock_release: sock d28b1200 sk d20d8e00<br />
<7>[16449.262286] hci_sock_release: sock d28b1c80 sk cc1e7800<br />
Then the working code from the laptop. Like on the tablet, hci0 is up, and command is "hciconfig hci0 name".

Code:
<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069456] hci_sock_create: sock f0a8ac40<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069476] hci_sock_ioctl: cmd 800448d3 arg fef240<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069479] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069491] hci_sock_ioctl: cmd 400448c9 arg 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069493] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069496] hci_dev_open: hci0 da350800<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069499] btusb_open: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069503] btusb_submit_intr_urb: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069513] btusb_submit_bulk_urb: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069519] btusb_submit_bulk_urb: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069526] __hci_request: hci0 start<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069529] hci_init_req: hci0 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069532] hci_send_cmd: hci0 opcode 0xc03 plen 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069535] hci_send_cmd: skb len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069542] hci_send_cmd: hci0 opcode 0x1003 plen 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069544] hci_send_cmd: skb len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069546] hci_send_cmd: hci0 opcode 0x1001 plen 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069549] hci_send_cmd: skb len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069551] hci_send_cmd: hci0 opcode 0x1005 plen 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069553] hci_send_cmd: skb len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069555] hci_send_cmd: hci0 opcode 0x1009 plen 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069558] hci_send_cmd: skb len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069560] hci_send_cmd: hci0 opcode 0xc23 plen 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069562] hci_send_cmd: skb len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069564] hci_send_cmd: hci0 opcode 0xc14 plen 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069567] hci_send_cmd: skb len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069569] hci_send_cmd: hci0 opcode 0xc25 plen 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069571] hci_send_cmd: skb len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069573] hci_send_cmd: hci0 opcode 0xc05 plen 1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069576] hci_send_cmd: skb len 4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069578] hci_send_cmd: hci0 opcode 0xc18 plen 2<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069580] hci_send_cmd: skb len 5<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069583] hci_send_cmd: hci0 opcode 0xc16 plen 2<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069586] hci_send_cmd: skb len 5<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069593] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069596] hci_send_frame: hci0 type 1 len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069599] hci_send_to_sock: hdev da350800 len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.069602] btusb_send_frame: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.070612] btusb_tx_complete: hci0 urb f650e100 status 0 count 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073612] btusb_intr_complete: hci0 urb f650ea00 status 0 count 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073622] hci_rx_task: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073625] hci_rx_task: hci0 promisc: 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073627] hci_send_to_sock: hdev da350800 len 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073637] hci_rx_task: hci0 event packet<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073639] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073642] hci_cmd_complete_evt: hci0 ev->opcode 0xc03<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073644] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073646] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073648] hci_cmd_complete_evt: hci0 &ev->opcode-2 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073650] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073652] hci_cmd_complete_evt: hci0 &ev->opcode 0x3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073654] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073656] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073658] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073660] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073662] hci_cc_reset: hci0 status 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073665] hci_req_complete: hci0 command 0x0c03 result 0x00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073667] hci_cmd_complete_evt: hci0 opcode 0xc03 (recognized if not twice)<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073669] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073672] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073675] hci_send_frame: hci0 type 1 len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073679] hci_send_to_sock: hdev da350800 len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073680] btusb_send_frame: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073727] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073737] hci_sock_create: sock f0a06e00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073744] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073746] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.073750] hci_sock_release: sock f0a06e00 sk f151d000<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.074608] btusb_tx_complete: hci0 urb eef4cc00 status 0 count 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075608] btusb_intr_complete: hci0 urb f650ea00 status 0 count 14<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075618] hci_rx_task: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075620] hci_rx_task: hci0 promisc: 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075622] hci_send_to_sock: hdev da350800 len 14<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075631] hci_rx_task: hci0 event packet<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075634] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075636] hci_cmd_complete_evt: hci0 ev->opcode 0x1003<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075638] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075640] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075642] hci_cmd_complete_evt: hci0 &ev->opcode-2 0xc<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075644] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075646] hci_cmd_complete_evt: hci0 &ev->opcode 0x3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075648] hci_cmd_complete_evt: hci0 &ev->opcode+1 0x10<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075650] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075653] hci_cmd_complete_evt: hci0 &ev->opcode+3 0xffffffff<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075658] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075659] hci_cmd_complete_evt: hci0 &ev->opcode+4 0xffffffff<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075661] hci_cc_read_local_features: hci0 status 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075666] hci_sock_create: sock f0a8ae00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075667] hci_cc_read_local_features: hci0 features 0xffff8ffe9bf90080<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075669] hci_cmd_complete_evt: hci0 opcode 0x1003 (recognized if not twice)<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075672] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075675] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075679] hci_send_frame: hci0 type 1 len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075683] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075685] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075689] hci_sock_release: sock f0a8ae00 sk f1712800<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075689] hci_send_to_sock: hdev da350800 len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.075692] btusb_send_frame: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.076608] btusb_tx_complete: hci0 urb eef4cc00 status 0 count 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077609] btusb_intr_complete: hci0 urb f650ea00 status 0 count 14<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077619] hci_rx_task: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077622] hci_rx_task: hci0 promisc: 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077624] hci_send_to_sock: hdev da350800 len 14<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077633] hci_rx_task: hci0 event packet<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077636] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077638] hci_cmd_complete_evt: hci0 ev->opcode 0x1001<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077640] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077642] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077644] hci_cmd_complete_evt: hci0 &ev->opcode-2 0xc<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077646] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077648] hci_cmd_complete_evt: hci0 &ev->opcode 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077650] hci_cmd_complete_evt: hci0 &ev->opcode+1 0x10<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077653] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077655] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077657] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x29<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077659] hci_cc_read_local_version: hci0 status 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077662] hci_cc_read_local_version: hci0 manufacturer 15 hci ver 3:8489<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077664] hci_cmd_complete_evt: hci0 opcode 0x1001 (recognized if not twice)<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077667] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077669] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077672] hci_send_frame: hci0 type 1 len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077675] hci_send_to_sock: hdev da350800 len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077677] btusb_send_frame: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077699] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077707] hci_sock_create: sock f0a06e00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077713] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077715] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.077719] hci_sock_release: sock f0a06e00 sk f151d000<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.078607] btusb_tx_complete: hci0 urb eef4cc00 status 0 count 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079607] btusb_intr_complete: hci0 urb f650ea00 status 0 count 13<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079615] hci_rx_task: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079617] hci_rx_task: hci0 promisc: 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079620] hci_send_to_sock: hdev da350800 len 13<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079626] hci_rx_task: hci0 event packet<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079628] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079630] hci_cmd_complete_evt: hci0 ev->opcode 0x1005<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079632] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079634] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079637] hci_cmd_complete_evt: hci0 &ev->opcode-2 0xb<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079639] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079641] hci_cmd_complete_evt: hci0 &ev->opcode 0x5<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079643] hci_cmd_complete_evt: hci0 &ev->opcode+1 0x10<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079647] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079648] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079651] hci_cmd_complete_evt: hci0 &ev->opcode+3 0xfffffff9<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079655] hci_sock_create: sock f0a8ae00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079655] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079657] hci_cc_read_buffer_size: hci0 status 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079662] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079664] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079665] hci_cc_read_buffer_size: hci0 acl mtu 1017:8 sco mtu 64:8<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079670] hci_sock_release: sock f0a8ae00 sk f1712800<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079670] hci_cmd_complete_evt: hci0 opcode 0x1005 (recognized if not twice)<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079673] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079676] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079679] hci_send_frame: hci0 type 1 len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079682] hci_send_to_sock: hdev da350800 len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.079684] btusb_send_frame: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.080609] btusb_tx_complete: hci0 urb eef4cc00 status 0 count 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081608] btusb_intr_complete: hci0 urb f650ea00 status 0 count 12<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081616] hci_rx_task: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081618] hci_rx_task: hci0 promisc: 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081621] hci_send_to_sock: hdev da350800 len 12<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081629] hci_rx_task: hci0 event packet<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081631] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081633] hci_cmd_complete_evt: hci0 ev->opcode 0x1009<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081635] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081638] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081640] hci_cmd_complete_evt: hci0 &ev->opcode-2 0xa<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081642] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081644] hci_cmd_complete_evt: hci0 &ev->opcode 0x9<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081646] hci_cmd_complete_evt: hci0 &ev->opcode+1 0x10<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081648] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081650] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x36<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081652] hci_cmd_complete_evt: hci0 &ev->opcode+4 0xffffff93<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081655] hci_cc_read_bd_addr: hci0 status 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081658] hci_req_complete: hci0 command 0x1009 result 0x00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081660] hci_cmd_complete_evt: hci0 opcode 0x1009 (recognized if not twice)<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081662] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081665] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081668] hci_send_frame: hci0 type 1 len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081671] hci_send_to_sock: hdev da350800 len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081673] btusb_send_frame: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081691] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081697] hci_sock_create: sock f0a06e00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081703] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081705] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.081708] hci_sock_release: sock f0a06e00 sk f151d000<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.082608] btusb_tx_complete: hci0 urb eef4cc00 status 0 count 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083606] btusb_intr_complete: hci0 urb f650ea00 status 0 count 9<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083614] hci_rx_task: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083616] hci_rx_task: hci0 promisc: 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083619] hci_send_to_sock: hdev da350800 len 9<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083625] hci_rx_task: hci0 event packet<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083628] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083630] hci_cmd_complete_evt: hci0 ev->opcode 0xc23<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083632] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083634] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083636] hci_cmd_complete_evt: hci0 &ev->opcode-2 0x7<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083638] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083640] hci_cmd_complete_evt: hci0 &ev->opcode 0x23<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083646] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083646] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083648] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083652] hci_sock_create: sock f0a8ae00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083653] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083655] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083659] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083661] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083662] hci_cc_read_class_of_dev: hci0 status 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083666] hci_sock_release: sock f0a8ae00 sk f1712800<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083667] hci_cc_read_class_of_dev: hci0 class 0x000000<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083669] hci_cmd_complete_evt: hci0 opcode 0xc23 (recognized if not twice)<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083672] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083674] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083677] hci_send_frame: hci0 type 1 len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083680] hci_send_to_sock: hdev da350800 len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.083683] btusb_send_frame: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.084610] btusb_tx_complete: hci0 urb eef4cc00 status 0 count 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.086608] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.088609] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.090608] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.092609] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.094609] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.096608] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.098607] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.100609] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.102608] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.104610] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.106607] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.108610] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.110609] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.112611] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.114615] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116610] btusb_intr_complete: hci0 urb f650ea00 status 0 count 14<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116619] hci_rx_task: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116621] hci_rx_task: hci0 promisc: 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116624] hci_send_to_sock: hdev da350800 len 254<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116636] hci_rx_task: hci0 event packet<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116639] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116641] hci_cmd_complete_evt: hci0 ev->opcode 0xc14<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116643] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116645] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116648] hci_cmd_complete_evt: hci0 &ev->opcode-2 0xfffffffc<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116650] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116652] hci_cmd_complete_evt: hci0 &ev->opcode 0x14<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116654] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116656] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116659] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x6a<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116661] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x6b<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116663] hci_cc_read_local_name: hci0 status 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116666] hci_cmd_complete_evt: hci0 opcode 0xc14 (recognized if not twice)<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116669] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116673] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116677] hci_send_frame: hci0 type 1 len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116680] hci_send_to_sock: hdev da350800 len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116684] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116687] btusb_send_frame: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116697] hci_sock_create: sock f0a8ae00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116709] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116711] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.116717] hci_sock_release: sock f0a8ae00 sk f1712800<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.117609] btusb_tx_complete: hci0 urb eef4cc00 status 0 count 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118608] btusb_intr_complete: hci0 urb f650ea00 status 0 count 8<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118618] hci_rx_task: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118620] hci_rx_task: hci0 promisc: 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118623] hci_send_to_sock: hdev da350800 len 8<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118633] hci_rx_task: hci0 event packet<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118635] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118637] hci_cmd_complete_evt: hci0 ev->opcode 0xc25<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118640] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118642] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118644] hci_cmd_complete_evt: hci0 &ev->opcode-2 0x6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118646] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118648] hci_cmd_complete_evt: hci0 &ev->opcode 0x25<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118653] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118653] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118656] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118658] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x60<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118661] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118663] hci_cc_read_voice_setting: hci0 status 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118666] hci_cmd_complete_evt: hci0 opcode 0xc25 (recognized if not twice)<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118668] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118671] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118675] hci_send_frame: hci0 type 1 len 4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118679] hci_sock_create: sock f0a8ae00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118681] hci_send_to_sock: hdev da350800 len 4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118685] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118686] btusb_send_frame: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118690] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.118694] hci_sock_release: sock f0a8ae00 sk f1712800<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.119608] btusb_tx_complete: hci0 urb eef4cc00 status 0 count 4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120609] btusb_intr_complete: hci0 urb f650ea00 status 0 count 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120618] hci_rx_task: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120620] hci_rx_task: hci0 promisc: 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120623] hci_send_to_sock: hdev da350800 len 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120631] hci_rx_task: hci0 event packet<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120633] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120635] hci_cmd_complete_evt: hci0 ev->opcode 0xc05<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120637] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120639] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120642] hci_cmd_complete_evt: hci0 &ev->opcode-2 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120644] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120646] hci_cmd_complete_evt: hci0 &ev->opcode 0x5<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120648] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120650] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120652] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120654] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120656] hci_cmd_complete_evt: hci0 default (non-recognized) opcode 0xc05<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120659] hci_cmd_complete_evt: hci0 opcode 0xc05 (recognized if not twice)<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120661] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120664] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120667] hci_send_frame: hci0 type 1 len 5<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120670] hci_send_to_sock: hdev da350800 len 5<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120673] btusb_send_frame: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120695] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120701] hci_sock_create: sock f0a06e00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120707] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120709] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.120713] hci_sock_release: sock f0a06e00 sk f151d600<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.121610] btusb_tx_complete: hci0 urb eef4cc00 status 0 count 5<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122608] btusb_intr_complete: hci0 urb f650ea00 status 0 count 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122615] hci_rx_task: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122618] hci_rx_task: hci0 promisc: 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122620] hci_send_to_sock: hdev da350800 len 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122627] hci_rx_task: hci0 event packet<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122629] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122632] hci_cmd_complete_evt: hci0 ev->opcode 0xc18<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122634] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122636] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122638] hci_cmd_complete_evt: hci0 &ev->opcode-2 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122640] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122642] hci_cmd_complete_evt: hci0 &ev->opcode 0x18<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122646] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122648] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122650] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122654] hci_sock_create: sock f0a8ae00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122655] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x2<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122657] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122661] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122663] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122664] hci_cmd_complete_evt: hci0 default (non-recognized) opcode 0xc18<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122668] hci_sock_release: sock f0a8ae00 sk f1712800<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122669] hci_cmd_complete_evt: hci0 opcode 0xc18 (recognized if not twice)<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122672] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122674] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122677] hci_send_frame: hci0 type 1 len 5<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122681] hci_send_to_sock: hdev da350800 len 5<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.122683] btusb_send_frame: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.123607] btusb_tx_complete: hci0 urb eef4cc00 status 0 count 5<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124611] btusb_intr_complete: hci0 urb f650ea00 status 0 count 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124618] hci_rx_task: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124621] hci_rx_task: hci0 promisc: 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124623] hci_send_to_sock: hdev da350800 len 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124631] hci_rx_task: hci0 event packet<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124633] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124635] hci_cmd_complete_evt: hci0 ev->opcode 0xc16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124637] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124639] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124641] hci_cmd_complete_evt: hci0 &ev->opcode-2 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124643] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124645] hci_cmd_complete_evt: hci0 &ev->opcode 0x16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124648] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124650] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124652] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x2<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124654] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124656] hci_cc_write_ca_timeout: hci0 status 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124659] hci_req_complete: hci0 command 0x0c16 result 0x00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124667] hci_cmd_complete_evt: hci0 opcode 0xc16 (recognized if not twice)<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124670] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124673] __hci_request: hci0 end: err 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124677] hci_sock_dev_event: hdev hci0 event 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124682] hci_send_to_sock: hdev   (null) len 8<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124684] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124690] hci_sock_create: sock f0a06e00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124697] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124699] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124703] hci_sock_release: sock f0a06e00 sk f151d600<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124705] hci_sock_release: sock f0a8ac40 sk f1713000<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124720] hci_sock_recvmsg: sock ec89ea80, sk f156d600<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124764] hci_sock_create: sock f0a06e00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124769] hci_sock_ioctl: cmd 800448d3 arg bf922568<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124771] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124774] hci_sock_release: sock f0a06e00 sk f151d600<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124782] hci_sock_sendmsg: sock ec89f6c0 sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124789] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124792] hci_send_frame: hci0 type 1 len 5<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124795] hci_send_to_sock: hdev da350800 len 5<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124798] btusb_send_frame: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124803] hci_sock_sendmsg: sock ec89f6c0 sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124807] hci_cmd_task: hci0 cmd 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124886] hci_sock_sendmsg: sock ec89f6c0 sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124890] hci_cmd_task: hci0 cmd 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124893] hci_sock_sendmsg: sock ec89f6c0 sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124897] hci_cmd_task: hci0 cmd 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124900] hci_sock_sendmsg: sock ec89f6c0 sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124904] hci_cmd_task: hci0 cmd 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124941] hci_sock_sendmsg: sock ec89f6c0 sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.124946] hci_cmd_task: hci0 cmd 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.125066] hci_sock_sendmsg: sock ec89f6c0 sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.125071] hci_cmd_task: hci0 cmd 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.125086] hci_sock_sendmsg: sock ec89f6c0 sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.125090] hci_cmd_task: hci0 cmd 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.125612] btusb_tx_complete: hci0 urb eef4cc00 status 0 count 5<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126610] btusb_intr_complete: hci0 urb f650ea00 status 0 count 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126618] hci_rx_task: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126621] hci_rx_task: hci0 promisc: 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126623] hci_send_to_sock: hdev da350800 len 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126630] hci_rx_task: hci0 event packet<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126632] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126635] hci_cmd_complete_evt: hci0 ev->opcode 0xc18<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126637] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126639] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126641] hci_cmd_complete_evt: hci0 &ev->opcode-2 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126643] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126645] hci_cmd_complete_evt: hci0 &ev->opcode 0x18<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126647] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126650] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126652] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126654] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126656] hci_cmd_complete_evt: hci0 default (non-recognized) opcode 0xc18<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126658] hci_cmd_complete_evt: hci0 opcode 0xc18 (recognized if not twice)<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126661] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126664] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126667] hci_send_frame: hci0 type 1 len 10<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126670] hci_send_to_sock: hdev da350800 len 10<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126672] btusb_send_frame: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126690] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126696] hci_sock_create: sock f0a06e00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126703] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126706] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.126709] hci_sock_release: sock f0a06e00 sk f151c800<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.127608] btusb_tx_complete: hci0 urb eef4cc00 status 0 count 10<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128612] btusb_intr_complete: hci0 urb f650ea00 status 0 count 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128623] hci_rx_task: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128627] hci_rx_task: hci0 promisc: 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128631] hci_send_to_sock: hdev da350800 len 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128639] hci_rx_task: hci0 event packet<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128642] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128646] hci_cmd_complete_evt: hci0 ev->opcode 0xc0d<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128649] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128653] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128656] hci_cmd_complete_evt: hci0 &ev->opcode-2 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128660] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128663] hci_cmd_complete_evt: hci0 &ev->opcode 0xd<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128667] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128671] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128674] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x2<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128678] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128682] hci_cmd_complete_evt: hci0 default (non-recognized) opcode 0xc0d<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128685] hci_cmd_complete_evt: hci0 opcode 0xc0d (recognized if not twice)<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128689] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128693] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128698] hci_send_frame: hci0 type 1 len 11<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128702] hci_send_to_sock: hdev da350800 len 11<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128706] btusb_send_frame: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128729] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128737] hci_sock_create: sock f0a06e00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128745] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128748] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.128753] hci_sock_release: sock f0a06e00 sk f151c800<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.129612] btusb_tx_complete: hci0 urb eef4cc00 status 0 count 11<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130610] btusb_intr_complete: hci0 urb f650ea00 status 0 count 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130620] hci_rx_task: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130623] hci_rx_task: hci0 promisc: 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130625] hci_send_to_sock: hdev da350800 len 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130633] hci_rx_task: hci0 event packet<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130636] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130638] hci_cmd_complete_evt: hci0 ev->opcode 0xc01<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130640] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130642] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130644] hci_cmd_complete_evt: hci0 &ev->opcode-2 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130646] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130648] hci_cmd_complete_evt: hci0 &ev->opcode 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130650] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130652] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130655] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x2<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130657] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130659] hci_cmd_complete_evt: hci0 default (non-recognized) opcode 0xc01<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130661] hci_cmd_complete_evt: hci0 opcode 0xc01 (recognized if not twice)<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130664] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130666] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130670] hci_send_frame: hci0 type 1 len 4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130673] hci_send_to_sock: hdev da350800 len 4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130676] btusb_send_frame: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130697] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130704] hci_sock_create: sock f0a06e00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130711] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130713] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.130717] hci_sock_release: sock f0a06e00 sk f151c800<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.131609] btusb_tx_complete: hci0 urb eef4cc00 status 0 count 4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132610] btusb_intr_complete: hci0 urb f650ea00 status 0 count 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132618] hci_rx_task: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132621] hci_rx_task: hci0 promisc: 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132623] hci_send_to_sock: hdev da350800 len 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132629] hci_rx_task: hci0 event packet<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132632] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132634] hci_cmd_complete_evt: hci0 ev->opcode 0xc45<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132636] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132638] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132640] hci_cmd_complete_evt: hci0 &ev->opcode-2 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132642] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132644] hci_cmd_complete_evt: hci0 &ev->opcode 0x45<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132646] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132649] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132651] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x2<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132653] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132655] hci_cmd_complete_evt: hci0 default (non-recognized) opcode 0xc45<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132658] hci_cmd_complete_evt: hci0 opcode 0xc45 (recognized if not twice)<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132660] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132663] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132666] hci_send_frame: hci0 type 1 len 5<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132670] hci_send_to_sock: hdev da350800 len 5<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132672] btusb_send_frame: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132689] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132695] hci_sock_create: sock f0a06e00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132700] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132703] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.132706] hci_sock_release: sock f0a06e00 sk f151c800<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.133609] btusb_tx_complete: hci0 urb eef4cc00 status 0 count 5<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134609] btusb_intr_complete: hci0 urb f650ea00 status 0 count 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134617] hci_rx_task: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134619] hci_rx_task: hci0 promisc: 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134622] hci_send_to_sock: hdev da350800 len 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134630] hci_rx_task: hci0 event packet<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134632] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134634] hci_cmd_complete_evt: hci0 ev->opcode 0x80f<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134637] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134639] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134641] hci_cmd_complete_evt: hci0 &ev->opcode-2 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134643] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134645] hci_cmd_complete_evt: hci0 &ev->opcode 0xf<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134647] hci_cmd_complete_evt: hci0 &ev->opcode+1 0x8<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134652] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134653] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134655] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x2<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134659] hci_sock_create: sock f0a8ac40<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134660] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134663] hci_cc_write_def_link_policy: hci0 status 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134667] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134669] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134671] hci_sent_cmd_data: hci0 opcode 0x80f<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134674] hci_sock_release: sock f0a8ac40 sk f1713000<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134676] hci_req_complete: hci0 command 0x080f result 0x00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134678] hci_cmd_complete_evt: hci0 opcode 0x80f (recognized if not twice)<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134681] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134684] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134687] hci_send_frame: hci0 type 1 len 251<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134690] hci_send_to_sock: hdev da350800 len 251<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.134693] btusb_send_frame: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.135608] btusb_tx_complete: hci0 urb eef4cc00 status 0 count 251<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137610] btusb_intr_complete: hci0 urb f650ea00 status 0 count 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137618] hci_rx_task: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137621] hci_rx_task: hci0 promisc: 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137623] hci_send_to_sock: hdev da350800 len 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137631] hci_rx_task: hci0 event packet<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137633] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137636] hci_cmd_complete_evt: hci0 ev->opcode 0xc13<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137638] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137640] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137642] hci_cmd_complete_evt: hci0 &ev->opcode-2 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137644] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137646] hci_cmd_complete_evt: hci0 &ev->opcode 0x13<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137649] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137651] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137653] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x2<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137655] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137657] hci_cc_write_local_name: hci0 status 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137659] hci_sent_cmd_data: hci0 opcode 0xc13<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137662] hci_cmd_complete_evt: hci0 opcode 0xc13 (recognized if not twice)<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137664] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137667] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137670] hci_send_frame: hci0 type 1 len 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137673] hci_send_to_sock: hdev da350800 len 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137675] btusb_send_frame: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137692] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137697] hci_sock_create: sock f0a06e00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137703] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137705] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137708] hci_sock_release: sock f0a06e00 sk f151c800<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137717] hci_sock_sendmsg: sock ec89f6c0 sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.137723] hci_cmd_task: hci0 cmd 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.138608] btusb_tx_complete: hci0 urb eef4cc00 status 0 count 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139608] btusb_intr_complete: hci0 urb f650ea00 status 0 count 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139616] hci_rx_task: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139618] hci_rx_task: hci0 promisc: 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139620] hci_send_to_sock: hdev da350800 len 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139627] hci_rx_task: hci0 event packet<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139629] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139631] hci_cmd_complete_evt: hci0 ev->opcode 0xc24<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139633] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139635] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139637] hci_cmd_complete_evt: hci0 &ev->opcode-2 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139640] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139642] hci_cmd_complete_evt: hci0 &ev->opcode 0x24<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139647] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139648] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139650] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139654] hci_sock_create: sock f0a8ac40<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139654] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x2<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139656] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139661] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139663] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139663] hci_cc_write_class_of_dev: hci0 status 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139668] hci_sock_release: sock f0a8ac40 sk f1713000<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139669] hci_sent_cmd_data: hci0 opcode 0xc24<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139671] hci_cmd_complete_evt: hci0 opcode 0xc24 (recognized if not twice)<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139673] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139676] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139679] hci_send_frame: hci0 type 1 len 4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139682] hci_send_to_sock: hdev da350800 len 4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.139685] btusb_send_frame: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.140611] btusb_tx_complete: hci0 urb eef4cc00 status 0 count 4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141609] btusb_intr_complete: hci0 urb f650ea00 status 0 count 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141618] hci_rx_task: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141621] hci_rx_task: hci0 promisc: 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141623] hci_send_to_sock: hdev da350800 len 6<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141630] hci_rx_task: hci0 event packet<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141633] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141635] hci_cmd_complete_evt: hci0 ev->opcode 0xc1a<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141637] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141639] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141641] hci_cmd_complete_evt: hci0 &ev->opcode-2 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141643] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141645] hci_cmd_complete_evt: hci0 &ev->opcode 0x1a<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141647] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141649] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141652] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x2<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141654] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141656] hci_cc_write_scan_enable: hci0 status 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141658] hci_sent_cmd_data: hci0 opcode 0xc1a<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141661] hci_req_complete: hci0 command 0x0c1a result 0x00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141663] hci_cmd_complete_evt: hci0 opcode 0xc1a (recognized if not twice)<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141666] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141668] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141671] hci_send_frame: hci0 type 1 len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141674] hci_send_to_sock: hdev da350800 len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141677] btusb_send_frame: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141693] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141699] hci_sock_create: sock f0a06e00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141705] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141707] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141711] hci_sock_release: sock f0a06e00 sk f151c800<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141720] hci_sock_sendmsg: sock ec89f6c0 sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.141725] hci_cmd_task: hci0 cmd 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.142608] btusb_tx_complete: hci0 urb eef4cc00 status 0 count 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.143607] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.145609] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.147608] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.149609] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.151608] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.153611] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.155608] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.157610] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.159608] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.161610] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.163609] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.165610] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.167608] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.169611] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.171610] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173612] btusb_intr_complete: hci0 urb f650ea00 status 0 count 14<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173622] hci_rx_task: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173625] hci_rx_task: hci0 promisc: 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173627] hci_send_to_sock: hdev da350800 len 254<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173638] hci_rx_task: hci0 event packet<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173641] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173643] hci_cmd_complete_evt: hci0 ev->opcode 0xc14<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173646] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173648] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173650] hci_cmd_complete_evt: hci0 &ev->opcode-2 0xfffffffc<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173652] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173654] hci_cmd_complete_evt: hci0 &ev->opcode 0x14<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173656] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173659] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173661] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x6a<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173663] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x6b<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173665] hci_cc_read_local_name: hci0 status 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173668] hci_cmd_complete_evt: hci0 opcode 0xc14 (recognized if not twice)<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173671] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173674] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173678] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173683] hci_send_frame: hci0 type 1 len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173686] hci_send_to_sock: hdev da350800 len 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173690] hci_sock_create: sock f0a8ac40<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173691] btusb_send_frame: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173703] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173706] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.173712] hci_sock_release: sock f0a8ac40 sk f1713000<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.174610] btusb_tx_complete: hci0 urb eef4cc00 status 0 count 3<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175608] btusb_intr_complete: hci0 urb f650ea00 status 0 count 7<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175617] hci_rx_task: hci0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175619] hci_rx_task: hci0 promisc: 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175621] hci_send_to_sock: hdev da350800 len 7<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175630] hci_rx_task: hci0 event packet<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175632] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175634] hci_cmd_complete_evt: hci0 ev->opcode 0xc19<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175637] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175639] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175641] hci_cmd_complete_evt: hci0 &ev->opcode-2 0x5<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175646] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175647] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175651] hci_sock_create: sock f0a8ac40<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175651] hci_cmd_complete_evt: hci0 &ev->opcode 0x19<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175653] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175656] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175658] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x2<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175661] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x2d<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175663] hci_cmd_complete_evt: hci0 default (non-recognized) opcode 0xc19<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175666] hci_cmd_complete_evt: hci0 opcode 0xc19 (recognized if not twice)<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175669] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175676] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175679] hci_dev_get: 0<br />
Sep 20 14:21:21 jkp-hp kernel: [251578.175682] hci_sock_release: sock f0a8ac40 sk f1713000<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.381379] hci_sock_create: sock f0a8ac40<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.381396] hci_sock_ioctl: cmd 800448d3 arg aea240<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.381399] hci_dev_get: 0<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.381418] hci_sock_create: sock f0a8ae00<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.381427] hci_sock_bind: sock f0a8ae00 sk f64d1800<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.381429] hci_dev_get: 0<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.381440] hci_sock_setsockopt: sk f64d1800, opt 2<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.381445] hci_sock_sendmsg: sock f0a8ae00 sk f64d1800<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.381455] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.381460] hci_send_frame: hci0 type 1 len 3<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.381463] hci_send_to_sock: hdev da350800 len 3<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.381466] btusb_send_frame: hci0<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.382684] btusb_tx_complete: hci0 urb f6cd8880 status 0 count 3<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383681] btusb_intr_complete: hci0 urb f650ea00 status 0 count 14<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383693] hci_rx_task: hci0<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383695] hci_rx_task: hci0 promisc: 0x2<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383698] hci_send_to_sock: hdev da350800 len 14<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383716] hci_rx_task: hci0 event packet<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383719] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383721] hci_cmd_complete_evt: hci0 ev->opcode 0x1001<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383724] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383726] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383728] hci_cmd_complete_evt: hci0 &ev->opcode-2 0xc<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383730] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383732] hci_cmd_complete_evt: hci0 &ev->opcode 0x1<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383734] hci_cmd_complete_evt: hci0 &ev->opcode+1 0x10<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383736] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383738] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x3<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383740] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x29<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383743] hci_cc_read_local_version: hci0 status 0x0<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383746] hci_cc_read_local_version: hci0 manufacturer 15 hci ver 3:8489<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383748] hci_cmd_complete_evt: hci0 opcode 0x1001 (recognized if not twice)<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383751] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383755] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383766] hci_sock_create: sock f0a8a380<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383774] hci_sock_recvmsg: sock f0a8ae00, sk f64d1800<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383778] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383781] hci_dev_get: 0<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383786] hci_sock_release: sock f0a8a380 sk f1f97800<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383790] hci_sock_setsockopt: sk f64d1800, opt 2<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383955] hci_sock_release: sock f0a8ae00 sk f64d1800<br />
Sep 20 14:21:24 jkp-hp kernel: [251581.383964] hci_sock_release: sock f0a8ac40 sk f64d1400<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.601529] hci_sock_create: sock f0a8a380<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.601550] hci_sock_ioctl: cmd 800448d3 arg a70240<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.601553] hci_dev_get: 0<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.601574] hci_sock_create: sock f0a8a700<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.601583] hci_sock_bind: sock f0a8a700 sk f14f7400<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.601586] hci_dev_get: 0<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.601597] hci_sock_setsockopt: sk f14f7400, opt 2<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.601602] hci_sock_sendmsg: sock f0a8a700 sk f14f7400<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.601613] hci_cmd_task: hci0 cmd 1<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.601618] hci_send_frame: hci0 type 1 len 3<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.601621] hci_send_to_sock: hdev da350800 len 3<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.601624] btusb_send_frame: hci0<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.603383] btusb_tx_complete: hci0 urb f29b8180 status 0 count 3<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.604384] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.606378] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.608379] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.610380] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.612380] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.614378] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.616380] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.618378] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.620380] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.622378] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.624380] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.626378] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.628380] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.630379] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.632380] btusb_intr_complete: hci0 urb f650ea00 status 0 count 16<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634379] btusb_intr_complete: hci0 urb f650ea00 status 0 count 14<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634388] hci_rx_task: hci0<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634390] hci_rx_task: hci0 promisc: 0x2<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634393] hci_send_to_sock: hdev da350800 len 254<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634411] hci_rx_task: hci0 event packet<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634415] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634417] hci_cmd_complete_evt: hci0 ev->opcode 0xc14<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634419] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x4<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634422] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634424] hci_cmd_complete_evt: hci0 &ev->opcode-2 0xfffffffc<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634426] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634428] hci_cmd_complete_evt: hci0 &ev->opcode 0x14<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634430] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634432] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634434] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x6a<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634436] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x6b<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634439] hci_cc_read_local_name: hci0 status 0x0<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634442] hci_cmd_complete_evt: hci0 opcode 0xc14 (recognized if not twice)<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634445] hci_event_packet: hci0 event 0xe<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634456] hci_sock_recvmsg: sock ec89f6c0, sk f153fe00<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634468] hci_sock_create: sock f0a8a540<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634477] hci_sock_ioctl: cmd 800448d3 arg bf922964<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634480] hci_dev_get: 0<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634484] hci_sock_release: sock f0a8a540 sk f14f6200<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634530] hci_sock_recvmsg: sock f0a8a700, sk f14f7400<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634546] hci_sock_setsockopt: sk f14f7400, opt 2<br />
Sep 20 14:23:28 jkp-hp kernel: [251705.634641] hci_sock_release: sock f0a8a700 sk f14f7400<br />
 

·
Registered
Joined
·
130 Posts
Discussion Starter · #2 ·
Here's a working "hciconfig hci1 name" output from the laptop with the same dongle which was used in the tablet test. This is from kernel 3.0.3, but there isn't that much difference in bluetooth code in this kernel either. This seems much cleaner that the previous one from 2.6.38, that probably contained switching BT on, I think there may be an inactivity timeout which caused the device to be switched off and the extra stuff in last message from 2.6.38 may have been switching hci0 back on.

Code:
<br />
Sep 20 19:38:33 jkp-hp kernel: [ 8872.874450] hci_sock_create: sock e8bc7680<br />
Sep 20 19:38:33 jkp-hp kernel: [ 8872.874469] hci_sock_ioctl: cmd 800448d3 arg b78a4240<br />
Sep 20 19:38:33 jkp-hp kernel: [ 8872.874472] hci_dev_get: 1<br />
Sep 20 19:38:33 jkp-hp kernel: [ 8872.874475] hci_del_off_timer: hci1<br />
Sep 20 19:38:33 jkp-hp kernel: [ 8872.874495] hci_sock_create: sock e8bc6000<br />
Sep 20 19:38:33 jkp-hp kernel: [ 8872.874504] hci_sock_bind: sock e8bc6000 sk ef0f3a00<br />
Sep 20 19:38:33 jkp-hp kernel: [ 8872.874507] hci_dev_get: 1<br />
Sep 20 19:38:33 jkp-hp kernel: [ 8872.874516] hci_sock_setsockopt: sk ef0f3a00, opt 2<br />
Sep 20 19:38:33 jkp-hp kernel: [ 8872.874521] hci_sock_sendmsg: sock e8bc6000 sk ef0f3a00<br />
Sep 20 19:38:33 jkp-hp kernel: [ 8872.874529] hci_cmd_task: hci1 cmd 1<br />
Sep 20 19:38:33 jkp-hp kernel: [ 8872.874534] hci_send_frame: hci1 type 1 len 3<br />
Sep 20 19:38:33 jkp-hp kernel: [ 8872.874537] hci_send_to_sock: hdev e81b8000 len 3<br />
Sep 20 19:38:33 jkp-hp kernel: [ 8872.874541] btusb_send_frame: hci1<br />
Sep 20 19:38:33 jkp-hp kernel: [ 8872.877110] btusb_tx_complete: hci1 urb e8147280 status 0 count 3<br />
Sep 20 19:38:33 jkp-hp kernel: [ 8872.880103] btusb_intr_complete: hci1 urb e8147d00 status 0 count 16<br />
Sep 20 19:38:33 jkp-hp kernel: [ 8872.882104] btusb_intr_complete: hci1 urb e8147d00 status 0 count 16<br />
Sep 20 19:38:33 jkp-hp kernel: [ 8872.884097] btusb_intr_complete: hci1 urb e8147d00 status 0 count 16<br />
Sep 20 19:38:33 jkp-hp kernel: [ 8872.886104] btusb_intr_complete: hci1 urb e8147d00 status 0 count 16<br />
Sep 20 19:38:33 jkp-hp kernel: [ 8872.888098] btusb_intr_complete: hci1 urb e8147d00 status 0 count 16<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.890105] btusb_intr_complete: hci1 urb e8147d00 status 0 count 16<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.892100] btusb_intr_complete: hci1 urb e8147d00 status 0 count 16<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.894104] btusb_intr_complete: hci1 urb e8147d00 status 0 count 16<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.896097] btusb_intr_complete: hci1 urb e8147d00 status 0 count 16<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.898105] btusb_intr_complete: hci1 urb e8147d00 status 0 count 16<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.900098] btusb_intr_complete: hci1 urb e8147d00 status 0 count 16<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.902097] btusb_intr_complete: hci1 urb e8147d00 status 0 count 16<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.904106] btusb_intr_complete: hci1 urb e8147d00 status 0 count 16<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.906100] btusb_intr_complete: hci1 urb e8147d00 status 0 count 16<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.908101] btusb_intr_complete: hci1 urb e8147d00 status 0 count 16<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910092] btusb_intr_complete: hci1 urb e8147d00 status 0 count 14<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910101] hci_rx_task: hci1<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910103] hci_rx_task: hci1 promisc: 0x2<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910106] hci_send_to_sock: hdev e81b8000 len 254<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910120] hci_rx_task: hci1 event packet<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910123] hci_cmd_complete_evt: hci1 ev->ncmd 0x1<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910125] hci_cmd_complete_evt: hci1 ev->opcode 0xc14<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910128] hci_cmd_complete_evt: hci1 &ev->opcode-4 0x4<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910130] hci_cmd_complete_evt: hci1 &ev->opcode-3 0xe<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910132] hci_cmd_complete_evt: hci1 &ev->opcode-2 0xfffffffc<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910134] hci_cmd_complete_evt: hci1 &ev->opcode-1 0x1<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910136] hci_cmd_complete_evt: hci1 &ev->opcode 0x14<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910139] hci_cmd_complete_evt: hci1 &ev->opcode+1 0xc<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910141] hci_cmd_complete_evt: hci1 &ev->opcode+2 0x0<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910143] hci_cmd_complete_evt: hci1 &ev->opcode+3 0x6a<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910145] hci_cmd_complete_evt: hci1 &ev->opcode+4 0x6b<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910148] hci_cc_read_local_name: hci1 status 0x0<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910153] hci_sock_recvmsg: sock e8bc6000, sk ef0f3a00<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910156] hci_cmd_complete_evt: hci1 opcode 0xc14 (recognized if not twice)<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910162] hci_event_packet: hci1 event 0xe<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910182] hci_sock_setsockopt: sk ef0f3a00, opt 2<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910306] hci_sock_release: sock e8bc6000 sk ef0f3a00<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910330] hci_sock_release: sock e8bc7680 sk f348e800<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910513] hci_sock_recvmsg: sock e8bc8000, sk ef14e600<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910523] hci_sock_create: sock e8bc7680<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910536] hci_sock_ioctl: cmd 800448d3 arg bf9f8034<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910539] hci_dev_get: 1<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910542] hci_del_off_timer: hci1<br />
Sep 20 19:38:34 jkp-hp kernel: [ 8872.910546] hci_sock_release: sock e8bc7680 sk ef0f3a00<br />
 

·
Registered
Joined
·
130 Posts
Some more log output showing that the data sent appears to be the same on both the tablet and the laptop:

tablet:
Code:
<br />
<7>[30041.791217] hci_sock_setsockopt: sk d20b8e00, opt 2<br />
<7>[30041.791271] hci_sock_sendmsg: sock c17f6c80 sk d20b8e00<br />
<7>[30041.791325] hci_cmd_task: hci0 cmd 1<br />
<7>[30041.791350] hci_send_frame: hci0 type 1 len 3<br />
<7>[30041.791368] hci_send_to_sock: hdev raw c5a3b400 len 3<br />
<7>[30041.791386] hci_send_frame: hci0 head byte 0: 0x14<br />
<7>[30041.791400] hci_send_frame: hci0 head byte 1: 0xc<br />
<7>[30041.791413] hci_send_frame: hci0 head byte 2: 0x0<br />
<7>[30041.791427] btusb_send_frame: hci0<br />
<7>[30041.791438] btusb_send_frame: hci0 skb data len: 0x0<br />
<7>[30041.791452] btusb_send_frame: hci0 head byte 0: 0x14<br />
<7>[30041.791466] btusb_send_frame: hci0 head byte 1: 0xc<br />
<7>[30041.791479] btusb_send_frame: hci0 head byte 2: 0x0<br />
<7>[30041.793284] btusb_tx_complete: hci0 urb c969a2c0 status 0 count 3<br />
<4>[30041.793443] adb_write<br />
<4>[30041.793485] adb_write<br />
<7>[30041.795137] btusb_intr_complete: hci0 urb c48749c0 status 0 count 10<br />
<7>[25676.435187] hci_rx_task: hci0<br />
<7>[25676.435200] hci_rx_task: hci0 promisc: 0x1<br />
<7>[25676.435214] hci_send_to_sock: hdev raw d20b8800 len 10<br />
<7>[25676.435235] hci_rx_task: hci0 event packet<br />
<7>[25676.435250] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
<7>[25676.435264] hci_cmd_complete_evt: hci0 ev->opcode 0x1401<br />
laptop:

Code:
<br />
Sep 21 08:47:48 jkp-hp kernel: [  795.355852] hci_sock_sendmsg: sock ee3a2780 sk f6271200<br />
Sep 21 08:47:48 jkp-hp kernel: [  795.355860] hci_cmd_task: hci0 cmd 1<br />
Sep 21 08:47:48 jkp-hp kernel: [  795.355865] hci_send_frame: hci0 type 1 len 3<br />
Sep 21 08:47:48 jkp-hp kernel: [  795.355868] hci_send_to_sock: hdev ed014800 len 3<br />
Sep 21 08:47:48 jkp-hp kernel: [  795.355871] hci_send_frame: hci0 head byte 0: 0x14<br />
Sep 21 08:47:48 jkp-hp kernel: [  795.355873] hci_send_frame: hci0 head byte 1: 0xc<br />
Sep 21 08:47:48 jkp-hp kernel: [  795.355875] hci_send_frame: hci0 head byte 2: 0x0<br />
Sep 21 08:47:48 jkp-hp kernel: [  795.355877] btusb_send_frame: hci0 data byte 0: 0x14<br />
Sep 21 08:47:48 jkp-hp kernel: [  795.355879] btusb_send_frame: hci0<br />
Sep 21 08:47:48 jkp-hp kernel: [  795.355881] btusb_send_frame: hci0 skb data len: 0x0<br />
Sep 21 08:47:48 jkp-hp kernel: [  795.355883] btusb_send_frame: hci0 head byte 0: 0x14<br />
Sep 21 08:47:48 jkp-hp kernel: [  795.355885] btusb_send_frame: hci0 head byte 1: 0xc<br />
Sep 21 08:47:48 jkp-hp kernel: [  795.355887] btusb_send_frame: hci0 head byte 2: 0x0<br />
Sep 21 08:47:48 jkp-hp kernel: [  795.355891] btusb_send_frame: hci0 urb f1294a00 status 0 count 0<br />
Sep 21 08:47:48 jkp-hp kernel: [  795.357269] btusb_tx_complete: hci0 urb f1294a00 status 0 count 3<br />
Sep 21 08:47:48 jkp-hp kernel: [  795.358263] btusb_intr_complete: hci0 urb ed0fdb80 status 0 count 16<br />
So, it would seem the same data is sent from btusb_send_frame, but on the tablet the answer which is gotten is different, length of ten instead of 254 (divided into 14 packets of 16 and one packet of 14) on the laptop.

On the tablet, the answer includes a byte of the code of the command - 0x14 for getting the name, and when trying to set the name, the answer contains 0x13 which is also in sent data.

I also booted the laptop with same kernel version which is running on the tablet, to make sure it isn't a shortcoming with the kernel version. hciconfig name & version work on that configuration.
 

·
Registered
Joined
·
130 Posts
Discussion Starter · #4 ·
Hey wait a moment, there's a succesful get name operation in the log when bringing the interface up. So, instead of a general failure of the local commands like get or set name, what's happening seems to be the device goes into some kind of failure mode after it is brought up and after the initial get name op succeeds.

Short log where the get name operation seems to succeed.

Code:
<br />
<7>[  185.852188] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x0<br />
<7>[  185.852203] hci_cc_read_class_of_dev: hci0 status 0x0<br />
<7>[  185.852218] hci_cc_read_class_of_dev: hci0 class 0x000000<br />
<7>[  185.852233] hci_cmd_complete_evt: hci0 opcode 0xc23 (recognized if not twice)<br />
<7>[  185.852249] hci_event_packet: hci0 event 0xe<br />
<7>[  185.852263] hci_cmd_task: hci0 cmd 1<br />
<7>[  185.852279] hci_send_frame: hci0 type 1 len 3<br />
<7>[  185.852291] hci_send_frame: hci0 head byte 0: 0x14<br />
<7>[  185.852304] hci_send_frame: hci0 head byte 1: 0xc<br />
<7>[  185.852317] hci_send_frame: hci0 head byte 2: 0x0<br />
<7>[  185.852329] btusb_send_frame: hci0<br />
<7>[  185.852340] btusb_send_frame: hci0 skb data len: 0x0<br />
<7>[  185.852353] btusb_send_frame: hci0 head byte 0: 0x14<br />
<7>[  185.852366] btusb_send_frame: hci0 head byte 1: 0xc<br />
<7>[  185.852379] btusb_send_frame: hci0 head byte 2: 0x0<br />
<7>[  185.852393] btusb_send_frame: hci0 skb len: 0x3<br />
<7>[  185.873053] btusb_tx_complete: hci0 urb ceae94c0 status 0 count 3<br />
<7>[  185.875979] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.876979] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.877978] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.878978] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.879978] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.880978] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.881978] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.882978] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.883978] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.884978] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.885978] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.886977] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.887977] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.888980] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.889979] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.890976] btusb_intr_complete: hci0 urb c73daac0 status 0 count 14<br />
<7>[  185.891006] hci_rx_task: hci0 arg: d2397800<br />
<7>[  185.891020] hci_rx_task: hci0 hdev: c0835edc<br />
<7>[  185.891031] hci_rx_task: hci0<br />
<7>[  185.891041] hci_rx_task: hci0 event packet<br />
<7>[  185.891054] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
<7>[  185.891068] hci_cmd_complete_evt: hci0 ev->opcode 0xc14<br />
<7>[  185.891081] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x0<br />
<7>[  185.891095] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
<7>[  185.891108] hci_cmd_complete_evt: hci0 &ev->opcode-2 0xfc<br />
<7>[  185.891122] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
<7>[  185.891136] hci_cmd_complete_evt: hci0 &ev->opcode 0x14<br />
<7>[  185.891149] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
<7>[  185.891163] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
<7>[  185.891177] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x43<br />
<7>[  185.891190] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x53<br />
<7>[  185.891206] hci_cc_read_local_name: hci0 status 0x0<br />
<7>[  185.891221] hci_cmd_complete_evt: hci0 opcode 0xc14 (recognized if not twice)<br />
<7>[  185.891238] hci_event_packet: hci0 event 0xe<br />
<7>[  185.891253] hci_cmd_task: hci0 cmd 1<br />
longer log:

Code:
<br />
<7>[  185.663159] hci_sock_create: sock d288c6c0<br />
<7>[  185.663222] hci_sock_ioctl: cmd 800448d3 arg 16234<br />
<7>[  185.663240] hci_dev_get: 0<br />
<7>[  185.663277] hci_sock_ioctl: cmd 400448c9 arg 0<br />
<7>[  185.663293] hci_dev_get: 0<br />
<7>[  185.663306] hci_dev_open: hci0 d2397800<br />
<7>[  185.663320] btusb_open: hci0<br />
<7>[  185.663332] btusb_submit_intr_urb: hci0<br />
<7>[  185.663349] btusb_submit_intr_urb: hci0, size: 16<br />
<6>[  185.663379] DWC_OTG: dwc_otg_hcd_qh_init tt->hub null!<br />
<7>[  185.665696] btusb_submit_bulk_urb: hci0<br />
<6>[  185.665726] DWC_OTG: dwc_otg_hcd_qh_init tt->hub null!<br />
<7>[  185.670836] btusb_intr_complete: hci0 urb c73daac0 status 0 count 6<br />
<7>[  185.670952] btusb_submit_bulk_urb: hci0<br />
<7>[  185.670975] __hci_request: hci0 start<br />
<7>[  185.670990] hci_init_req: hci0 0<br />
<7>[  185.671005] hci_send_cmd: hci0 opcode 0xc03 plen 0<br />
<7>[  185.671021] hci_send_cmd: skb len 3<br />
<7>[  185.671042] hci_send_cmd: hci0 opcode 0x1003 plen 0<br />
<7>[  185.671069] hci_cmd_task: hci0 cmd 1<br />
<7>[  185.671088] hci_send_frame: hci0 type 1 len 3<br />
<7>[  185.671102] hci_send_frame: hci0 head byte 0: 0x3<br />
<7>[  185.671114] hci_send_frame: hci0 head byte 1: 0xc<br />
<7>[  185.671128] hci_send_frame: hci0 head byte 2: 0x0<br />
<7>[  185.671140] btusb_send_frame: hci0<br />
<7>[  185.671152] btusb_send_frame: hci0 skb data len: 0x0<br />
<7>[  185.671166] btusb_send_frame: hci0 head byte 0: 0x3<br />
<7>[  185.671179] btusb_send_frame: hci0 head byte 1: 0xc<br />
<7>[  185.671192] btusb_send_frame: hci0 head byte 2: 0x0<br />
<7>[  185.671207] btusb_send_frame: hci0 skb len: 0x3<br />
<7>[  185.671239] hci_send_cmd: skb len 3<br />
<7>[  185.671257] hci_send_cmd: hci0 opcode 0x1001 plen 0<br />
<7>[  185.671276] hci_cmd_task: hci0 cmd 0<br />
<7>[  185.671294] hci_send_cmd: skb len 3<br />
<7>[  185.671311] hci_send_cmd: hci0 opcode 0x1005 plen 0<br />
<7>[  185.671328] hci_cmd_task: hci0 cmd 0<br />
<7>[  185.671356] hci_send_cmd: skb len 3<br />
<7>[  185.671373] hci_send_cmd: hci0 opcode 0x1009 plen 0<br />
<7>[  185.671390] hci_cmd_task: hci0 cmd 0<br />
<7>[  185.671408] hci_send_cmd: skb len 3<br />
<7>[  185.671425] hci_send_cmd: hci0 opcode 0xc23 plen 0<br />
<7>[  185.671442] hci_cmd_task: hci0 cmd 0<br />
<7>[  185.671465] hci_send_cmd: skb len 3<br />
<7>[  185.671483] hci_send_cmd: hci0 opcode 0xc14 plen 0<br />
<7>[  185.671500] hci_cmd_task: hci0 cmd 0<br />
<7>[  185.671518] hci_send_cmd: skb len 3<br />
<7>[  185.671535] hci_send_cmd: hci0 opcode 0xc25 plen 0<br />
<7>[  185.671552] hci_cmd_task: hci0 cmd 0<br />
<7>[  185.671570] hci_send_cmd: skb len 3<br />
<7>[  185.671586] hci_send_cmd: hci0 opcode 0xc05 plen 1<br />
<7>[  185.671604] hci_cmd_task: hci0 cmd 0<br />
<7>[  185.671622] hci_send_cmd: skb len 4<br />
<7>[  185.671639] hci_send_cmd: hci0 opcode 0xc18 plen 2<br />
<7>[  185.671656] hci_cmd_task: hci0 cmd 0<br />
<7>[  185.671674] hci_send_cmd: skb len 5<br />
<7>[  185.671690] hci_send_cmd: hci0 opcode 0xc16 plen 2<br />
<7>[  185.671708] hci_cmd_task: hci0 cmd 0<br />
<7>[  185.671725] hci_send_cmd: skb len 5<br />
<7>[  185.671747] hci_cmd_task: hci0 cmd 0<br />
<7>[  185.672978] btusb_tx_complete: hci0 urb ceae94c0 status 0 count 3<br />
<7>[  185.824977] btusb_intr_complete: hci0 urb c73daac0 status 0 count 6<br />
<7>[  185.825018] hci_rx_task: hci0 arg: d2397800<br />
<7>[  185.825032] hci_rx_task: hci0 hdev: c0835edc<br />
<7>[  185.825044] hci_rx_task: hci0<br />
<7>[  185.825055] hci_rx_task: hci0 event packet<br />
<7>[  185.825070] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
<7>[  185.825084] hci_cmd_complete_evt: hci0 ev->opcode 0xc03<br />
<7>[  185.825097] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x0<br />
<7>[  185.825111] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
<7>[  185.825125] hci_cmd_complete_evt: hci0 &ev->opcode-2 0x4<br />
<7>[  185.825139] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
<7>[  185.825153] hci_cmd_complete_evt: hci0 &ev->opcode 0x3<br />
<7>[  185.825166] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
<7>[  185.825180] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
<7>[  185.825194] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x0<br />
<7>[  185.825208] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x0<br />
<7>[  185.825223] hci_cc_reset: hci0 status 0x0<br />
<7>[  185.825235] hci_req_complete: hci0 result 0x00<br />
<7>[  185.825253] hci_cmd_complete_evt: hci0 opcode 0xc03 (recognized if not twice)<br />
<7>[  185.825271] hci_event_packet: hci0 event 0xe<br />
<7>[  185.825289] hci_cmd_task: hci0 cmd 1<br />
<7>[  185.825306] hci_send_frame: hci0 type 1 len 3<br />
<7>[  185.825320] hci_send_frame: hci0 head byte 0: 0x3<br />
<7>[  185.825333] hci_send_frame: hci0 head byte 1: 0x10<br />
<7>[  185.825346] hci_send_frame: hci0 head byte 2: 0x0<br />
<7>[  185.825358] btusb_send_frame: hci0<br />
<7>[  185.825369] btusb_send_frame: hci0 skb data len: 0x0<br />
<7>[  185.825382] btusb_send_frame: hci0 head byte 0: 0x3<br />
<7>[  185.825396] btusb_send_frame: hci0 head byte 1: 0x10<br />
<7>[  185.825409] btusb_send_frame: hci0 head byte 2: 0x0<br />
<7>[  185.825424] btusb_send_frame: hci0 skb len: 0x3<br />
<7>[  185.825463] __hci_request: hci0 end: err 0<br />
<7>[  185.825479] hci_sock_dev_event: hdev hci0 event 3<br />
<7>[  185.825498] hci_send_to_sock: hdev raw (null) len 8<br />
<7>[  185.825529] hci_sock_release: sock d288c6c0 sk ceaf4000<br />
<7>[  185.826994] btusb_tx_complete: hci0 urb ceae94c0 status 0 count 3<br />
<7>[  185.827977] btusb_intr_complete: hci0 urb c73daac0 status 0 count 14<br />
<7>[  185.828016] hci_rx_task: hci0 arg: d2397800<br />
<7>[  185.828029] hci_rx_task: hci0 hdev: c0835edc<br />
<7>[  185.828041] hci_rx_task: hci0<br />
<7>[  185.828052] hci_rx_task: hci0 event packet<br />
<7>[  185.828066] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
<7>[  185.828079] hci_cmd_complete_evt: hci0 ev->opcode 0x1003<br />
<7>[  185.828093] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x0<br />
<7>[  185.828106] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
<7>[  185.828120] hci_cmd_complete_evt: hci0 &ev->opcode-2 0xc<br />
<7>[  185.828133] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
<7>[  185.828147] hci_cmd_complete_evt: hci0 &ev->opcode 0x3<br />
<7>[  185.828160] hci_cmd_complete_evt: hci0 &ev->opcode+1 0x10<br />
<7>[  185.828174] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
<7>[  185.828188] hci_cmd_complete_evt: hci0 &ev->opcode+3 0xff<br />
<7>[  185.828202] hci_cmd_complete_evt: hci0 &ev->opcode+4 0xff<br />
<7>[  185.828218] hci_cc_read_local_features: hci0 status 0x0<br />
<7>[  185.828238] hci_cc_read_local_features: hci0 features 0xffff8ffe9bf90080<br />
<7>[  185.828255] hci_cmd_complete_evt: hci0 opcode 0x1003 (recognized if not twice)<br />
<7>[  185.828272] hci_event_packet: hci0 event 0xe<br />
<7>[  185.828287] hci_cmd_task: hci0 cmd 1<br />
<7>[  185.828305] hci_send_frame: hci0 type 1 len 3<br />
<7>[  185.828318] hci_send_frame: hci0 head byte 0: 0x1<br />
<7>[  185.828331] hci_send_frame: hci0 head byte 1: 0x10<br />
<7>[  185.828343] hci_send_frame: hci0 head byte 2: 0x0<br />
<7>[  185.828355] btusb_send_frame: hci0<br />
<7>[  185.828366] btusb_send_frame: hci0 skb data len: 0x0<br />
<7>[  185.828380] btusb_send_frame: hci0 head byte 0: 0x1<br />
<7>[  185.828393] btusb_send_frame: hci0 head byte 1: 0x10<br />
<7>[  185.828405] btusb_send_frame: hci0 head byte 2: 0x0<br />
<7>[  185.828421] btusb_send_frame: hci0 skb len: 0x3<br />
<4>[  185.829240] adb_write<br />
<4>[  185.829281] adb_write<br />
<4>[  185.831279] adb_read<br />
<7>[  185.839279] btusb_tx_complete: hci0 urb ceae94c0 status 0 count 3<br />
<7>[  185.839977] btusb_intr_complete: hci0 urb c73daac0 status 0 count 14<br />
<7>[  185.840015] hci_rx_task: hci0 arg: d2397800<br />
<7>[  185.840028] hci_rx_task: hci0 hdev: c0835edc<br />
<7>[  185.840040] hci_rx_task: hci0<br />
<7>[  185.840050] hci_rx_task: hci0 event packet<br />
<7>[  185.840063] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
<7>[  185.840076] hci_cmd_complete_evt: hci0 ev->opcode 0x1001<br />
<7>[  185.840090] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x65<br />
<7>[  185.840104] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
<7>[  185.840118] hci_cmd_complete_evt: hci0 &ev->opcode-2 0xc<br />
<7>[  185.840131] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
<7>[  185.840145] hci_cmd_complete_evt: hci0 &ev->opcode 0x1<br />
<7>[  185.840158] hci_cmd_complete_evt: hci0 &ev->opcode+1 0x10<br />
<7>[  185.840172] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
<7>[  185.840185] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x2<br />
<7>[  185.840199] hci_cmd_complete_evt: hci0 &ev->opcode+4 0xa6<br />
<7>[  185.840214] hci_cc_read_local_version: hci0 status 0x0<br />
<7>[  185.840231] hci_cc_read_local_version: hci0 manufacturer 10 hci ver 2:1958<br />
<7>[  185.840248] hci_cmd_complete_evt: hci0 opcode 0x1001 (recognized if not twice)<br />
<7>[  185.840264] hci_event_packet: hci0 event 0xe<br />
<7>[  185.840279] hci_cmd_task: hci0 cmd 1<br />
<7>[  185.840296] hci_send_frame: hci0 type 1 len 3<br />
<7>[  185.840309] hci_send_frame: hci0 head byte 0: 0x5<br />
<7>[  185.840323] hci_send_frame: hci0 head byte 1: 0x10<br />
<7>[  185.840335] hci_send_frame: hci0 head byte 2: 0x0<br />
<7>[  185.840347] btusb_send_frame: hci0<br />
<7>[  185.840358] btusb_send_frame: hci0 skb data len: 0x0<br />
<7>[  185.840371] btusb_send_frame: hci0 head byte 0: 0x5<br />
<7>[  185.840384] btusb_send_frame: hci0 head byte 1: 0x10<br />
<7>[  185.840397] btusb_send_frame: hci0 head byte 2: 0x0<br />
<7>[  185.840412] btusb_send_frame: hci0 skb len: 0x3<br />
<7>[  185.844592] btusb_tx_complete: hci0 urb ceae94c0 status 0 count 3<br />
<7>[  185.845975] btusb_intr_complete: hci0 urb c73daac0 status 0 count 13<br />
<7>[  185.846007] hci_rx_task: hci0 arg: d2397800<br />
<7>[  185.846020] hci_rx_task: hci0 hdev: c0835edc<br />
<7>[  185.846031] hci_rx_task: hci0<br />
<7>[  185.846041] hci_rx_task: hci0 event packet<br />
<7>[  185.846054] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
<7>[  185.846068] hci_cmd_complete_evt: hci0 ev->opcode 0x1005<br />
<7>[  185.846081] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x65<br />
<7>[  185.846095] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
<7>[  185.846109] hci_cmd_complete_evt: hci0 &ev->opcode-2 0xb<br />
<7>[  185.846122] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
<7>[  185.846135] hci_cmd_complete_evt: hci0 &ev->opcode 0x5<br />
<7>[  185.846149] hci_cmd_complete_evt: hci0 &ev->opcode+1 0x10<br />
<7>[  185.846162] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
<7>[  185.846176] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x80<br />
<7>[  185.846190] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x1<br />
<7>[  185.846205] hci_cc_read_buffer_size: hci0 status 0x0<br />
<7>[  185.846221] hci_cc_read_buffer_size: hci0 acl mtu 384:8 sco mtu 64:8<br />
<7>[  185.846238] hci_cmd_complete_evt: hci0 opcode 0x1005 (recognized if not twice)<br />
<7>[  185.846254] hci_event_packet: hci0 event 0xe<br />
<7>[  185.846268] hci_cmd_task: hci0 cmd 1<br />
<7>[  185.846283] hci_send_frame: hci0 type 1 len 3<br />
<7>[  185.846296] hci_send_frame: hci0 head byte 0: 0x9<br />
<7>[  185.846309] hci_send_frame: hci0 head byte 1: 0x10<br />
<7>[  185.846322] hci_send_frame: hci0 head byte 2: 0x0<br />
<7>[  185.846333] btusb_send_frame: hci0<br />
<7>[  185.846344] btusb_send_frame: hci0 skb data len: 0x0<br />
<7>[  185.846357] btusb_send_frame: hci0 head byte 0: 0x9<br />
<7>[  185.846370] btusb_send_frame: hci0 head byte 1: 0x10<br />
<7>[  185.846383] btusb_send_frame: hci0 head byte 2: 0x0<br />
<7>[  185.846398] btusb_send_frame: hci0 skb len: 0x3<br />
<7>[  185.847993] btusb_tx_complete: hci0 urb ceae94c0 status 0 count 3<br />
<7>[  185.848978] btusb_intr_complete: hci0 urb c73daac0 status 0 count 12<br />
<7>[  185.849014] hci_rx_task: hci0 arg: d2397800<br />
<7>[  185.849027] hci_rx_task: hci0 hdev: c0835edc<br />
<7>[  185.849038] hci_rx_task: hci0<br />
<7>[  185.849049] hci_rx_task: hci0 event packet<br />
<7>[  185.849061] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
<7>[  185.849075] hci_cmd_complete_evt: hci0 ev->opcode 0x1009<br />
<7>[  185.849089] hci_cmd_complete_evt: hci0 &ev->opcode-4 0xc9<br />
<7>[  185.849102] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
<7>[  185.849116] hci_cmd_complete_evt: hci0 &ev->opcode-2 0xa<br />
<7>[  185.849130] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
<7>[  185.849143] hci_cmd_complete_evt: hci0 &ev->opcode 0x9<br />
<7>[  185.849157] hci_cmd_complete_evt: hci0 &ev->opcode+1 0x10<br />
<7>[  185.849170] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
<7>[  185.849184] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x6b<br />
<7>[  185.849197] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x3c<br />
<7>[  185.849212] hci_cc_read_bd_addr: hci0 status 0x0<br />
<7>[  185.849226] hci_req_complete: hci0 result 0x00<br />
<7>[  185.849239] hci_cmd_complete_evt: hci0 opcode 0x1009 (recognized if not twice)<br />
<7>[  185.849256] hci_event_packet: hci0 event 0xe<br />
<7>[  185.849271] hci_cmd_task: hci0 cmd 1<br />
<7>[  185.849286] hci_send_frame: hci0 type 1 len 3<br />
<7>[  185.849299] hci_send_frame: hci0 head byte 0: 0x23<br />
<7>[  185.849312] hci_send_frame: hci0 head byte 1: 0xc<br />
<7>[  185.849324] hci_send_frame: hci0 head byte 2: 0x0<br />
<7>[  185.849336] btusb_send_frame: hci0<br />
<7>[  185.849347] btusb_send_frame: hci0 skb data len: 0x0<br />
<7>[  185.849360] btusb_send_frame: hci0 head byte 0: 0x23<br />
<7>[  185.849374] btusb_send_frame: hci0 head byte 1: 0xc<br />
<7>[  185.849387] btusb_send_frame: hci0 head byte 2: 0x0<br />
<7>[  185.849401] btusb_send_frame: hci0 skb len: 0x3<br />
<7>[  185.850994] btusb_tx_complete: hci0 urb ceae94c0 status 0 count 3<br />
<7>[  185.851973] btusb_intr_complete: hci0 urb c73daac0 status 0 count 9<br />
<7>[  185.852006] hci_rx_task: hci0 arg: d2397800<br />
<7>[  185.852019] hci_rx_task: hci0 hdev: c0835edc<br />
<7>[  185.852030] hci_rx_task: hci0<br />
<7>[  185.852040] hci_rx_task: hci0 event packet<br />
<7>[  185.852053] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
<7>[  185.852066] hci_cmd_complete_evt: hci0 ev->opcode 0xc23<br />
<7>[  185.852080] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x0<br />
<7>[  185.852093] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
<7>[  185.852107] hci_cmd_complete_evt: hci0 &ev->opcode-2 0x7<br />
<7>[  185.852121] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
<7>[  185.852134] hci_cmd_complete_evt: hci0 &ev->opcode 0x23<br />
<7>[  185.852148] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
<7>[  185.852162] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
<7>[  185.852175] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x0<br />
<7>[  185.852188] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x0<br />
<7>[  185.852203] hci_cc_read_class_of_dev: hci0 status 0x0<br />
<7>[  185.852218] hci_cc_read_class_of_dev: hci0 class 0x000000<br />
<7>[  185.852233] hci_cmd_complete_evt: hci0 opcode 0xc23 (recognized if not twice)<br />
<7>[  185.852249] hci_event_packet: hci0 event 0xe<br />
<7>[  185.852263] hci_cmd_task: hci0 cmd 1<br />
<7>[  185.852279] hci_send_frame: hci0 type 1 len 3<br />
<7>[  185.852291] hci_send_frame: hci0 head byte 0: 0x14<br />
<7>[  185.852304] hci_send_frame: hci0 head byte 1: 0xc<br />
<7>[  185.852317] hci_send_frame: hci0 head byte 2: 0x0<br />
<7>[  185.852329] btusb_send_frame: hci0<br />
<7>[  185.852340] btusb_send_frame: hci0 skb data len: 0x0<br />
<7>[  185.852353] btusb_send_frame: hci0 head byte 0: 0x14<br />
<7>[  185.852366] btusb_send_frame: hci0 head byte 1: 0xc<br />
<7>[  185.852379] btusb_send_frame: hci0 head byte 2: 0x0<br />
<7>[  185.852393] btusb_send_frame: hci0 skb len: 0x3<br />
<7>[  185.873053] btusb_tx_complete: hci0 urb ceae94c0 status 0 count 3<br />
<7>[  185.875979] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.876979] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.877978] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.878978] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.879978] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.880978] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.881978] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.882978] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.883978] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.884978] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.885978] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.886977] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.887977] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.888980] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.889979] btusb_intr_complete: hci0 urb c73daac0 status 0 count 16<br />
<7>[  185.890976] btusb_intr_complete: hci0 urb c73daac0 status 0 count 14<br />
<7>[  185.891006] hci_rx_task: hci0 arg: d2397800<br />
<7>[  185.891020] hci_rx_task: hci0 hdev: c0835edc<br />
<7>[  185.891031] hci_rx_task: hci0<br />
<7>[  185.891041] hci_rx_task: hci0 event packet<br />
<7>[  185.891054] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
<7>[  185.891068] hci_cmd_complete_evt: hci0 ev->opcode 0xc14<br />
<7>[  185.891081] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x0<br />
<7>[  185.891095] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
<7>[  185.891108] hci_cmd_complete_evt: hci0 &ev->opcode-2 0xfc<br />
<7>[  185.891122] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
<7>[  185.891136] hci_cmd_complete_evt: hci0 &ev->opcode 0x14<br />
<7>[  185.891149] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
<7>[  185.891163] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
<7>[  185.891177] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x43<br />
<7>[  185.891190] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x53<br />
<7>[  185.891206] hci_cc_read_local_name: hci0 status 0x0<br />
<7>[  185.891221] hci_cmd_complete_evt: hci0 opcode 0xc14 (recognized if not twice)<br />
<7>[  185.891238] hci_event_packet: hci0 event 0xe<br />
<7>[  185.891253] hci_cmd_task: hci0 cmd 1<br />
<7>[  185.891269] hci_send_frame: hci0 type 1 len 3<br />
<7>[  185.891282] hci_send_frame: hci0 head byte 0: 0x25<br />
<7>[  185.891295] hci_send_frame: hci0 head byte 1: 0xc<br />
<7>[  185.891308] hci_send_frame: hci0 head byte 2: 0x0<br />
<7>[  185.891320] btusb_send_frame: hci0<br />
<7>[  185.891331] btusb_send_frame: hci0 skb data len: 0x0<br />
<7>[  185.891343] btusb_send_frame: hci0 head byte 0: 0x25<br />
<7>[  185.891357] btusb_send_frame: hci0 head byte 1: 0xc<br />
<7>[  185.891369] btusb_send_frame: hci0 head byte 2: 0x0<br />
<7>[  185.891384] btusb_send_frame: hci0 skb len: 0x3<br />
<7>[  185.892989] btusb_tx_complete: hci0 urb ceae94c0 status 0 count 3<br />
<7>[  185.893976] btusb_intr_complete: hci0 urb c73daac0 status 0 count 8<br />
<7>[  185.894008] hci_rx_task: hci0 arg: d2397800<br />
<7>[  185.894021] hci_rx_task: hci0 hdev: c0835edc<br />
<7>[  185.894032] hci_rx_task: hci0<br />
<7>[  185.894042] hci_rx_task: hci0 event packet<br />
<7>[  185.894055] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
<7>[  185.894068] hci_cmd_complete_evt: hci0 ev->opcode 0xc25<br />
<7>[  185.894082] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x0<br />
<7>[  185.894095] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
<7>[  185.894109] hci_cmd_complete_evt: hci0 &ev->opcode-2 0x6<br />
<7>[  185.894123] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
<7>[  185.894136] hci_cmd_complete_evt: hci0 &ev->opcode 0x25<br />
<7>[  185.894150] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
<7>[  185.894163] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
<7>[  185.894177] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x60<br />
<7>[  185.894191] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x0<br />
<7>[  185.894206] hci_cc_read_voice_setting: hci0 status 0x0<br />
<7>[  185.894220] hci_cc_read_voice_setting: hci0 voice setting 0x0060<br />
<7>[  185.894235] btusb_notify: hci0 evt 3<br />
<7>[  185.894248] hci_cmd_complete_evt: hci0 opcode 0xc25 (recognized if not twice)<br />
<7>[  185.894264] hci_event_packet: hci0 event 0xe<br />
<7>[  185.894278] hci_cmd_task: hci0 cmd 1<br />
<7>[  185.894293] hci_send_frame: hci0 type 1 len 4<br />
<7>[  185.894305] hci_send_frame: hci0 head byte 0: 0x5<br />
<7>[  185.894318] hci_send_frame: hci0 head byte 1: 0xc<br />
<7>[  185.894331] hci_send_frame: hci0 head byte 2: 0x1<br />
<7>[  185.894343] btusb_send_frame: hci0<br />
<7>[  185.894354] btusb_send_frame: hci0 skb data len: 0x0<br />
<7>[  185.894367] btusb_send_frame: hci0 head byte 0: 0x5<br />
<7>[  185.894380] btusb_send_frame: hci0 head byte 1: 0xc<br />
<7>[  185.894393] btusb_send_frame: hci0 head byte 2: 0x1<br />
<7>[  185.894408] btusb_send_frame: hci0 skb len: 0x4<br />
<7>[  185.895994] btusb_tx_complete: hci0 urb ceae94c0 status 0 count 4<br />
<7>[  185.896974] btusb_intr_complete: hci0 urb c73daac0 status 0 count 6<br />
<7>[  185.897006] hci_rx_task: hci0 arg: d2397800<br />
<7>[  185.897019] hci_rx_task: hci0 hdev: c0835edc<br />
<7>[  185.897030] hci_rx_task: hci0<br />
<7>[  185.897040] hci_rx_task: hci0 event packet<br />
<7>[  185.897053] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
<7>[  185.897066] hci_cmd_complete_evt: hci0 ev->opcode 0xc05<br />
<7>[  185.897080] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x0<br />
<7>[  185.897093] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
<7>[  185.897107] hci_cmd_complete_evt: hci0 &ev->opcode-2 0x4<br />
<7>[  185.897120] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
<7>[  185.897134] hci_cmd_complete_evt: hci0 &ev->opcode 0x5<br />
<7>[  185.897147] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
<7>[  185.897161] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
<7>[  185.897174] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x0<br />
<7>[  185.897188] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x0<br />
<7>[  185.897202] hci_cmd_complete_evt: hci0 default (non-recognized) opcode 0xc05<br />
<7>[  185.897218] hci_cmd_complete_evt: hci0 opcode 0xc05 (recognized if not twice)<br />
<7>[  185.897235] hci_event_packet: hci0 event 0xe<br />
<7>[  185.897249] hci_cmd_task: hci0 cmd 1<br />
<7>[  185.897264] hci_send_frame: hci0 type 1 len 5<br />
<7>[  185.897277] hci_send_frame: hci0 head byte 0: 0x18<br />
<7>[  185.897290] hci_send_frame: hci0 head byte 1: 0xc<br />
<7>[  185.897302] hci_send_frame: hci0 head byte 2: 0x2<br />
<7>[  185.897314] btusb_send_frame: hci0<br />
<7>[  185.897325] btusb_send_frame: hci0 skb data len: 0x0<br />
<7>[  185.897338] btusb_send_frame: hci0 head byte 0: 0x18<br />
<7>[  185.897351] btusb_send_frame: hci0 head byte 1: 0xc<br />
<7>[  185.897364] btusb_send_frame: hci0 head byte 2: 0x2<br />
<7>[  185.897378] btusb_send_frame: hci0 skb len: 0x5<br />
<7>[  185.898989] btusb_tx_complete: hci0 urb ceae94c0 status 0 count 5<br />
<7>[  185.899974] btusb_intr_complete: hci0 urb c73daac0 status 0 count 6<br />
<7>[  185.900006] hci_rx_task: hci0 arg: d2397800<br />
<7>[  185.900019] hci_rx_task: hci0 hdev: c0835edc<br />
<7>[  185.900030] hci_rx_task: hci0<br />
<7>[  185.900041] hci_rx_task: hci0 event packet<br />
<7>[  185.900053] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
<7>[  185.900067] hci_cmd_complete_evt: hci0 ev->opcode 0xc18<br />
<7>[  185.900080] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x0<br />
<7>[  185.900094] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
<7>[  185.900107] hci_cmd_complete_evt: hci0 &ev->opcode-2 0x4<br />
<7>[  185.900121] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
<7>[  185.900135] hci_cmd_complete_evt: hci0 &ev->opcode 0x18<br />
<7>[  185.900148] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
<7>[  185.900161] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
<7>[  185.900175] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x0<br />
<7>[  185.900188] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x0<br />
<7>[  185.900203] hci_cmd_complete_evt: hci0 default (non-recognized) opcode 0xc18<br />
<7>[  185.900219] hci_cmd_complete_evt: hci0 opcode 0xc18 (recognized if not twice)<br />
<7>[  185.900235] hci_event_packet: hci0 event 0xe<br />
<7>[  185.900250] hci_cmd_task: hci0 cmd 1<br />
<7>[  185.900265] hci_send_frame: hci0 type 1 len 5<br />
<7>[  185.900278] hci_send_frame: hci0 head byte 0: 0x16<br />
<7>[  185.900291] hci_send_frame: hci0 head byte 1: 0xc<br />
<7>[  185.900303] hci_send_frame: hci0 head byte 2: 0x2<br />
<7>[  185.900315] btusb_send_frame: hci0<br />
<7>[  185.900326] btusb_send_frame: hci0 skb data len: 0x0<br />
<7>[  185.900339] btusb_send_frame: hci0 head byte 0: 0x16<br />
<7>[  185.900352] btusb_send_frame: hci0 head byte 1: 0xc<br />
<7>[  185.900365] btusb_send_frame: hci0 head byte 2: 0x2<br />
<7>[  185.900379] btusb_send_frame: hci0 skb len: 0x5<br />
<7>[  185.901988] btusb_tx_complete: hci0 urb ceae94c0 status 0 count 5<br />
<7>[  185.902975] btusb_intr_complete: hci0 urb c73daac0 status 0 count 6<br />
<7>[  185.903006] hci_rx_task: hci0 arg: d2397800<br />
<7>[  185.903019] hci_rx_task: hci0 hdev: c0835edc<br />
<7>[  185.903031] hci_rx_task: hci0<br />
<7>[  185.903041] hci_rx_task: hci0 event packet<br />
<7>[  185.903053] hci_cmd_complete_evt: hci0 ev->ncmd 0x1<br />
<7>[  185.903067] hci_cmd_complete_evt: hci0 ev->opcode 0xc16<br />
<7>[  185.903080] hci_cmd_complete_evt: hci0 &ev->opcode-4 0x0<br />
<7>[  185.903094] hci_cmd_complete_evt: hci0 &ev->opcode-3 0xe<br />
<7>[  185.903107] hci_cmd_complete_evt: hci0 &ev->opcode-2 0x4<br />
<7>[  185.903121] hci_cmd_complete_evt: hci0 &ev->opcode-1 0x1<br />
<7>[  185.903135] hci_cmd_complete_evt: hci0 &ev->opcode 0x16<br />
<7>[  185.903148] hci_cmd_complete_evt: hci0 &ev->opcode+1 0xc<br />
<7>[  185.903162] hci_cmd_complete_evt: hci0 &ev->opcode+2 0x0<br />
<7>[  185.903175] hci_cmd_complete_evt: hci0 &ev->opcode+3 0x0<br />
<7>[  185.903188] hci_cmd_complete_evt: hci0 &ev->opcode+4 0x0<br />
<7>[  185.903203] hci_cc_write_ca_timeout: hci0 status 0x0<br />
<7>[  185.903217] hci_req_complete: hci0 result 0x00<br />
<7>[  185.903231] hci_cmd_complete_evt: hci0 opcode 0xc16 (recognized if not twice)<br />
<7>[  185.903246] hci_event_packet: hci0 event 0xe<br />
<4>[  186.277985] adb_read<br />
<4>[  186.278103] adb_read<br />
<4>[  186.279779] adb_write<br />
<4>[  186.299153] adb_write<br />
<4>[  186.299186] adb_write<br />
<4>[  186.301291] adb_read<br />
<4>[  186.454172] adb_read<br />
<4>[  186.454408] adb_read<br />
<4>[  186.455741] adb_write<br />
<4>[  186.469103] adb_write<br />
<4>[  186.469134] adb_write<br />
<4>[  186.470995] adb_read<br />
<4>[  186.918058] adb_read<br />
<4>[  186.918219] adb_read<br />
<4>[  186.919831] adb_write<br />
<7>[  186.936653] hci_sock_create: sock d288c6c0<br />
<7>[  186.936770] hci_sock_ioctl: cmd 800448d2 arg 17008<br />
<7>[  186.936795] hci_sock_ioctl: cmd 800448d3 arg 16234<br />
<7>[  186.936812] hci_dev_get: 0<br />
<7>[  186.937505] hci_sock_release: sock d288c6c0 sk d23d6600<br />
 

·
Registered
Joined
·
130 Posts
Discussion Starter · #5 ·
Hey wait a moment, there's a succesful get name operation in the log when bringing the interface up. So, instead of a general failure of the local commands like get or set name, what's happening seems to be the device goes into some kind of failure mode after it is brought up and after the initial get name op succeeds.
The successfull op is in function hci_init_req() in hci_core.c, i.e. in-kernel call. hci_init_req is called I think from hci_dev_open().

What's strange is that it seems to me the order of operations is the same in the in-kernel get name operation and the from-user-mode operation. But the end result is different, one works and one doesn't. Perhaps there's difference in some data structures (sk_buf ?) and the skbufs get corrupted, leading to the data packet to be corrupted after received from the USB bus, and the opcode 0x1401 instead of 0x0c14. Or perhaps the request packet is corrupted due to some other data structure difference after being passed in the URB to the in-kernel USB code.
 

·
Registered
Joined
·
106 Posts
I'm out of town for work for a few days, so i cant check anything.

I seem to remember that the bluez hci interface uses hci_dev and maby other structures.
I'm assuming that some of these structures must some how correspond to the kernel version.

As the bluez recompiles i did where from the gigerbread tree and there might be deferend from our active/compiled rk29xx tree.
We could de the same check as before and verify sizeof's of strucrurs in the bluez tree with corresponding sizeofs from the kernel tree

The there is a discrepency of 1 byte more or less then x1 x2 01 14 x3 x4 could verywell be one byte shift and you get x2 14 x3 x4 ?? (when x3 is 0c you get 0x0c14)
 

·
Registered
Joined
·
130 Posts
I seem to remember that the bluez hci interface uses hci_dev and maby other structures.
I'm assuming that some of these structures must some how correspond to the kernel version.
Yes, that holds for you as you have kernel-internal bluetooth, but I don't think the hci structures are in the kernel for me, as bluetooth has to be compiled as an external module.

I have done some sizeof checks, but haven't found a problem. I didn't find a way to find the size of skbuff in the kernel though.

Update: Here are some things I've printed, unfortunately seems I haven't systematically marked which I've managed to check or which seem to constant size (like poll_t) in includes.

Code:
<br />
 printk("10: %04x [?    ]mutex\n",sizeof(struct mutex));<br />
 printk("11: %04x [?    ]tty_driver\n",sizeof(struct tty_driver));<br />
 printk("12: %04x [?    ]acm\n",sizeof(struct acm));<br />
 printk("13: %04x [?    ]tty_port\n",sizeof(struct tty_port));<br />
 printk("14: %04x [?    ]tty_struct\n",sizeof(struct tty_struct));<br />
 printk("15: %04x [?    ]work_struct\n",sizeof(struct work_struct));<br />
 printk("16: %04x [?    ]spinlock_t\n",sizeof(spinlock_t));<br />
 printk("17: %04x [?    ]tty_bufhead\n",sizeof(struct tty_bufhead));<br />
 printk("18: %04x [?    ]timer_list\n",sizeof(struct timer_list));<br />
 printk("19: %04x [?    ]tty_struct->buf\n",(void *) &ts.buf - (void *) &ts);<br />
 printk("20: %04x [?    ]tty_struct->port\n",(void *) &ts.port - (void *) &ts);<br />
 printk("21: %04x [?    ]tty_port->count\n",(void *) &tp.count - (void *) &tp);<br />
 printk("22: %04x [?    ]tty_struct->driver_data\n",(void *) &ts.driver_data - (void *) &ts);<br />
 printk("23: %04x [?    ]usb_device\n",sizeof(struct usb_device));<br />
 printk("24: %04x [?    ]kmem_cache\n",sizeof(struct kmem_cache));<br />
 printk("25: %04x [?    ]pollfd\n",sizeof(struct pollfd));<br />
 // printk("26: %04x [?    ]rfkill\n",sizeof(struct rfkill));<br />
 printk("27: %04x [?    ]device\n",sizeof(struct device));<br />
 printk("28: %04x [?    ]module\n",sizeof(struct module));<br />
 printk("29: %04x [?    ]device\n",sizeof(struct device));<br />
 printk("30: %04x [?    ]semaphore\n",sizeof(struct semaphore));<br />
 printk("31: %04x [?    ]dev_archdata\n",sizeof(struct dev_archdata));<br />
 printk("32: %04x [?    ]klist_node\n",sizeof(struct klist_node));<br />
 printk("33: %04x [?    ]iovec\n",sizeof(struct iovec));<br />
 printk("34: %04x [?    ]socket\n",sizeof(struct socket));<br />
 printk("35: %04x [?    ]sockaddr\n",sizeof(struct sockaddr));<br />
 printk("36: %04x [?    ]net\n",sizeof(struct net));<br />
 printk("37: %04x [?    ]sco_conn\n",sizeof(struct sco_conn));<br />
Update2: I'll probably be taking a break from the attempt getting this kernel bluetooth control stuff to work, or perhaps will abandon the attempt. Come to think of it, I should be able to use the mobile phone & GPS by bluetooth or USB even without getting the Android bluetooth support to work: You report rfcomm works so rfcomm bluetooth for the phone should work too. Also, I've tested /dev/ttyACM0 for wired USB connection to phone to work (on Ubuntu side with pppd) so I expect the GPS USB dongle should work (although it's a different serial converter, so it's not sure). So, the most important stuff (for me) should work even at this stage of bluetooth functionality. While BT file transfer are a nice idea, I find I've very rarely used bluetooth file transfer anyway, so it doesn't look important to get the Android BT interface to work for that part.

Oops, I forgot about pairing - to use rfcomm, I'd need to be able to pair the phone and the tablet. Hmm, actually, maybe not: as both the laptop and the tablet use bluez, I think I should be able to pair the devices on the laptop and copy the key files from the laptop to the tablet.
 

·
Registered
Joined
·
130 Posts
No success yet with paring, though I do get the "agent" (pin agent) binary to connect to bluetoothd.

While trying to debug pairing, I found a user-mode debug tool for the control connection issue. No kernel debugging necessary, "hcitool cmd" can be used to show the different events from the laptop and the tablet.

laptop get local name operation:

Code:
<br />
$ hcitool cmd 0x03 0x0014 <br />
< HCI Command: ogf 0x03, ocf 0x0014, plen 0<br />
> HCI Event: 0x0e plen 252<br />
  01 14 0C 00 6A 6B 70 2D 6C 61 70 74 6F 70 00 00 00 00 00 00 <br />
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <br />
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <br />
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <br />
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <br />
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <br />
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <br />
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <br />
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <br />
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <br />
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <br />
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <br />
  00 00 00 00 00 00 00 00 00 00 00 00 <br />
tablet get local name operation (failing):

Code:
<br />
# hcitool cmd 0x03 0x0014<br />
< HCI Command: ogf 0x03, ocf 0x0014, plen 0<br />
> HCI Event: 0x0e plen 8<br />
  01 01 14 12 03 00 00 00 <br />
Update: Interestingly, after a while poking with different commands, now the result is:

Code:
<br />
# hcitool cmd 0x03 0x0014<br />
< HCI Command: ogf 0x03, ocf 0x0014, plen 0<br />
> HCI Event: 0x0e plen 8<br />
  01 01 14 12 0C 01 00 00 <br />
so the 0x0c does show up; but probably just a coincided, as now I also get:

Code:
<br />
# hcitool cmd 0x03 0x0014<br />
< HCI Command: ogf 0x03, ocf 0x0014, plen 0<br />
> HCI Event: 0x0e plen 8<br />
  01 01 14 12 0D 01 00 00 <br />
without giving any other commands than 0x03 0x0014.
 

·
Registered
Joined
·
130 Posts
Discussion Starter · #9 ·
Hmm, with some testing with hcitool cmd, I'm beginning to wonder if this is an endianness issue - on the laptop, the last hex byte influences the second-to-last byte in the reply and the second-to-last byte influences the last byte. On the tablet, the last hex byte influences the last byte. Normally this wouldn't be probable, but perhaps it's possible as it seems ARM swings both ways: "The ARM Architectural Reference Manual states that ARM processors are bi-endian" and "The ARM can be configured to be either little- or big-endian."
 

·
Registered
Joined
·
106 Posts
I did the same test with the same result / failure...

I added debuginfo to btusb.c where i dump the contents of the urb buffer in
btusb_send_frame (what i think is the sending part)
and in btusb_intr_complete (what i think is "one of" the receiving part)

this is the result of hcitool cmd 0x3 0x14

<4>[ 1589.178967] oTEST: 14 0c 00 01 <-- send

where 0x14 0x0c the opcode for HCI_OP_READ_LOCAL_NAME

<4>[ 1589.207987] iTEST: 0e 08 01 01 14 12 00 00 00 00 e3 <-- receive
where 0xe = HCI_EV_CMD_COMPLETE
0x8 = length
0x1 = cmdnr
0x1 0x14 = shoould be the confirmed/complete opcode
rest = data

this seems to be wrong...

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
I also check the loggin from the start of insmod bttest enable

<4>[ 1564.053812] oTEST: 03 0c 00 72
<4>[ 1564.056920] oTEST: . . .
<4>[ 1566.667448] iTEST: 0e 04 01 03 0c 00 fb
<4>[ 1566.671348] iTEST: . . . . . .
<4>[ 1566.694203] oTEST: 03 10 00 62
<4>[ 1566.697262] oTEST: . . .
<4>[ 1566.718668] iTEST: 0e 0c 01 03 10 00 ff ff 8f fe 9b ff 59 83 ab
<4>[ 1566.724648] iTEST: . . . . . . . . . . . . Y .
<4>[ 1566.749534] oTEST: 01 10 00 00
<4>[ 1566.752641] oTEST: . . .
<4>[ 1566.778555] iTEST: 0e 0c 01 01 10 00 04 e7 12 04 0a 00 e7 12 1e
<4>[ 1566.784535] iTEST: . . . . . . . . . . . . . .
<4>[ 1566.809421] oTEST: 05 10 00 00
<4>[ 1566.812528] oTEST: . . .
<4>[ 1566.834727] iTEST: 0e 0b 01 05 10 00 36 01 40 0a 00 08 00 84
<4>[ 1566.840447] iTEST: . . . . . . 6 . @ . . . .
<4>[ 1566.867543] oTEST: 09 10 00 00
<4>[ 1566.870656] oTEST: . . .
<4>[ 1566.892062] iTEST: 0e 0a 01 09 10 00 d2 91 50 dd 09 00 00
<4>[ 1566.897522] iTEST: . . . . . . . . P . . .
<4>[ 1566.921882] oTEST: 23 0c 00 00
<4>[ 1566.924996] oTEST: . . .
<4>[ 1566.958015] iTEST: 0e 07 01 23 0c 00 00 00 00 ff
<4>[ 1566.962695] iTEST: . . . . . . . . .
<4>[ 1566.991823] oTEST: 14 0c 00 00
<4>[ 1566.994936] oTEST: . . .
<4>[ 1567.022866] iTEST: 0e fc 01 14 0c 00 42 54 32 2e 30 00 00 00 00 00
<4>[ 1567.029106] iTEST: . . . . . . B T 2 . 0 . . . . .
<4>[ 1567.035346] iTEST: 08
<4>[ 1567.037686] iTEST:
... followed by more ....

And what do i see ....
An call for opcode 0x14 0xC
Followed by a successfull response containing the usbdevice name...

There is a difference in the call 0x14 0x0c 0x00 0x00 (triggerd from btenable) [successfull]
and 0x14 0x0c 0x00 0x01 (triggerd from hcitool) [failing]
 

·
Registered
Joined
·
130 Posts
Discussion Starter · #11 ·
I checked the Archos gen9 kernel repo (I think this is for archos r29xx devices), and it has been populated. The repo is at git://gitorious.org/archos/archos-gpl-gen9-kernel.git

The repo appears to contain a kernel source tree, kernel version appears to be 2.6.35.7 according to linux.config and also Makefile.

Diff to stock 2.6.35.7 is quite big, 159343 lines without new files.

Maybe this can be of help to find out what happens with btusb.ko.

Can't find a single reference in the diffs to "rockchip", "r29", "rk29" though, so I'm beginning to wonder if this has much to do with Rockchip sources. There is however mach-omap2/board-archos-a101h.c which would seem to match with the Archos 101 home tablet which has a rk29xx processor. (see http://www.arctablet.com/blog/archos-tablet/comparing-archos-101-home-tablet-cpu-rockchip-rk-2918/?lang=fr )
 

·
Registered
Joined
·
106 Posts
I checked the Archos gen9 kernel repo (I think this is for archos r29xx devices), and it has been populated. The repo is at git://gitorious.org/archos/archos-gpl-gen9-kernel.git

The repo appears to contain a kernel source tree, kernel version appears to be 2.6.35.7 according to linux.config and also Makefile.

Diff to stock 2.6.35.7 is quite big, 159343 lines without new files.

Maybe this can be of help to find out what happens with btusb.ko.

Can't find a single reference in the diffs to "rockchip", "r29", "rk29" though, so I'm beginning to wonder if this has much to do with Rockchip sources. There is however mach-omap2/board-archos-a101h.c which would seem to match with the Archos 101 home tablet which has a rk29xx processor. (see http://www.arctablet.com/blog/archos-tablet/comparing-archos-101-home-tablet-cpu-rockchip-rk-2918/?lang=fr )
I cant find any archos model on the archos website that is using the rk29xx chip, and the specs of the gen9 models point to be to useing the new omap4 chip.
 

·
Registered
Joined
·
130 Posts
I cant find any archos model on the archos website that is using the rk29xx chip, and the specs of the gen9 models point to be to useing the new omap4 chip.
OK, maybe the reports of Archos using rk2918 are incorrect. Another report is here: http://mp4nation.net/blog/2011/04/archos-7c-at-rockchip-booth-rk2918-gingerbread/ - according to it, a 7c home tablet prototype using rk2918 was presented at a Rockchip booth.

There do seem to be reports of Archos tablets using Rockchip at the hands of end users: http://www.arctablet.com/blog/archos-tablet/flashing-firmware-rockchip-cpu-based-devices-archos-ht-7-8-arnova-10/ "Flashing a firmware on Rockchip CPU based devices: Archos HT (7 and
and Arnova tablets". But wait a moment, that post specifies Archos 7c HT as using the Rockchip 2818 CPU. Confusing. Maybe Archos has done prototypes using RK 2918 but selected another processor for production models and the 2918 report is misleading. And/or maybe the mp4nation report is just incorrect, the device was a prototype of something else than the 7c HT. Or maybe they planned the 2918 but chose the 2818.

Update: The video the RK29XX-marked Rockchip stand at http://archosfans.com/2011/01/07/archos-101-home-tablet-at-ces-2011/ seems genuine enough. Though it's true that Rockchip presenting an Archos prototype at a RK29XX stand doesn't necessarily mean that the production models are with a RK29XX.

Update2: Another video seems to definitely connect Archos with plans to bring out a RK29XX tablet:

Update3: OK, now I think I can make some sense out of this - looks like Archos has published or plans to publish the RK29XX tablets under the label Arnova or "Archos Arnova", see e.g. http://www.cnx-software.com/2011/04/15/rk2918-arnova-10-with-capacitive-touchscreen/ and http://store.archos.com/arnova-p-5014.html and http://www.engadget.com/2011/02/26/archos-arnova-8-and-10-tablets-hit-the-bargain-bin-video/ - I downloaded the firmware for Arnova 10 from http://arnovatech.com/support/updates.html and extracted it with AFPTool.exe, does look like Rockchip though I couldn't confirm it as rk2918 - reading more closely at the releases, appears that at least the first Arnovas also were rk28xx with resistive screens, not sure if the rk29xx Arnovas (apparently G2 devices, see http://arnovatech.com/products/g2/arn_10/index.html?country=fi&lang=en ) are anything else than vaporware, or if they have some other processor than RK29XX. But maybe these Arnova RK29XX ones are real after all - unlike for the RK29XX Archos-branded tablets, there are recent mentions of RK29XX-based Arnova tables, e.g. http://www.arctablet.com/blog/featured/arnova-10-g2-android-2-3-capacitive-rk2918-cpu-512-mb-review/ and http://www.engadget.com/2011/08/11/archos-arnova-7-g2-and-10-g2-tablets-launch-in-hong-kong-taste/ and http://www.arctablet.com/blog/featured/arnova-10-g2-tablet-bundle-philly-com/

Update4: Here's another of the sources which point to the problem being that the Rockchip tablet vendors themselves don't have the source code for anything after rk2808: http://www.advogato.org/person/mjg59/diary.html?start=293
 

·
Registered
Joined
·
130 Posts
Discussion Starter · #14 ·
I don't think the difference between 14 0c 00 01 and 14 0c 00 00 (i.e. with the fourth byte) is relevant, as the length is only three bytes as output by my debug output (both on 3.0 kernel and the android kernel):

BT_DBG("%s skb len: 0x%x", hdev->name, skb->len);

in btusb_send_frame().

I did the same test with the same result / failure...

I added debuginfo to btusb.c where i dump the contents of the urb buffer in
btusb_send_frame (what i think is the sending part)
and in btusb_intr_complete (what i think is "one of" the receiving part)

this is the result of hcitool cmd 0x3 0x14

<4>[ 1589.178967] oTEST: 14 0c 00 01 <-- send

where 0x14 0x0c the opcode for HCI_OP_READ_LOCAL_NAME

<4>[ 1589.207987] iTEST: 0e 08 01 01 14 12 00 00 00 00 e3 <-- receive
where 0xe = HCI_EV_CMD_COMPLETE
0x8 = length
0x1 = cmdnr
0x1 0x14 = shoould be the confirmed/complete opcode
rest = data

this seems to be wrong...

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
I also check the loggin from the start of insmod bttest enable

<4>[ 1564.053812] oTEST: 03 0c 00 72
<4>[ 1564.056920] oTEST: . . .
<4>[ 1566.667448] iTEST: 0e 04 01 03 0c 00 fb
<4>[ 1566.671348] iTEST: . . . . . .
<4>[ 1566.694203] oTEST: 03 10 00 62
<4>[ 1566.697262] oTEST: . . .
<4>[ 1566.718668] iTEST: 0e 0c 01 03 10 00 ff ff 8f fe 9b ff 59 83 ab
<4>[ 1566.724648] iTEST: . . . . . . . . . . . . Y .
<4>[ 1566.749534] oTEST: 01 10 00 00
<4>[ 1566.752641] oTEST: . . .
<4>[ 1566.778555] iTEST: 0e 0c 01 01 10 00 04 e7 12 04 0a 00 e7 12 1e
<4>[ 1566.784535] iTEST: . . . . . . . . . . . . . .
<4>[ 1566.809421] oTEST: 05 10 00 00
<4>[ 1566.812528] oTEST: . . .
<4>[ 1566.834727] iTEST: 0e 0b 01 05 10 00 36 01 40 0a 00 08 00 84
<4>[ 1566.840447] iTEST: . . . . . . 6 . @ . . . .
<4>[ 1566.867543] oTEST: 09 10 00 00
<4>[ 1566.870656] oTEST: . . .
<4>[ 1566.892062] iTEST: 0e 0a 01 09 10 00 d2 91 50 dd 09 00 00
<4>[ 1566.897522] iTEST: . . . . . . . . P . . .
<4>[ 1566.921882] oTEST: 23 0c 00 00
<4>[ 1566.924996] oTEST: . . .
<4>[ 1566.958015] iTEST: 0e 07 01 23 0c 00 00 00 00 ff
<4>[ 1566.962695] iTEST: . . . . . . . . .
<4>[ 1566.991823] oTEST: 14 0c 00 00
<4>[ 1566.994936] oTEST: . . .
<4>[ 1567.022866] iTEST: 0e fc 01 14 0c 00 42 54 32 2e 30 00 00 00 00 00
<4>[ 1567.029106] iTEST: . . . . . . B T 2 . 0 . . . . .
<4>[ 1567.035346] iTEST: 08
<4>[ 1567.037686] iTEST:
... followed by more ....

And what do i see ....
An call for opcode 0x14 0xC
Followed by a successfull response containing the usbdevice name...

There is a difference in the call 0x14 0x0c 0x00 0x00 (triggerd from btenable) [successfull]
and 0x14 0x0c 0x00 0x01 (triggerd from hcitool) [failing]
 

·
Registered
Joined
·
130 Posts
I noticed that one of the BT dongles I've tested often doesn't get the hci0 interface even up on the tablet. Sometimes it does get up, but I get no call to btusb_intr_complete after sending a data packet with hcitool cmd.

lsusb shows Bus 003 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

On the laptop, the dongle works fine with the same hcitool cmds.

The other dongle gives consistently the kind of answer I've reported.
 

·
Registered
Joined
·
106 Posts
I don't think the difference between 14 0c 00 01 and 14 0c 00 00 (i.e. with the fourth byte) is relevant, as the length is only three bytes as output by my debug output (both on 3.0 kernel and the android kernel):

BT_DBG("%s skb len: 0x%x", hdev->name, skb->len);

in btusb_send_frame().
The 4ft byte is a bug in my debugging code

so on all lines the last byte is bogus.
 

·
Registered
Joined
·
130 Posts
I think I'm having some progress. I did an experiment on the laptop. I added the following to btusb_send_frame before usb_fill_control_urb():

Code:
<br />
		if ((skb->data[0] == 0x14) <br />
		    && (skb->data[1] == 0x0c)) {<br />
		  skb->data[0] = 0x01;<br />
		  skb->data[1] = 0x14;<br />
		}<br />
In other words, opcode 0xc14 is changed to opcode 0x1401 before sending to the USB device.

With this mod, the result is essentially the same on the laptop as on the tablet with the unmodified code:

Code:
<br />
# hcitool cmd 0x3 0x14<br />
< HCI Command: ogf 0x03, ocf 0x0014, plen 0<br />
> HCI Event: 0x0e plen 8<br />
  01 01 14 12 16 0C 00 00 <br />
# hcitool cmd 0x3 0x14<br />
< HCI Command: ogf 0x03, ocf 0x0014, plen 0<br />
> HCI Event: 0x0e plen 8<br />
  01 01 14 12 01 14 00 00 <br />
From the tablet I've got:
Code:
<br />
01 01 14 12 0C 01 00 00 <br />
01 01 14 12 03 00 00 00 <br />
The bytes 4 and 5 seem to vary, seemingly at random - both on the laptop with the modified code and the tablet with the unmodified code.

Update: To rule out (or in) the issue being endianness, I tried also:

Code:
<br />
		  skb->data[0] = 0x0c;<br />
		  skb->data[1] = 0x14;<br />
The answer was:

Code:
<br />
> HCI Event: 0x0e plen 4<br />
  01 0C 14 01 <br />
which I take as ruling out endianness being the issue.

So, I guess I'm presenting a hypothesis that something does the equivalent of the above (topmost) experimental laptop code on the tablet, changing the opcode 0xc14 (which it is when entering btusb_send_frame) into 0x1401 before being sent to the USB dongle. Perhaps the inline function usb_fill_control_urb works incorrectly for some reason (struct urb different?). Or, looking at the results from tablet experiments, the generic change is 0xc?? -> 0x??01.

Perhaps some other structure is different and data gets corrupted at USB code. Perhaps the problem is in struct skbuff or skbuff handling, that seems relatively complicated, though I'm not sure how the skbuff includes would step in after usb_fill_control_urb is called by btusb.c and the USB code processes the URB to send the data to the USB device.

I think an important clue is also that when called from the HCI code, things work correctly. But I don't know yet why that happens.

Update2: One clue is this might be an off-by-one error (perhaps in some kind of skbuff handling (peeking at skbuff)):

The generic form of the experimental laptop code is:

Code:
<br />
		  skb->data[1] = skb->data[0];<br />
		  skb->data[0] = 0x01;<br />
It seems from your debug output that skb->data[-1] already contains 0x01 as cmdnr, so what's going on might be some code somewhere writing data off by one byte. I don't grok the skbuff handling code, but there are some peek macros, one guess for the reason which comes to mind is the skbuff code peeks at the bytes 0x01 0x14 0x0c, then for some reason writes them back but one byte in the wrong place, resulting in 0x01 0x01 0x14 which then gets sent into the USB device. A confirmable fact does seem to be that what we see looks like the answer to 0x01 0x01 0x14 instead of the answer to 0x01 0x14 0x0c.
 

·
Registered
Joined
·
106 Posts
Of course skbuff or something alike could be wrong or one byte off as you say.
In my kernel the hci parts are already compiled in, so i'm assuming the hci data parts are correct (of course there could still be a difference with my compiled btusb)

Sumary of my tests

[A]
During registration/initialization of the btusb module, there are various calls from inside hci_init_req (in hci_core.c) and there are all successfull (one of the calls is OP_READ_LOCAL_NAME)

Checking the outgoing data of the OP_READ_LOCAL_NAME in the debugging part of btusb_send_frame (in btusb.c) the content of skb->data and urb->transfer_buffer are identical.
And there is the resulting name data in the receiving part

[B[
When doing the same OP_READ_LOCAL_NAME from userspace with the hcitool cmd, the debuging of btusb_send_frame again show the same data for skb->data and urb->transfer_buffer
and the data is also the same as the data of [A]. but there is not the expected response.

I created a simple userspace program that writes the command string to the hci device (same result/failure as with hcitool cmd)
- it works on pc
- it doesnt work on android

[C]
I also created an testmodule that opens hci device and does a hci_send_cmd call for OP_READ_LOCAL_NAME (using only hci calls) and that also work (after trying userspace)

notes
- If there would be a corruption of urb/skbuf/etc after btusb , shouldnt the corruption apply to both paths. [A and B]
- The curruption only seems to occure when calling from userspace
- Same data going out of btusb_send_frame should result in same data receiving .... [if everything else is the same]

To me it looks more like that calling hci from userspace is corrupting the device or some buffers or initializing it incorrectly.

PS my next test is if i can dump the whole contents of the urb and compare the successfull [A] ones with the failing ones

Update 1:
content of all urb structure variables [a] is identical to content of urb structure variables
content of urb->dev (usb_device) [a] is identical to content of urb->dev (except for the urb->dev->active_duration (with i assume counts the nr of sec the device is up)
 

·
Registered
Joined
·
130 Posts
(A)
During registration/initialization of the btusb module, there are various calls from inside hci_init_req (in hci_core.c) and there are all successfull (one of the calls is OP_READ_LOCAL_NAME)
Same thing happens for me, too, all of the calls seem to be succesful.

(

When doing the same OP_READ_LOCAL_NAME from userspace with the hcitool cmd, the debuging of btusb_send_frame again show the same data for skb->data and urb->transfer_buffer
and the data is also the same as the data of (A). but there is not the expected response.

I created a simple userspace program that writes the command string to the hci device (same result/failure as with hcitool cmd)
- it works on pc
- it doesnt work on android

(C)
I also created an testmodule that opens hci device and does a hci_send_cmd call for OP_READ_LOCAL_NAME (using only hci calls) and that also work (after trying userspace)

notes
- If there would be a corruption of urb/skbuf/etc after btusb , shouldnt the corruption apply to both paths. (A and
Yes, unless being called from user side somehow is the trigger for the corruption.

Quite interesting that making the call from a test module will cause a succesful operation.

- The curruption only seems to occure when calling from userspace
- Same data going out of btusb_send_frame should result in same data receiving .... [if everything else is the same]

To me it looks more like that calling hci from userspace is corrupting the device or some buffers or initializing it incorrectly.
Well, it does appear to be related to it, but when we look at the logs and timing, the corruption happens after btusb_send_frame() passes the URB to usb code. And the hci code is the one which is calling the btusb_send_frame code. So corruption happens _after_ hci code has handled the packet. But it does seem that the fault mode is entered after return from the hci open. Your test with the test module seems to rule out the problem being the hci device going into failure mode right after opening. (when returning to user mode from open).

OK, we agreed that calling the get local name opcode from usermode behaves differently than when called from kernel module (hci open). Then again, isn't it true the usermode hcitool cmd of calling btusb also goes via the kernel HCI code too (module bluetooth.ko for me, kernel-internal code for you)? So, one approach is to see what is different between the code path from your simple test module doing the call and the normal HCI data interface - perhaps that would give a hint of what might get wrongly initialized or corrupted with the code path taken when using hcitool cmd or your user-mode test program.
 

·
Registered
Joined
·
106 Posts
check this out

[email protected]:/home/dave# adb shell hcitool cmd 0x3 0x14
< HCI Command: ogf 0x03, ocf 0x0014, plen 0
> HCI Event: 0x0e plen 252
01 14 0C 00 42 54 32 2E 30 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00

After debugging and checking every piece of data that goes out through btusb.ko I was unable to find any difference between data send from kernel space and data send from user space
- skbuff, hci_device, usb_device, urb's, etc every single byte of data was identical. But still sending from kernel space works and sending from user space fails.

So what else could be different ?
Answer: the source of the data or more exact the type of allocated memory
- when send from kernelspace (by hci_init_req in hci_core.c) all memory is allocac inside the kernel
- when send from userspace (by hcitool) the interface between kernel and userspace is done by network sockets and the networksocket databuffers are allocated by the C-Library bionic (in userspace)

So i tried de following

btusb.c
Code:
<br />
static int btusb_send_frame(struct sk_buff *skb)<br />
{<br />
        struct hci_dev *hdev = (struct hci_dev *) skb->dev;<br />
        struct btusb_data *data = hdev->driver_data;<br />
        struct usb_ctrlrequest *dr;<br />
        struct urb *urb;<br />
        unsigned int pipe;<br />
        int err;<br />
[b][color="#FF0000"]<br />
        unsigned char *buffer;<br />
[/color][/b]<br />
<br />
        BT_DBG("send_frame: %s\n", hdev->name);<br />
<br />
        if (!test_bit(HCI_RUNNING, &hdev->flags))<br />
                return -EBUSY;<br />
<br />
[b][color="#FF0000"]<br />
        buffer=NULL;<br />
[/color][/b]<br />
<br />
        switch (bt_cb(skb)->pkt_type) {<br />
        case HCI_COMMAND_PKT:<br />
[b][color="#FF0000"]<br />
                buffer=kmalloc(skb->len,GFP_ATOMIC);<br />
                if(buffer==NULL) return -ENOMEM;<br />
                memcpy(buffer,skb->data,skb->len);<br />
[/color][/b]<br />
<br />
                urb = usb_alloc_urb(0, GFP_ATOMIC);<br />
                if (!urb)<br />
                        return -ENOMEM;<br />
<br />
                dr = kmalloc(sizeof(*dr), GFP_ATOMIC);<br />
                if (!dr) {<br />
                        usb_free_urb(urb);<br />
                        return -ENOMEM;   <br />
                }<br />
<br />
                dr->bRequestType = data->cmdreq_type;<br />
                dr->bRequest     = 0;<br />
                dr->wIndex       = 0;<br />
                dr->wValue       = 0;<br />
                dr->wLength      = __cpu_to_le16(skb->len);<br />
<br />
                pipe = usb_sndctrlpipe(data->udev, 0x00);<br />
[b][color="#FF0000"]<br />
//              usb_fill_control_urb(urb, data->udev, pipe, (void *) dr, skb->data, skb->len, btusb_tx_complete, <br />
                usb_fill_control_urb(urb, data->udev, pipe, (void *) dr, buffer, skb->len, btusb_tx_complete, skb<br />
[/color][/b]<br />
                hdev->stat.cmd_tx++;<br />
                break;<br />
<br />
... snip ...<br />
<br />
skip_waking:<br />
        usb_anchor_urb(urb, &data->tx_anchor);<br />
        err = usb_submit_urb(urb, GFP_ATOMIC);<br />
        if (err < 0) <br />
        {<br />
                BT_ERR("%s urb %p submission failed", hdev->name, urb);<br />
                kfree(urb->setup_packet);<br />
                usb_unanchor_urb(urb);   <br />
        }<br />
        else<br />
        {   <br />
                usb_mark_last_busy(data->udev);<br />
        }<br />
<br />
        [b][color="#FF0000"]if(buffer!=NULL) kfree(buffer);[/color][/b]<br />
        usb_free_urb(urb);<br />
done:<br />
        return err;<br />
}<br />
Why does this work ?
I'm assuming that the DWCOTG usbhost controler has some specific requirements for the URB memory like one or more of the following
- kernel space alocated
- wordt alligned
- allocated in lower address space
- etc..

I'm also assuming that the DWCOTG drivers is supposed to handle this correct (re)allocation stuf before starting dma transfers.
And if you start looking for DWCOTG kernel source you file quite a few bugs/patches concerning dma memory allocation and alingment issues.

As we cant change/modifie the usbhost parts, we must try to fix in in the area's we can modify (for me this has to be btusb.ko)

jkpjj: can you check / confirm that the above reallocation hack works for hcitool cmd 0x3 0x14 on your side ?.

PS If it works the other parts (see switch) needs fixing to.
 
1 - 20 of 38 Posts
Top