From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: linuxwifi@intel.com,
Linux List Kernel Mailing <linux-wireless@vger.kernel.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Microcode SW error detected on Wi-Fi 6 AX200 (rev 1a)
Date: Fri, 31 Jan 2020 00:44:03 +0500 [thread overview]
Message-ID: <CABXGCsOn=W+grZcZBybY8FkQBL_WH_OH6mQgGHKj3ojJbL-Osw@mail.gmail.com> (raw)
Hi folks.
During Wi-Fi operation, the following entry in the kernel logs was noticed:
Microcode SW error detected. Restarting 0x0.
Start IWL Error Log Dump:
Status: 0x00000040, count: 6
Loaded firmware version: 48.4fa0041f.0
0x00000034 | NMI_INTERRUPT_WDG
0x0000A2F0 | trm_hw_status0
0x00000000 | trm_hw_status1
0x004F8E3C | branchlink2
0x0000DBBA | interruptlink1
0x0000DBBA | interruptlink2
0x004F7FB6 | data1
0x00000002 | data2
0xF0000008 | data3
0x02001D26 | beacon time
0xC9CE631E | tsf low
0x00000113 | tsf hi
0x00000000 | time gp1
0xCEE30220 | time gp2
0x00000001 | uCode revision type
0x00000030 | uCode version major
0x4FA0041F | uCode version minor
0x00000340 | hw version
0x00C89000 | board version
0x80A0FC0F | hcmd
0xE6FA0000 | isr0
0x00400000 | isr1
0x08F80002 | isr2
0x4CC1FFDC | isr3
0x00000000 | isr4
0x0542001C | last cmd Id
0x004F7FB6 | wait_event
0x00000094 | l2p_control
0x00000020 | l2p_duration
0x0000000F | l2p_mhvalid
0x000000C7 | l2p_addr_match
0x00000009 | lmpm_pmg_sel
0x00000000 | timestamp
0x0000E080 | flow_handler
Start IWL Error Log Dump:
Status: 0x00000040, count: 7
0x20000070 | NMI_INTERRUPT_LMAC_FATAL
0x00000000 | umac branchlink1
0xC008CC3C | umac branchlink2
0x8048D0E6 | umac interruptlink1
0x8048D0E6 | umac interruptlink2
0x00000400 | umac data1
0x8048D0E6 | umac data2
0x00000000 | umac data3
0x00000030 | umac major
0x4FA0041F | umac minor
0xCEE30231 | frame pointer
0xC0886284 | stack pointer
0x0010011D | last host cmd
0x00000000 | isr status reg
Fseq Registers:
0xE0000101 | FSEQ_ERROR_CODE
0x00290008 | FSEQ_TOP_INIT_VERSION
0x80050008 | FSEQ_CNVIO_INIT_VERSION
0x0000A503 | FSEQ_OTP_VERSION
0x80000003 | FSEQ_TOP_CONTENT_VERSION
0x4552414E | FSEQ_ALIVE_TOKEN
0x00100530 | FSEQ_CNVI_ID
0x00000532 | FSEQ_CNVR_ID
0x00100530 | CNVI_AUX_MISC_CHIP
0x00000532 | CNVR_AUX_MISC_CHIP
0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
Collecting data: trigger 2 fired.
lspci detect Wi Fi device as "04:00.0 Network controller: Intel
Corporation Wi-Fi 6 AX200 (rev 1a)"
$ ethtool -i wlp4s0 | grep firmware
firmware-version: 48.4fa0041f.0
Full kernel log is here: https://pastebin.com/gtpyTaeM
I hope it helps fix the problem.
Take this opportunity I wanna ask is it normal that kernel logs
flooded with such messages:
authenticate with 50:ff:20:04:c8:dc
send auth to 50:ff:20:04:c8:dc (try 1/3)
authenticated
associate with 50:ff:20:04:c8:dc (try 1/3)
RX AssocResp from 50:ff:20:04:c8:dc (capab=0x1811 status=53 aid=1)
50:ff:20:04:c8:dc denied association (code=53)
authenticate with 50:ff:20:04:c8:dc
send auth to 50:ff:20:04:c8:dc (try 1/3)
authenticate with 50:ff:20:04:c8:dc
send auth to 50:ff:20:04:c8:dc (try 1/3)
authenticated
associate with 50:ff:20:04:c8:dc (try 1/3)
RX AssocResp from 50:ff:20:04:c8:dc (capab=0x1811 status=0 aid=1)
associated
Thanks.
--
Best Regards,
Mike Gavrilov.
reply other threads:[~2020-01-30 19:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CABXGCsOn=W+grZcZBybY8FkQBL_WH_OH6mQgGHKj3ojJbL-Osw@mail.gmail.com' \
--to=mikhail.v.gavrilov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
/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).