Hi Loic, >> Seems there is a regression in bluetooth-next. >> I'm unable to communicate with my Intel WP chip via HCI User channel. >> To test user channel, I use bluemoon: >> $ hciconfig hci0 down >> $ bluemoon -i hci0 >> Bluemoon configuration utility ver 5.30 >> >> Then bluemoon hangs up, no HCI event... >> >> HCI packet seems successfully sent, but no HCI response: >> [ 491.525914] Bluetooth: hci0 >> [ 491.525918] Bluetooth: hci0 >> [ 491.525924] Bluetooth: hci0 >> [ 491.525927] Bluetooth: hci0 >> [ 491.525964] Bluetooth: hci0 >> [ 491.526114] Bluetooth: hci0 urb ffff8800c1f320c0 status 0 count 3 >> >> When I kill bluemoon, I get same kind of issue (cmd timeout): >> [ 895.603661] Bluetooth: hci0 urb ffff8802f89d5b40 status 0 count 3 >> [ 897.606323] Bluetooth: hci0 command 0xfc3f tx timeout >> [ 897.606350] Bluetooth: hci0 >> [ 897.607011] Bluetooth: hci0 urb ffff88030c2c83c0 status 0 count 244 >> [ 899.612007] Bluetooth: hci0 command 0x0c52 tx timeout >> >> After that, device still usable by other sockets (hciconfig, hcitool...) >> >> I wonder if you reproduce this issue on your side? > > can you git bisect this to pin point the patch that broke this for you. any chance you did git bisect this and tell us which patch broken this? Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
