* [Bug 216817] btusb device with ID 0489:e0d0 no longer working after v6.0
2022-12-18 4:28 [Bug 216817] New: btusb device with ID 0489:e0d0 no longer working after v6.0 bugzilla-daemon
@ 2022-12-18 4:30 ` bugzilla-daemon
2022-12-19 8:33 ` bugzilla-daemon
` (11 subsequent siblings)
12 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2022-12-18 4:30 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=216817
--- Comment #1 from Andrew M (quantumphazor@gmail.com) ---
Created attachment 303421
--> https://bugzilla.kernel.org/attachment.cgi?id=303421&action=edit
output of lsusb -v -d 0489:e0d0
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 216817] btusb device with ID 0489:e0d0 no longer working after v6.0
2022-12-18 4:28 [Bug 216817] New: btusb device with ID 0489:e0d0 no longer working after v6.0 bugzilla-daemon
2022-12-18 4:30 ` [Bug 216817] " bugzilla-daemon
@ 2022-12-19 8:33 ` bugzilla-daemon
2022-12-19 10:55 ` bugzilla-daemon
` (10 subsequent siblings)
12 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2022-12-19 8:33 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=216817
The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |regressions@leemhuis.info
--- Comment #2 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) ---
FWIW, there is a fix for that patch that might or might not be related to your
problem (I'm not a bluetooth developer):
https://lore.kernel.org/all/20221206012323.3684462-1-luiz.dentz@gmail.com/
You also might want to check if 6.1 works, as some fixes are not backported --
and 6.0 will likely be soon EOL anyway
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 216817] btusb device with ID 0489:e0d0 no longer working after v6.0
2022-12-18 4:28 [Bug 216817] New: btusb device with ID 0489:e0d0 no longer working after v6.0 bugzilla-daemon
2022-12-18 4:30 ` [Bug 216817] " bugzilla-daemon
2022-12-19 8:33 ` bugzilla-daemon
@ 2022-12-19 10:55 ` bugzilla-daemon
2022-12-19 21:06 ` bugzilla-daemon
` (9 subsequent siblings)
12 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2022-12-19 10:55 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=216817
--- Comment #3 from Andrew M (quantumphazor@gmail.com) ---
Unfortunately it sill fails with 6.1 from Arch testing and a latest git pull
(6.1.r13139.gf9ff5644bcc0) which both include that change.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 216817] btusb device with ID 0489:e0d0 no longer working after v6.0
2022-12-18 4:28 [Bug 216817] New: btusb device with ID 0489:e0d0 no longer working after v6.0 bugzilla-daemon
` (2 preceding siblings ...)
2022-12-19 10:55 ` bugzilla-daemon
@ 2022-12-19 21:06 ` bugzilla-daemon
2022-12-19 21:10 ` bugzilla-daemon
` (8 subsequent siblings)
12 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2022-12-19 21:06 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=216817
Luiz Von Dentz (luiz.dentz@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |luiz.dentz@gmail.com
--- Comment #4 from Luiz Von Dentz (luiz.dentz@gmail.com) ---
Looks like the command that is failing is HCI_OP_LE_READ_BUFFER_SIZE_V2:
#define HCI_OP_LE_READ_BUFFER_SIZE_V2 0x2060
Looks like the controller is marking as supported but in fact it doesn't:
/* Use Read LE Buffer Size V2 if supported */
if (hdev->commands[41] & 0x20)
return __hci_cmd_sync_status(hdev,
HCI_OP_LE_READ_BUFFER_SIZE_V2,
0, NULL, HCI_CMD_TIMEOUT);
So either we introduce a quirk that must be set by the driver or we fallback to
HCI_OP_LE_READ_BUFFER_SIZE if HCI_OP_LE_READ_BUFFER_SIZE_V2 is not supported,
the later perhaps save us more time detecting this broken behavior since some
manufacturers don't seem to even care to qualify their controllers.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 216817] btusb device with ID 0489:e0d0 no longer working after v6.0
2022-12-18 4:28 [Bug 216817] New: btusb device with ID 0489:e0d0 no longer working after v6.0 bugzilla-daemon
` (3 preceding siblings ...)
2022-12-19 21:06 ` bugzilla-daemon
@ 2022-12-19 21:10 ` bugzilla-daemon
2022-12-19 21:13 ` [Bug,216817] " bluez.test.bot
2022-12-20 3:25 ` [Bug 216817] " bugzilla-daemon
` (7 subsequent siblings)
12 siblings, 1 reply; 15+ messages in thread
From: bugzilla-daemon @ 2022-12-19 21:10 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=216817
--- Comment #5 from Luiz Von Dentz (luiz.dentz@gmail.com) ---
(In reply to Andrew M from comment #3)
> Unfortunately it sill fails with 6.1 from Arch testing and a latest git pull
> (6.1.r13139.gf9ff5644bcc0) which both include that change.
Can you try with the following patch:
diff --git a/net/bluetooth/hci_sync.c b/net/bluetooth/hci_sync.c
index 5220bfd75b00..b3676b899647 100644
--- a/net/bluetooth/hci_sync.c
+++ b/net/bluetooth/hci_sync.c
@@ -3572,7 +3572,7 @@ static const struct hci_init_stage hci_init2[] = {
static int hci_le_read_buffer_size_sync(struct hci_dev *hdev)
{
/* Use Read LE Buffer Size V2 if supported */
- if (hdev->commands[41] & 0x20)
+ if (iso_capable(hdev) && hdev->commands[41] & 0x20)
return __hci_cmd_sync_status(hdev,
HCI_OP_LE_READ_BUFFER_SIZE_V2,
0, NULL, HCI_CMD_TIMEOUT);
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply related [flat|nested] 15+ messages in thread* [Bug 216817] btusb device with ID 0489:e0d0 no longer working after v6.0
2022-12-18 4:28 [Bug 216817] New: btusb device with ID 0489:e0d0 no longer working after v6.0 bugzilla-daemon
` (4 preceding siblings ...)
2022-12-19 21:10 ` bugzilla-daemon
@ 2022-12-20 3:25 ` bugzilla-daemon
2022-12-20 20:25 ` bugzilla-daemon
` (6 subsequent siblings)
12 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2022-12-20 3:25 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=216817
--- Comment #6 from Andrew M (quantumphazor@gmail.com) ---
(In reply to Luiz Von Dentz from comment #5)
> Can you try with the following patch
Thanks for the quick response. Tried the patch and it has solved the problem
for me on both 6.1.0 and git.
I hope it makes it into 6.1.1
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 216817] btusb device with ID 0489:e0d0 no longer working after v6.0
2022-12-18 4:28 [Bug 216817] New: btusb device with ID 0489:e0d0 no longer working after v6.0 bugzilla-daemon
` (5 preceding siblings ...)
2022-12-20 3:25 ` [Bug 216817] " bugzilla-daemon
@ 2022-12-20 20:25 ` bugzilla-daemon
2022-12-21 11:19 ` bugzilla-daemon
` (5 subsequent siblings)
12 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2022-12-20 20:25 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=216817
--- Comment #7 from Luiz Von Dentz (luiz.dentz@gmail.com) ---
(In reply to Andrew M from comment #6)
> (In reply to Luiz Von Dentz from comment #5)
> > Can you try with the following patch
>
> Thanks for the quick response. Tried the patch and it has solved the problem
> for me on both 6.1.0 and git.
> I hope it makes it into 6.1.1
Please test with the latest version:
https://patchwork.kernel.org/project/bluetooth/patch/20221219234945.3733741-1-luiz.dentz@gmail.com/
It turns out the features are not ready if we don't change the command sequence
so iso_capable would always evaluate to false.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 216817] btusb device with ID 0489:e0d0 no longer working after v6.0
2022-12-18 4:28 [Bug 216817] New: btusb device with ID 0489:e0d0 no longer working after v6.0 bugzilla-daemon
` (6 preceding siblings ...)
2022-12-20 20:25 ` bugzilla-daemon
@ 2022-12-21 11:19 ` bugzilla-daemon
2023-01-11 19:44 ` bugzilla-daemon
` (4 subsequent siblings)
12 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2022-12-21 11:19 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=216817
--- Comment #8 from Andrew M (quantumphazor@gmail.com) ---
(In reply to Luiz Von Dentz from comment #7)
> (In reply to Andrew M from comment #6)
> > (In reply to Luiz Von Dentz from comment #5)
> > > Can you try with the following patch
> >
> > Thanks for the quick response. Tried the patch and it has solved the
> problem
> > for me on both 6.1.0 and git.
> > I hope it makes it into 6.1.1
>
> Please test with the latest version:
>
> https://patchwork.kernel.org/project/bluetooth/patch/20221219234945.3733741-
> 1-luiz.dentz@gmail.com/
>
> It turns out the features are not ready if we don't change the command
> sequence so iso_capable would always evaluate to false.
Still works. Tested v6.1 and 6.1.r13872.gb6bb9676f216
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 216817] btusb device with ID 0489:e0d0 no longer working after v6.0
2022-12-18 4:28 [Bug 216817] New: btusb device with ID 0489:e0d0 no longer working after v6.0 bugzilla-daemon
` (7 preceding siblings ...)
2022-12-21 11:19 ` bugzilla-daemon
@ 2023-01-11 19:44 ` bugzilla-daemon
2023-01-11 19:44 ` bugzilla-daemon
` (3 subsequent siblings)
12 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2023-01-11 19:44 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=216817
Mario Limonciello (AMD) (mario.limonciello@amd.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mario.limonciello@amd.com
--- Comment #9 from Mario Limonciello (AMD) (mario.limonciello@amd.com) ---
As this completely broke bluetooth for a number of people, can you please
consider this to be sent up to 6.2-rc in a fixes PR rather than waiting for 6.3
and
Cc: stable@vger.kernel.org # 6.1
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 216817] btusb device with ID 0489:e0d0 no longer working after v6.0
2022-12-18 4:28 [Bug 216817] New: btusb device with ID 0489:e0d0 no longer working after v6.0 bugzilla-daemon
` (8 preceding siblings ...)
2023-01-11 19:44 ` bugzilla-daemon
@ 2023-01-11 19:44 ` bugzilla-daemon
2023-01-16 13:29 ` bugzilla-daemon
` (2 subsequent siblings)
12 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2023-01-11 19:44 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=216817
Mario Limonciello (AMD) (mario.limonciello@amd.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
URL| |https://bugzilla.redhat.com
| |/show_bug.cgi?id=2149136
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 216817] btusb device with ID 0489:e0d0 no longer working after v6.0
2022-12-18 4:28 [Bug 216817] New: btusb device with ID 0489:e0d0 no longer working after v6.0 bugzilla-daemon
` (9 preceding siblings ...)
2023-01-11 19:44 ` bugzilla-daemon
@ 2023-01-16 13:29 ` bugzilla-daemon
2023-01-17 19:22 ` bugzilla-daemon
2023-01-26 16:21 ` bugzilla-daemon
12 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2023-01-16 13:29 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=216817
--- Comment #10 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) ---
(In reply to Mario Limonciello (AMD) from comment #9)
> As this completely broke bluetooth for a number of people,
Did it? Ohh, interesting.
> can you please
> consider this to be sent up to 6.2-rc in a fixes PR rather than waiting for
> 6.3 and
>
> Cc: stable@vger.kernel.org # 6.1
Luiz, that sounds like a reasonable request. Did you work on that front?
Doesn't look like it from here, but maybe I missed something.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 216817] btusb device with ID 0489:e0d0 no longer working after v6.0
2022-12-18 4:28 [Bug 216817] New: btusb device with ID 0489:e0d0 no longer working after v6.0 bugzilla-daemon
` (10 preceding siblings ...)
2023-01-16 13:29 ` bugzilla-daemon
@ 2023-01-17 19:22 ` bugzilla-daemon
2023-01-26 16:21 ` bugzilla-daemon
12 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2023-01-17 19:22 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=216817
--- Comment #11 from Luiz Von Dentz (luiz.dentz@gmail.com) ---
Sorry for late reply, long weekend here, I will create a pull request for net
so hopefully this get in the next rc.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 15+ messages in thread* [Bug 216817] btusb device with ID 0489:e0d0 no longer working after v6.0
2022-12-18 4:28 [Bug 216817] New: btusb device with ID 0489:e0d0 no longer working after v6.0 bugzilla-daemon
` (11 preceding siblings ...)
2023-01-17 19:22 ` bugzilla-daemon
@ 2023-01-26 16:21 ` bugzilla-daemon
12 siblings, 0 replies; 15+ messages in thread
From: bugzilla-daemon @ 2023-01-26 16:21 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=216817
Mario Limonciello (AMD) (mario.limonciello@amd.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |CODE_FIX
--- Comment #12 from Mario Limonciello (AMD) (mario.limonciello@amd.com) ---
As this is upstreamed as of 6.2-rc5 (3a4d29b6d631b ("Bluetooth: hci_sync: Fix
use HCI_OP_LE_READ_BUFFER_SIZE_V2")) closing this issue.
The fix should trickle into 6.1.y as well.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 15+ messages in thread