2023-01-15 20:53:26

by bugzilla-daemon

[permalink] [raw]
Subject: [Bug 216936] New: [REGRESSION] The first attempt to upload firmware for Intel Bluetooth fails

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

Bug ID: 216936
Summary: [REGRESSION] The first attempt to upload firmware for
Intel Bluetooth fails
Product: Drivers
Version: 2.5
Kernel Version: 6.1.6
Hardware: AMD
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Bluetooth
Assignee: [email protected]
Reporter: [email protected]
Regression: No

This looks like a new regression for kernel 6.1.6.

Kernel 6.1.4 and previous kernels didn't have the issue.

Hardware: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter

From dmesg:

Bluetooth: hci0: FW download error recovery failed (-19)
Bluetooth: hci0: sending frame failed (-19)
Bluetooth: hci0: Failed to read MSFT supported features (-19)

Full log:

Bluetooth: hci0: Found device firmware: intel/ibt-18-16-1.sfi
Bluetooth: hci0: Boot Address: 0x40800
Bluetooth: hci0: Firmware Version: 214-6.22
Bluetooth: hci0: FW download error recovery failed (-19)
Bluetooth: hci0: sending frame failed (-19)
Bluetooth: hci0: Failed to read MSFT supported features (-19)
Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015
Bluetooth: hci0: Device revision is 2
Bluetooth: hci0: Secure boot is enabled
Bluetooth: hci0: OTP lock is enabled
Bluetooth: hci0: API lock is enabled
Bluetooth: hci0: Debug lock is disabled
Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Bluetooth: hci0: Found device firmware: intel/ibt-18-16-1.sfi
Bluetooth: hci0: Boot Address: 0x40800
Bluetooth: hci0: Firmware Version: 214-6.22
Bluetooth: hci0: Waiting for firmware download to complete
Bluetooth: hci0: Firmware loaded in 1111205 usecs
Bluetooth: hci0: Waiting for device to boot
Bluetooth: hci0: Device booted in 14844 usecs
Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-18-16-1.ddc
Bluetooth: hci0: Applying Intel DDC parameters completed
Bluetooth: hci0: Firmware revision 0.1 build 214 week 6 2022

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

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


2023-01-15 22:34:23

by bugzilla-daemon

[permalink] [raw]
Subject: [Bug 216936] First attempt to upload firmware for Intel Bluetooth fails (a timing issue?)

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

Artem S. Tashkinov ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
Kernel Version|6.1.6 |6.1.4

--- Comment #2 from Artem S. Tashkinov ([email protected]) ---
I had these errors with 6.1.4 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.

2023-01-16 12:47:37

by bugzilla-daemon

[permalink] [raw]
Subject: [Bug 216936] First attempt to upload firmware for Intel Bluetooth fails (a timing issue?)

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

The Linux kernel's regression tracker (Thorsten Leemhuis) ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #3 from The Linux kernel's regression tracker (Thorsten Leemhuis) ([email protected]) ---
(In reply to Artem S. Tashkinov from comment #2)
> I had these errors with 6.1.4 as well.

But earlier series (e.g. 6.0.y) worked fine?

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

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

2023-01-17 06:02:05

by bugzilla-daemon

[permalink] [raw]
Subject: [Bug 216936] First attempt to upload firmware for Intel Bluetooth fails (a timing issue?)

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

Mario Limonciello (AMD) ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #4 from Mario Limonciello (AMD) ([email protected]) ---
> Kernel 6.1.4 and previous kernels didn't have the issue.
> I had these errors with 6.1.4 as well.

Which one is it?

If you can find a definitive kernel it really was working 100% of the time a
bisect would be ideal. But given the ambiguous result you indicated with
6.1.4, I suspect it's not really ever been 100% correct.

Perhaps turning on dynamic debugging for net/bluetooth would be helpful to
identify what about the sequence of init causes -ENODEV. Naively it looks to
me that the main reason this can get returned is if a command is issued while
the device is actively being unregistered.

So perhaps your userspace is racing?

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

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