With an AX210 card I get "Failed to send firmware data (-38)" on linux-next
from Dec 4th in case of a cold-boot after power-cycle.
"hk: bt code = 0x001f" is a private debug message to check which BT code
is mapped to ENOSYS (-38). From what I found 0x1f is "Unspecified error".
The second attempt to load the firmware is successful then.
[ 4.192718] Bluetooth: Core ver 2.22
[ 4.192756] Bluetooth: Starting self testing
[ 4.192785] Bluetooth: Finished self testing
[ 4.192937] Bluetooth: HCI device and connection manager initialized
[ 4.193067] Bluetooth: HCI socket layer initialized
[ 4.193108] Bluetooth: L2CAP socket layer initialized
[ 4.193195] Bluetooth: SCO socket layer initialized
[ 4.242342] Bluetooth: hci0: Device revision is 0
[ 4.242435] Bluetooth: hci0: Secure boot is enabled
[ 4.242495] Bluetooth: hci0: OTP lock is enabled
[ 4.242533] Bluetooth: hci0: API lock is enabled
[ 4.242570] Bluetooth: hci0: Debug lock is disabled
[ 4.242609] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 4.242657] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
[ 4.261977] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
[ 4.855813] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 4.855873] Bluetooth: BNEP socket layer initialized
[ 5.819388] Bluetooth: hk: bt code = 0x001f
[ 5.819438] Bluetooth: hci0: Failed to send firmware data (-38)
[ 5.820069] Bluetooth: hci0: Intel reset sent to retry FW download
[ 6.362248] Bluetooth: hci0: Device revision is 0
[ 6.362384] Bluetooth: hci0: Secure boot is enabled
[ 6.362439] Bluetooth: hci0: OTP lock is enabled
[ 6.362551] Bluetooth: hci0: API lock is enabled
[ 6.362605] Bluetooth: hci0: Debug lock is disabled
[ 6.362660] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 6.362726] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
[ 6.364508] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
[ 9.020540] Bluetooth: hci0: Waiting for firmware download to complete
[ 9.021443] Bluetooth: hci0: Firmware loaded in 2599136 usecs
[ 9.022778] Bluetooth: hci0: Waiting for device to boot
[ 9.050099] Bluetooth: hci0: Device booted in 27723 usecs
[ 9.052633] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0041-0041.ddc
[ 9.055224] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 9.060184] Bluetooth: hci0: Firmware timestamp 2020.42 buildtype 1 build 15791
Hi Heiner Kallweit,
Please provide more information test environment.
1. cat /proc/cpuinfo
2. Is this an intermittent issue ?
3. Are you using any specific distro ?
I didn't observe any such issue on my system.
Thanks,
Kiran
> -----Original Message-----
> From: Heiner Kallweit <[email protected]>
> Sent: Tuesday, December 8, 2020 1:26 AM
> To: K, Kiran <[email protected]>; Marcel Holtmann <[email protected]>
> Cc: BlueZ development <[email protected]>
> Subject: linux-next-2020-12-04: Failed to send firmware data (-38) with AX210
>
> With an AX210 card I get "Failed to send firmware data (-38)" on linux-next
> from Dec 4th in case of a cold-boot after power-cycle.
>
> "hk: bt code = 0x001f" is a private debug message to check which BT code is
> mapped to ENOSYS (-38). From what I found 0x1f is "Unspecified error".
>
> The second attempt to load the firmware is successful then.
>
>
> [ 4.192718] Bluetooth: Core ver 2.22
> [ 4.192756] Bluetooth: Starting self testing
> [ 4.192785] Bluetooth: Finished self testing
> [ 4.192937] Bluetooth: HCI device and connection manager initialized
> [ 4.193067] Bluetooth: HCI socket layer initialized
> [ 4.193108] Bluetooth: L2CAP socket layer initialized
> [ 4.193195] Bluetooth: SCO socket layer initialized
> [ 4.242342] Bluetooth: hci0: Device revision is 0
> [ 4.242435] Bluetooth: hci0: Secure boot is enabled
> [ 4.242495] Bluetooth: hci0: OTP lock is enabled
> [ 4.242533] Bluetooth: hci0: API lock is enabled
> [ 4.242570] Bluetooth: hci0: Debug lock is disabled
> [ 4.242609] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
> [ 4.242657] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1
> build 38
> [ 4.261977] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
> [ 4.855813] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> [ 4.855873] Bluetooth: BNEP socket layer initialized
> [ 5.819388] Bluetooth: hk: bt code = 0x001f
> [ 5.819438] Bluetooth: hci0: Failed to send firmware data (-38)
> [ 5.820069] Bluetooth: hci0: Intel reset sent to retry FW download
> [ 6.362248] Bluetooth: hci0: Device revision is 0
> [ 6.362384] Bluetooth: hci0: Secure boot is enabled
> [ 6.362439] Bluetooth: hci0: OTP lock is enabled
> [ 6.362551] Bluetooth: hci0: API lock is enabled
> [ 6.362605] Bluetooth: hci0: Debug lock is disabled
> [ 6.362660] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
> [ 6.362726] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1
> build 38
> [ 6.364508] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
> [ 9.020540] Bluetooth: hci0: Waiting for firmware download to complete
> [ 9.021443] Bluetooth: hci0: Firmware loaded in 2599136 usecs
> [ 9.022778] Bluetooth: hci0: Waiting for device to boot
> [ 9.050099] Bluetooth: hci0: Device booted in 27723 usecs
> [ 9.052633] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0041-
> 0041.ddc
> [ 9.055224] Bluetooth: hci0: Applying Intel DDC parameters completed
> [ 9.060184] Bluetooth: hci0: Firmware timestamp 2020.42 buildtype 1 build
> 15791
Am 09.12.2020 um 01:40 schrieb K, Kiran:
> Hi Heiner Kallweit,
>
Hi Kiran,
thanks for following up.
> Please provide more information test environment.
>
> 1. cat /proc/cpuinfo
For one of the four cores:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 92
model name : Intel(R) Celeron(R) CPU N3450 @ 1.10GHz
stepping : 9
microcode : 0x40
cpu MHz : 1093.748
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 21
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl est tm2 ssse3 sdbg cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave rdrand lahf_lm 3dnowprefetch cpuid_fault cat_l2 ibrs ibpb stibp fsgsbase tsc_adjust smep erms mpx rdt_a rdseed smap clflushopt intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts md_clear arch_capabilities
bugs : monitor spectre_v1 spectre_v2
bogomips : 2188.80
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:
> 2. Is this an intermittent issue ?
No, it's perfectly reproducible. Happens always after a power cycle.
I don' think it's related to the following, but I'd like to mention
it nevertheless. After each reboot (not only after power cycle) the
WiFi PCI device is missing. Therefore I have to reboot with
reboot=pci. See also bug 202399 in kernel bugzilla.
> 3. Are you using any specific distro ?
>
Arch, headless
> I didn't observe any such issue on my system.
>
> Thanks,
> Kiran
>
Heiner
>
>> -----Original Message-----
>> From: Heiner Kallweit <[email protected]>
>> Sent: Tuesday, December 8, 2020 1:26 AM
>> To: K, Kiran <[email protected]>; Marcel Holtmann <[email protected]>
>> Cc: BlueZ development <[email protected]>
>> Subject: linux-next-2020-12-04: Failed to send firmware data (-38) with AX210
>>
>> With an AX210 card I get "Failed to send firmware data (-38)" on linux-next
>> from Dec 4th in case of a cold-boot after power-cycle.
>>
>> "hk: bt code = 0x001f" is a private debug message to check which BT code is
>> mapped to ENOSYS (-38). From what I found 0x1f is "Unspecified error".
>>
>> The second attempt to load the firmware is successful then.
>>
>>
>> [ 4.192718] Bluetooth: Core ver 2.22
>> [ 4.192756] Bluetooth: Starting self testing
>> [ 4.192785] Bluetooth: Finished self testing
>> [ 4.192937] Bluetooth: HCI device and connection manager initialized
>> [ 4.193067] Bluetooth: HCI socket layer initialized
>> [ 4.193108] Bluetooth: L2CAP socket layer initialized
>> [ 4.193195] Bluetooth: SCO socket layer initialized
>> [ 4.242342] Bluetooth: hci0: Device revision is 0
>> [ 4.242435] Bluetooth: hci0: Secure boot is enabled
>> [ 4.242495] Bluetooth: hci0: OTP lock is enabled
>> [ 4.242533] Bluetooth: hci0: API lock is enabled
>> [ 4.242570] Bluetooth: hci0: Debug lock is disabled
>> [ 4.242609] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
>> [ 4.242657] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1
>> build 38
>> [ 4.261977] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
>> [ 4.855813] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
>> [ 4.855873] Bluetooth: BNEP socket layer initialized
>> [ 5.819388] Bluetooth: hk: bt code = 0x001f
>> [ 5.819438] Bluetooth: hci0: Failed to send firmware data (-38)
>> [ 5.820069] Bluetooth: hci0: Intel reset sent to retry FW download
>> [ 6.362248] Bluetooth: hci0: Device revision is 0
>> [ 6.362384] Bluetooth: hci0: Secure boot is enabled
>> [ 6.362439] Bluetooth: hci0: OTP lock is enabled
>> [ 6.362551] Bluetooth: hci0: API lock is enabled
>> [ 6.362605] Bluetooth: hci0: Debug lock is disabled
>> [ 6.362660] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
>> [ 6.362726] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1
>> build 38
>> [ 6.364508] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
>> [ 9.020540] Bluetooth: hci0: Waiting for firmware download to complete
>> [ 9.021443] Bluetooth: hci0: Firmware loaded in 2599136 usecs
>> [ 9.022778] Bluetooth: hci0: Waiting for device to boot
>> [ 9.050099] Bluetooth: hci0: Device booted in 27723 usecs
>> [ 9.052633] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0041-
>> 0041.ddc
>> [ 9.055224] Bluetooth: hci0: Applying Intel DDC parameters completed
>> [ 9.060184] Bluetooth: hci0: Firmware timestamp 2020.42 buildtype 1 build
>> 15791
>