Bug 215680 - iwlwifi: AX210: firmware crash when enabling bluetooth first
Summary: iwlwifi: AX210: firmware crash when enabling bluetooth first
Status: NEEDINFO
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless-intel (show other bugs)
Hardware: Intel Linux
: P1 normal
Assignee: Default virtual assignee for network-wireless-intel
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-14 00:23 UTC by Loïc Yhuel
Modified: 2022-03-21 17:59 UTC (History)
2 users (show)

See Also:
Kernel Version: 5.16.13-200.fc35.x86_64
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Loïc Yhuel 2022-03-14 00:23:58 UTC
If I enable (rfkill) the bluetooth first, there is a firmware error when enabling the wifi.
But if I enable the wifi first, I can then enable the bluetooth, and disabling/enabling the wifi works.

Laptop is Dell Latitude 5521 (TGL-H).

Boot :
iwlwifi 0000:71:00.0: enabling device (0000 -> 0002)
iwlwifi 0000:71:00.0: api flags index 2 larger than supported by driver
iwlwifi 0000:71:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.34
iwlwifi 0000:71:00.0: loaded firmware version 67.8f59b80b.0 ty-a0-gf-a0-67.ucode op_mode iwlmvm
iwlwifi 0000:71:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
iwlwifi 0000:71:00.0: reporting RF_KILL (radio disabled)
iwlwifi 0000:71:00.0: WRT: Failed to set DRAM buffer for alloc id 1, ret=-1
iwlwifi 0000:71:00.0: WRT: Failed to set DRAM buffer for alloc id 2, ret=-1
iwlwifi 0000:71:00.0: WRT: Failed to set DRAM buffer for alloc id 3, ret=-1
iwlwifi 0000:71:00.0: loaded PNVM version 05a8dfca
iwlwifi 0000:71:00.0: Detected RF GF, rfid=0x10d000
iwlwifi 0000:71:00.0: base HW address: 84:14:4d:fd:82:75
iwlwifi 0000:71:00.0 wlp113s0: renamed from wlan0

Bluetooth power on :
usb 3-14: new full-speed USB device number 7 using xhci_hcd
usb 3-14: New USB device found, idVendor=8087, idProduct=0032, bcdDevice= 0.00
usb 3-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Bluetooth: hci0: Device revision is 0
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: Bootloader timestamp 2019.40 buildtype 1 build 38
Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
Bluetooth: hci0: Boot Address: 0x100800
Bluetooth: hci0: Firmware Version: 132-5.22
Bluetooth: hci0: Waiting for firmware download to complete
Bluetooth: hci0: Firmware loaded in 1503418 usecs
Bluetooth: hci0: Waiting for device to boot
Bluetooth: hci0: Device booted in 27313 usecs
Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0041-0041.ddc
Bluetooth: hci0: Applying Intel DDC parameters completed
Bluetooth: hci0: Firmware timestamp 2022.5 buildtype 1 build 38020
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11

