Hi Luiz, > The invalid SCO handle error is normally caused by a race in the USB > transport where the data and event happen to be 2 different endpoints > so the event carrying the SCO handle is processed after its data. > > Note: This can probably be resolved with use of force_poll_sync > debugfs. > > Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx> > --- > net/bluetooth/hci_core.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) patch has been applied to bluetooth-next tree. Regards Marcel