From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Bug 215523 - Firmware crash with 66.f1c864e0.0 (cc-a0-66.ucode) and 68.01d30b0c (cc-a0-68.ucode)
Date: Thu, 10 Feb 2022 10:56:13 +0100 [thread overview]
Message-ID: <adf5ac57-cd60-a004-a05d-6d7c3ad7efa7@leemhuis.info> (raw)
Hi, this is your Linux kernel regression tracker speaking.
There is a regression in bugzilla.kernel.org I'd like to add to the
tracking:
#regzbot introduced: v5.16..v5.17-rc1
#regzbot from: Udo Steinberg <udo@hypervisor.org>
#regzbot title: iwlwifi: Firmware crash with 66.f1c864e0.0
(cc-a0-66.ucode) and 68.01d30b0c (cc-a0-68.ucode)
#regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215523
Quote:
> Seeing the following firmware crash frequently with
> firmware-version: 66.f1c864e0.0 cc-a0-66.ucode
>
> [14699.974055] iwlwifi 0000:03:00.0: Microcode SW error detected. Restarting 0x0.
> [14699.974484] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
> [14699.974496] iwlwifi 0000:03:00.0: Transport status: 0x0000004A, valid: 6
> [14699.974509] iwlwifi 0000:03:00.0: Loaded firmware version: 66.f1c864e0.0 cc-a0-66.ucode
> [14699.974521] iwlwifi 0000:03:00.0: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL
> [14699.974532] iwlwifi 0000:03:00.0: 0x000022F0 | trm_hw_status0
> [14699.974541] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
> [14699.974549] iwlwifi 0000:03:00.0: 0x004FAA46 | branchlink2
> [14699.974557] iwlwifi 0000:03:00.0: 0x004F13DE | interruptlink1
> [14699.974565] iwlwifi 0000:03:00.0: 0x004F13DE | interruptlink2
> [14699.974573] iwlwifi 0000:03:00.0: 0x00005D04 | data1
> [14699.974581] iwlwifi 0000:03:00.0: 0x00001000 | data2
> [14699.974588] iwlwifi 0000:03:00.0: 0x00000000 | data3
> [14699.974596] iwlwifi 0000:03:00.0: 0x5F80B98E | beacon time
> [14699.974604] iwlwifi 0000:03:00.0: 0xDA80E7BE | tsf low
> [14699.974612] iwlwifi 0000:03:00.0: 0x000001D9 | tsf hi
> [14699.974621] iwlwifi 0000:03:00.0: 0x00000000 | time gp1
> [14699.974629] iwlwifi 0000:03:00.0: 0x1622E64D | time gp2
> [14699.974636] iwlwifi 0000:03:00.0: 0x00000001 | uCode revision type
> [14699.974645] iwlwifi 0000:03:00.0: 0x00000042 | uCode version major
> [14699.974652] iwlwifi 0000:03:00.0: 0xF1C864E0 | uCode version minor
> [14699.974662] iwlwifi 0000:03:00.0: 0x00000340 | hw version
> [14699.974668] iwlwifi 0000:03:00.0: 0x00C89000 | board version
> [14699.974675] iwlwifi 0000:03:00.0: 0x800EFC03 | hcmd
> [14699.974682] iwlwifi 0000:03:00.0: 0x00020000 | isr0
> [14699.974689] iwlwifi 0000:03:00.0: 0x00400000 | isr1
> [14699.974695] iwlwifi 0000:03:00.0: 0x08F04802 | isr2
> [14699.974702] iwlwifi 0000:03:00.0: 0x00C3780C | isr3
> [14699.974710] iwlwifi 0000:03:00.0: 0x00000000 | isr4
> [14699.974718] iwlwifi 0000:03:00.0: 0x0510001C | last cmd Id
> [14699.974725] iwlwifi 0000:03:00.0: 0x00005D04 | wait_event
> [14699.974733] iwlwifi 0000:03:00.0: 0x00000054 | l2p_control
> [14699.974740] iwlwifi 0000:03:00.0: 0x00000000 | l2p_duration
> [14699.974746] iwlwifi 0000:03:00.0: 0x0000000F | l2p_mhvalid
> [14699.974754] iwlwifi 0000:03:00.0: 0x000000C7 | l2p_addr_match
> [14699.974761] iwlwifi 0000:03:00.0: 0x00000008 | lmpm_pmg_sel
> [14699.974768] iwlwifi 0000:03:00.0: 0x00000000 | timestamp
> [14699.974776] iwlwifi 0000:03:00.0: 0x00004890 | flow_handler
> [14699.974923] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
> [14699.974933] iwlwifi 0000:03:00.0: Transport status: 0x0000004A, valid: 7
> [14699.974945] iwlwifi 0000:03:00.0: 0x20003463 | ADVANCED_SYSASSERT
> [14699.974953] iwlwifi 0000:03:00.0: 0x00000000 | umac branchlink1
> [14699.974961] iwlwifi 0000:03:00.0: 0x80455A96 | umac branchlink2
> [14699.974969] iwlwifi 0000:03:00.0: 0xC00811A4 | umac interruptlink1
> [14699.974976] iwlwifi 0000:03:00.0: 0x00000000 | umac interruptlink2
> [14699.974983] iwlwifi 0000:03:00.0: 0xDA80E7B1 | umac data1
> [14699.974992] iwlwifi 0000:03:00.0: 0x1622E63F | umac data2
> [14699.974999] iwlwifi 0000:03:00.0: 0xC5490101 | umac data3
> [14699.975006] iwlwifi 0000:03:00.0: 0x00000042 | umac major
> [14699.975013] iwlwifi 0000:03:00.0: 0xF1C864E0 | umac minor
> [14699.975020] iwlwifi 0000:03:00.0: 0x1622E647 | frame pointer
> [14699.975027] iwlwifi 0000:03:00.0: 0xC0885E08 | stack pointer
> [14699.975035] iwlwifi 0000:03:00.0: 0x00AB010C | last host cmd
> [14699.975042] iwlwifi 0000:03:00.0: 0x00000000 | isr status reg
> [14699.975089] iwlwifi 0000:03:00.0: IML/ROM dump:
> [14699.975096] iwlwifi 0000:03:00.0: 0x00000003 | IML/ROM error/state
> [14699.975135] iwlwifi 0000:03:00.0: 0x00005A9A | IML/ROM data1
> [14699.975170] iwlwifi 0000:03:00.0: 0x00000080 | IML/ROM WFPM_AUTH_KEY_0
> [14699.975249] iwlwifi 0000:03:00.0: Fseq Registers:
> [14699.975269] iwlwifi 0000:03:00.0: 0x60000000 | FSEQ_ERROR_CODE
> [14699.975288] iwlwifi 0000:03:00.0: 0x80290021 | FSEQ_TOP_INIT_VERSION
> [14699.975308] iwlwifi 0000:03:00.0: 0x00050008 | FSEQ_CNVIO_INIT_VERSION
> [14699.975328] iwlwifi 0000:03:00.0: 0x0000A503 | FSEQ_OTP_VERSION
> [14699.975348] iwlwifi 0000:03:00.0: 0x80000003 | FSEQ_TOP_CONTENT_VERSION
> [14699.975368] iwlwifi 0000:03:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
> [14699.975388] iwlwifi 0000:03:00.0: 0x00100530 | FSEQ_CNVI_ID
> [14699.975407] iwlwifi 0000:03:00.0: 0x00000532 | FSEQ_CNVR_ID
> [14699.975428] iwlwifi 0000:03:00.0: 0x00100530 | CNVI_AUX_MISC_CHIP
> [14699.975450] iwlwifi 0000:03:00.0: 0x00000532 | CNVR_AUX_MISC_CHIP
> [14699.975472] iwlwifi 0000:03:00.0: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
> [14699.975494] iwlwifi 0000:03:00.0: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
> [14699.975970] iwlwifi 0000:03:00.0: WRT: Collecting data: ini trigger 4 fired (delay=0ms).
next reply other threads:[~2022-02-10 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 9:56 Thorsten Leemhuis [this message]
2022-02-25 15:10 ` Bug 215523 - Firmware crash with 66.f1c864e0.0 (cc-a0-66.ucode) and 68.01d30b0c (cc-a0-68.ucode) Thorsten Leemhuis
2022-03-01 17:07 ` Jakub Kicinski
2022-03-01 17:51 ` Thorsten Leemhuis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=adf5ac57-cd60-a004-a05d-6d7c3ad7efa7@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).