intel-ucode 20210608 release triggers iwlwifi Microcode SW error on 06-9e-0a #56
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Is it only the microcode that is upgrade/downgraded to see the issue? Also, is there more detail on the "multiple users" affected? |
|
@whpenner I can confirm that I got microcode errors regarding giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: regular scan timed out
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: Microcode SW error detected. Restarting 0x2000000.
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: Status: 0x00000040, count: 6
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: Loaded firmware version: 36.ad812ee0.0 8000C-36.ucode
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x000002F0 | trm_hw_status0
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00000000 | trm_hw_status1
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x0002438C | branchlink2
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00039C06 | interruptlink1
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00000126 | interruptlink2
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00000000 | data1
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00000080 | data2
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x07830000 | data3
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x56406C31 | beacon time
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x2294452A | tsf low
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00000001 | tsf hi
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00000000 | time gp1
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x2294A08A | time gp2
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00000001 | uCode revision type
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00000024 | uCode version major
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0xAD812EE0 | uCode version minor
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00000201 | hw version
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00489004 | board version
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x808BFE01 | hcmd
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00022000 | isr0
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00800000 | isr1
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x08005802 | isr2
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00400080 | isr3
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00000000 | isr4
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x808AFB03 | last cmd Id
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00000000 | wait_event
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00008E4C | l2p_control
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00000000 | l2p_duration
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00000000 | l2p_mhvalid
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00000000 | l2p_addr_match
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x0000008F | lmpm_pmg_sel
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x14100651 | timestamp
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00340010 | flow_handler
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: Status: 0x00000040, count: 7
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00000070 | NMI_INTERRUPT_LMAC_FATAL
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00000000 | umac branchlink1
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0xC0086B3C | umac branchlink2
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0xC008D930 | umac interruptlink1
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0xC0083D08 | umac interruptlink2
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00000800 | umac data1
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0xC0083D08 | umac data2
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0xDEADBEEF | umac data3
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00000024 | umac major
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0xAD812EE0 | umac minor
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0xC088628C | frame pointer
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0xC088628C | stack pointer
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00CC010D | last host cmd
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00000000 | isr status reg
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: IML/ROM dump:
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00000000 | IML/ROM error/state
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x00000003 | IML/ROM data1
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: Fseq Registers:
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x2CA4494C | FSEQ_ERROR_CODE
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0xA8528020 | FSEQ_TOP_INIT_VERSION
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0xEA146062 | FSEQ_CNVIO_INIT_VERSION
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x0000A056 | FSEQ_OTP_VERSION
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0xE3B1BE88 | FSEQ_TOP_CONTENT_VERSION
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0xE3639711 | FSEQ_ALIVE_TOKEN
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0xE4F156E1 | FSEQ_CNVI_ID
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0xAD4584B4 | FSEQ_CNVR_ID
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x03000000 | CNVI_AUX_MISC_CHIP
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x0BADCAFE | CNVR_AUX_MISC_CHIP
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
giu 13 15:33:41 hyperversum kernel: iwlwifi 0000:02:00.0: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR |
|
Do we have any more data on this? What I did notice is that it looks like neither reporter is using the latest iwlwifi firmware available at linux-firmware git ATM, but given the lack of changelogs, there's no way to know whether that would be relevant without actually trying the newest iwlwifi firmware to see if the problem goes away... |
|
@hmh I'm using the latest version of Will try switching to |
Why do you say so? It seems that the iwlwifi ucode API version is 36 in both cases, and API version 36 is the latest (at least in [0]) for both 8000C[1] and 8265[2]. [0] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/?id=0f66b74b6267fce66395316308d88b0535aa3df2 |
|
I was looking at the reported git hash (not API version) of the firmware in the logs submitted with the reports, against the one in a fresh checkout of linux-firmware, and noticed they were different. Evidently, I may have been mistaken about it. I am looking at it again now, if I got it wrong I will hide that comment to avoid confusing things (and edit this one)... Edit1: Since firmware revision ca7b901d is different from the firmware revision in the reported logs, I assumed the two reports were using out-of-date firmware. This assumes linux-firmware in git actually has the newest available iwlwifi dump at the moment, of course. I don't have hardware here to run that firmware and check if it reports anything different from what is in the commit log "revision", though. |
|
Oh, you're right, revision Not sure why is there such a author/commit discrepancy, though, looks like a revert (cf. commit |
|
Well, no idea about the commit flux, maybe some regression was detected and fixed in the latest one... if there is some sort of errata, specification updates or changelog for iwlwifi, I have no idea where it could be. The latest iwlwifi release is a relevant security update: it fixes some of FragAttack (the full fix also requires updated kernel drivers and kernel wifi stack AFAIK). Whatever the reason (and I have my own opinion on this, off-topic here), several distros have not picked up on it yet. Debian is now aware, so we should issue updates for that firmware shortly. I believe Ubuntu has been alerted as well if they were not working on it yet. @BachoSeven : you might want to alert your distro to update wifi firmware from the latest in linux-firmware git as a security fix for FragAttack. That said, all you need to do to use the newer iwlwifi firmware is to copy the newer file(s) from here: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/ over the older one(s) in /lib/firmware (or /lib/firmware/ depending on your distro). Keep a copy of the old file or reinstall your distribution's firmware package to restore back to the distro firmware if it doesn't work. Please do report back if the newer wifi firmware fixes the bad interaction with the new CPU microcode... |
|
Any news on this? Does the newest iwlwifi firmware fix things ? Or maybe disabling Intel ME / AMT network connection over WiFi in BIOS/UEFI fixes it ? |
|
@hmh I switched to the As for your second suggestion, I have no idea how to try those(can a user even disable IME?) or if they are possible in my bios, didn't see related settings in it. |
|
@BachoSeven thanks for the update! Please drop a note here if you reproduce the issue again (which would mean the problem can still happen even with the latest iwlwifi firmware). |
|
@hmh It happened again yesterday while using the |
|
@BachoSeven : thanks for the update! it is a pity the newest iwlwifi firmware available ATM in linux-firmware did not avoid the microcode+iwlwifi regression: it would have been straightforward to work around the issue by recommending everyone to also update the iwlwifi firmware... |
|
I have got the same issue on kernel 5.12.15 with a Intel Corporation Centrino Advanced-N 6205. Trying both firmwares 18.168.6.1 6000g2a-6.ucode SHA1 sum: 1936ad5fe2551ac9d6551be0d85984c1f5cc5cf7 repeatedly restarts with the error above / below, and the older iwconfig:
Full error message:
|
|
Downgrading my kernel back to Ubuntu's standard 5.8.0-59 makes this disappear on the new firmware for me, so my piece does not seem to be a firmware issue; I'll bisect kernel versions and open a report on kernel.org |
|
Spoke too soon, seems like the reboot was what helped and a suspend-to-ram cycle made the problem appear again on 5.8.0. I will see if any of the tricks (iwlmvm power_scheme=1, lower ucode) help prevent the problem after a reboot and subsequent s2ram cycles. |
|
I wonder if it is possible to narrow the issue down some way; may I ask those who is experiencing the issue, provide the DMI information (it may be the case that it is related to specific vendor's system firmware's PM implementation, or something like that)? It can be obtained with the following command: |
|
My DMI info: |
|
I have found that the issue disappears for me when I do: via a comment in https://askubuntu.com/questions/675352/wireless-disconnects-intermittently-with-intel-corporation-centrino-advanced-n-6 |
Here you go: /sys/devices/virtual/dmi/id/bios_date 04/18/2019
/sys/devices/virtual/dmi/id/bios_release 5.12
/sys/devices/virtual/dmi/id/bios_vendor American Megatrends Inc.
/sys/devices/virtual/dmi/id/bios_version UX310UQK.311
/sys/devices/virtual/dmi/id/board_asset_tag ATN12345678901234567
/sys/devices/virtual/dmi/id/board_name UX310UQK
/sys/devices/virtual/dmi/id/board_serial N0CV1715MB0024881
/sys/devices/virtual/dmi/id/board_vendor ASUSTeK COMPUTER INC.
/sys/devices/virtual/dmi/id/board_version 1.0
/sys/devices/virtual/dmi/id/chassis_asset_tag No Asset Tag
/sys/devices/virtual/dmi/id/chassis_serial H4N0CV048885155
/sys/devices/virtual/dmi/id/chassis_type 10
/sys/devices/virtual/dmi/id/chassis_vendor ASUSTeK COMPUTER INC.
/sys/devices/virtual/dmi/id/chassis_version 1.0
/sys/devices/virtual/dmi/id/product_family ZenBook
/sys/devices/virtual/dmi/id/product_name UX310UQK
/sys/devices/virtual/dmi/id/product_serial H4N0CV048885155
/sys/devices/virtual/dmi/id/product_sku
/sys/devices/virtual/dmi/id/product_uuid 5a8b4aa0-db09-9248-8c8a-c15f8bf1fc30
/sys/devices/virtual/dmi/id/product_version 1.0
/sys/devices/virtual/dmi/id/sys_vendor ASUSTeK COMPUTER INC. |
Interesting, personally I have |
|
@tu-maurice, could you please hide your last three comments since it is a different issue? Just so someone doesn't get confused if they read it fast and don't notice your last comment... |
|
@hmh I wasn't entirely sure whether maybe the others could've confirmed my observations, but okay. I was never here. |
|
@tu-maurice: if you can link your issue to a microcode update (hint: boot Linux with the dis_ucode_ldr parameter in the kernel command line/grub -- if the issue disappears, the chances are very high that the microcode update is the culprit), you are very welcome to open a new bug with the correct processor signature and full details... |
|
Please look at the following site - there is some data collection that can help us debug this issue. https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging |
|
For what it worth, I had this exact crash but with an on-board AX 210 WiFi NIC (iwlwifi loads the microcode ty-a0-gf-a0-71.ucode). In my case it seems to trace back to some power management issue as setting iwlmvm.power_scheme=1 (and only this, nothing disabled or overridden in iwlwifi) make the issue disappear. My WiFi connection is now stable for more than 8 hours without any glitch of any kind. AFAK, setting something for Kernel 5.18.9 with Gentoo patches applied but it should change nothing at all and a vanilla kernel should exhibit the very same behavior. |
|
What is |
|
Ah, I now see, there is also a |
|
I just wanted to share that it has worked rock solid, for two days now, with the previous firmware version, on my Ubuntu 22.04: I've just removed the |
After updating to the latest release 20210608 in Ubuntu we have had a report that this caused iwlwifi to constantly restart in a loop and hence make wifi unusable in that case. Please see https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1931540 for the full details.
The text was updated successfully, but these errors were encountered: