[Bug 219365] USB bluetooth dongle stop working after upgrade from 6.11.1 to 6.11.2

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=219365

--- Comment #2 from Adilson Dantas (adilson@adilson.net.br) ---
I tested each commit with 6.11.2 and 6.12-rc2 and I have isolated the
regression at commit 8603daa4300b84abb3c68e48f3b607d7d5a2a207 


    Bluetooth: btusb: Fix not handling ZPL/short-transfer

    [ Upstream commit 7b05933340f4490ef5b09e84d644d12484b05fdf ]

Reverting this commit fix the regression on my BT dongle.


(In reply to Paul Menzel from comment #1)
> Thank you for your report, and great that you can build the Linux kernel
> yourself.
> 
> > Maybe is one or all commits has caused the regression on my BT dongle
> 
> It’d be great if you tested each of the three commits. (Normally, `git
> bisect start -- drivers/bluetooth/btusb.c net/bluetooth/`, and then `git
> bisect good v6.11.1` and `git bisect bad v6.11.2`, would do that
> automatically.)
> 
> If you already have git clone, then:
> 
>     git remote add stable
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>     git fetch stable
> 
> or, if you do not,
> 
>     git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> 
> Then
> 
>     git reset --hard f68f72d04b60d3af36b63b888fe084966bca07b9
> 
> build and test. If it does *not* work, it’s the fault commit.
> 
> Then
> 
>     git reset --hard 846a6fc7860119ee72737391856497b3fcf7c2b5
> 
> If it does *not* work, it’s the fault commit.
> 
> Then
> 
>     git reset --hard 8603daa4300b84abb3c68e48f3b607d7d5a2a207
> 
> If it does *not* work, it’s the fault commit.
> 
> It’d be also good to know, if it works with current Linux master branch, or
> 6.12-rc2.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.