Wifi power on :
iwlwifi 0000:71:00.0: RF_KILL bit toggled to enable radio.
iwlwifi 0000:71:00.0: reporting RF_KILL (radio enabled)
iwlwifi 0000:71:00.0: WRT: Failed to set DRAM buffer for alloc id 1, ret=-1
iwlwifi 0000:71:00.0: WRT: Failed to set DRAM buffer for alloc id 2, ret=-1
iwlwifi 0000:71:00.0: WRT: Failed to set DRAM buffer for alloc id 3, ret=-1
iwlwifi 0000:71:00.0: SecBoot CPU1 Status: 0x7696, CPU2 Status: 0xb03
iwlwifi 0000:71:00.0: UMAC PC: 0x8047f8e0
iwlwifi 0000:71:00.0: LMAC PC: 0x0
iwlwifi 0000:71:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms).
iwlwifi 0000:71:00.0: Loaded firmware version: 67.8f59b80b.0 ty-a0-gf-a0-67.ucode
iwlwifi 0000:71:00.0: 0x00000000 | ADVANCED_SYSASSERT          
iwlwifi 0000:71:00.0: 0x00000000 | trm_hw_status0
iwlwifi 0000:71:00.0: 0x00000000 | trm_hw_status1
iwlwifi 0000:71:00.0: 0x00000000 | branchlink2
iwlwifi 0000:71:00.0: 0x00000000 | interruptlink1
iwlwifi 0000:71:00.0: 0x00000000 | interruptlink2
iwlwifi 0000:71:00.0: 0x00000000 | data1
iwlwifi 0000:71:00.0: 0x00000000 | data2
iwlwifi 0000:71:00.0: 0x00000000 | data3
iwlwifi 0000:71:00.0: 0x00000000 | beacon time
iwlwifi 0000:71:00.0: 0x00000000 | tsf low
iwlwifi 0000:71:00.0: 0x00000000 | tsf hi
iwlwifi 0000:71:00.0: 0x00000000 | time gp1
iwlwifi 0000:71:00.0: 0x00000000 | time gp2
iwlwifi 0000:71:00.0: 0x00000000 | uCode revision type
iwlwifi 0000:71:00.0: 0x00000000 | uCode version major
iwlwifi 0000:71:00.0: 0x00000000 | uCode version minor
iwlwifi 0000:71:00.0: 0x00000000 | hw version
iwlwifi 0000:71:00.0: 0x00000000 | board version
iwlwifi 0000:71:00.0: 0x00000000 | hcmd
iwlwifi 0000:71:00.0: 0x00000000 | isr0
iwlwifi 0000:71:00.0: 0x00000000 | isr1
iwlwifi 0000:71:00.0: 0x00000000 | isr2
iwlwifi 0000:71:00.0: 0x00000000 | isr3
iwlwifi 0000:71:00.0: 0x00000000 | isr4
iwlwifi 0000:71:00.0: 0x00000000 | last cmd Id
iwlwifi 0000:71:00.0: 0x00000000 | wait_event
iwlwifi 0000:71:00.0: 0x00000000 | l2p_control
iwlwifi 0000:71:00.0: 0x00000000 | l2p_duration
iwlwifi 0000:71:00.0: 0x00000000 | l2p_mhvalid
iwlwifi 0000:71:00.0: 0x00000000 | l2p_addr_match
iwlwifi 0000:71:00.0: 0x00000000 | lmpm_pmg_sel
iwlwifi 0000:71:00.0: 0x00000000 | timestamp
iwlwifi 0000:71:00.0: 0x00000000 | flow_handler
iwlwifi 0000:71:00.0: Start IWL Error Log Dump:
iwlwifi 0000:71:00.0: Transport status: 0x00000042, valid: 7
iwlwifi 0000:71:00.0: 0x201013F2 | ADVANCED_SYSASSERT
iwlwifi 0000:71:00.0: 0x00000000 | umac branchlink1
iwlwifi 0000:71:00.0: 0x8045E20E | umac branchlink2
iwlwifi 0000:71:00.0: 0x00000000 | umac interruptlink1
iwlwifi 0000:71:00.0: 0x00000000 | umac interruptlink2
iwlwifi 0000:71:00.0: 0x0000000C | umac data1
iwlwifi 0000:71:00.0: 0x00040000 | umac data2
iwlwifi 0000:71:00.0: 0xDEADBEEF | umac data3
iwlwifi 0000:71:00.0: 0x00000043 | umac major
iwlwifi 0000:71:00.0: 0x8F59B80B | umac minor
iwlwifi 0000:71:00.0: 0x000120AB | frame pointer
iwlwifi 0000:71:00.0: 0xC0887F34 | stack pointer
iwlwifi 0000:71:00.0: 0x00000000 | last host cmd
iwlwifi 0000:71:00.0: 0x00000000 | isr status reg
iwlwifi 0000:71:00.0: IML/ROM dump:
iwlwifi 0000:71:00.0: 0x00000B03 | IML/ROM error/state
iwlwifi 0000:71:00.0: 0x00007696 | IML/ROM data1
iwlwifi 0000:71:00.0: 0x00000080 | IML/ROM WFPM_AUTH_KEY_0
iwlwifi 0000:71:00.0: Fseq Registers:
iwlwifi 0000:71:00.0: 0x60000100 | FSEQ_ERROR_CODE
iwlwifi 0000:71:00.0: 0x00440005 | FSEQ_TOP_INIT_VERSION
iwlwifi 0000:71:00.0: 0x00080009 | FSEQ_CNVIO_INIT_VERSION
iwlwifi 0000:71:00.0: 0x0000A652 | FSEQ_OTP_VERSION
iwlwifi 0000:71:00.0: 0x00000002 | FSEQ_TOP_CONTENT_VERSION
iwlwifi 0000:71:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
iwlwifi 0000:71:00.0: 0x00400410 | FSEQ_CNVI_ID
iwlwifi 0000:71:00.0: 0x00400410 | FSEQ_CNVR_ID
iwlwifi 0000:71:00.0: 0x00400410 | CNVI_AUX_MISC_CHIP
iwlwifi 0000:71:00.0: 0x00400410 | CNVR_AUX_MISC_CHIP
iwlwifi 0000:71:00.0: 0x00009061 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
iwlwifi 0000:71:00.0: 0x00000061 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
iwlwifi 0000:71:00.0: Failed to start RT ucode: -110
iwlwifi 0000:71:00.0: Failed to start RT ucode: -110
...
Comment 1 The Linux kernel's regression tracker (Thorsten Leemhuis) 2022-03-17 13:45:44 UTC
Did this work with earlier Linux versions, like 5.15? I'm not involved in here, but FWIW: 5.16.16 will likely have a iwlwifi fix (https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.16/iwlwifi-don-t-advertise-twt-support.patch ), not sure if that might be related somehow, guess not. Maybe trying 5.17-rc might be a good idea.
Comment 2 Golan Ben Ami 2022-03-20 08:42:30 UTC
Hi,

This issue occurs due to a mutual SW component between WIFI and BT that seems to be not aligned on your machine.
Are you using default WIFI and BT versions from the auto installations?

Thanks,
Golan
Comment 3 Loïc Yhuel 2022-03-21 17:59:01 UTC
Hi,

I'm using the default files from linux-firmware-20220310-130.fc35.noarch / iwlax2xx-firmware-20220310-130.fc35.noarch, which match the current linux-firmware tree.

The bluetooth is using the latest ibt-0041-0041.sfi / ibt-0041-0041.ddc.
The wifi is using :
 - the -67 ucode (only 5.17 uses -68)
 - the latest iwlwifi-ty-a0-gf-a0.pnvm

I tried reverting to older ibt-0041-0041.sfi manually :
 - REL31878 works (this was the current version when the -67 ucode was added) !
 - REL34345 has the issue (this was committed between the -67 and the -68 ucode)
 - the original REL38020 has the issue

So if there are version dependencies, they aren't obvious.
With which ucode version would the REL34345 work ? And the current REL38020 ?

There is nothing which ensure the Wifi and BT versions are aligned, since the ucode is versioned, but the ibt-*.sfi aren't.

Note You need to log in before you can comment on or make changes to this bug.