On Thu, Apr 04, 2019 at 08:22:15PM +0530, Balakrishna Godavarthi wrote: > Hi Matthias, > > On 2019-04-03 21:44, Matthias Kaehlcke wrote: > > On Wed, Apr 03, 2019 at 11:53:26AM +0530, Balakrishna Godavarthi wrote: > > > + Harish to update his findings on wcn3998. > > > Mean time i will perform a regression to detect the failure. > > > > On my system it typically reproduces within a few dozen > > iterations. Make sure your tree doesn't contain any custom BT patches, > > even if they just add logging or fix the timeout during > > initialization. Since this problem is timing sensitive it might get > > masked. My tree is based on 4.19 LTS with all QCA BT related changes > > on top: > > https://chromium.googlesource.com/chromiumos/third_party/kernel/+/refs/heads/chromeos-4.19 > > > > I found some problems during initialization easier to reproduce > > when binding and unbinding the device through sysfs, instead of > > doing hciconfig up/down, this resembles more the initialization at > > boot time. > > > [Bala]: I am able to replicate this issue. > are you seeing the below error message getting logged on the console > in the issue case or an different error message. > Bluetooth: hci0: QCA TLV response size mismatch Yes, that's the error message. The size doesn't match because the driver expects a TLV response but gets a baud rate response.
