Bug 218946 - iwlwifi 0000:02:00.0: Microcode SW error detected. Restarting 0x82000000.
Summary: iwlwifi 0000:02:00.0: Microcode SW error detected. Restarting 0x82000000.
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless-intel (show other bugs)
Hardware: Intel Linux
: P3 normal
Assignee: Default virtual assignee for network-wireless-intel
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-08 06:52 UTC by doru iorgulescu
Modified: 2024-12-11 07:23 UTC (History)
5 users (show)

See Also:
Kernel Version: 6.10.0-rc3
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg.txt (88.47 KB, text/plain)
2024-06-08 06:52 UTC, doru iorgulescu
Details

Description doru iorgulescu 2024-06-08 06:52:38 UTC
Created attachment 306442 [details]
dmesg.txt

The linux Kernel 6.10.0-rc3
[   17.124384] iwlwifi 0000:02:00.0: Microcode SW error detected.  Restarting 0x82000000.
[   17.124405] iwlwifi 0000:02:00.0: Loaded firmware version: 18.168.6.1 6000g2b-6.ucode
[   17.124588] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
[   17.124590] iwlwifi 0000:02:00.0: Status: 0x000002CC, count: 6
[   17.124592] iwlwifi 0000:02:00.0: 0x0000198A | ADVANCED_SYSASSERT          
[   17.124594] iwlwifi 0000:02:00.0: 0x00015920 | uPc
[   17.124596] iwlwifi 0000:02:00.0: 0x00015910 | branchlink1
[   17.124597] iwlwifi 0000:02:00.0: 0x00015910 | branchlink2
[   17.124599] iwlwifi 0000:02:00.0: 0x0000DBEA | interruptlink1
[   17.124600] iwlwifi 0000:02:00.0: 0x00000000 | interruptlink2
[   17.124602] iwlwifi 0000:02:00.0: 0x0000005C | data1
[   17.124603] iwlwifi 0000:02:00.0: 0x00000008 | data2
[   17.124605] iwlwifi 0000:02:00.0: 0x000001DC | line
[   17.124606] iwlwifi 0000:02:00.0: 0x11C0C9B1 | beacon time
[   17.124608] iwlwifi 0000:02:00.0: 0x006FB64F | tsf low
[   17.124609] iwlwifi 0000:02:00.0: 0x00000000 | tsf hi
[   17.124611] iwlwifi 0000:02:00.0: 0x00000000 | time gp1
[   17.124612] iwlwifi 0000:02:00.0: 0x0078DBFB | time gp2
[   17.124613] iwlwifi 0000:02:00.0: 0x00000000 | time gp3
[   17.124615] iwlwifi 0000:02:00.0: 0x754312A8 | uCode version
[   17.124616] iwlwifi 0000:02:00.0: 0x000000B0 | hw version
[   17.124618] iwlwifi 0000:02:00.0: 0x00484B00 | board version
[   17.124619] iwlwifi 0000:02:00.0: 0x0000001C | hcmd
[   17.124620] iwlwifi 0000:02:00.0: 0x27863040 | isr0
[   17.124622] iwlwifi 0000:02:00.0: 0x0189F800 | isr1
[   17.124623] iwlwifi 0000:02:00.0: 0x00000E02 | isr2
[   17.124625] iwlwifi 0000:02:00.0: 0x0143FCC3 | isr3
[   17.124626] iwlwifi 0000:02:00.0: 0x00000000 | isr4
[   17.124627] iwlwifi 0000:02:00.0: 0x00000110 | isr_pref
[   17.124629] iwlwifi 0000:02:00.0: 0x000260A4 | wait_event
[   17.124630] iwlwifi 0000:02:00.0: 0x00000050 | l2p_control
[   17.124632] iwlwifi 0000:02:00.0: 0x0000013A | l2p_duration
[   17.124633] iwlwifi 0000:02:00.0: 0x0000003F | l2p_mhvalid
[   17.124634] iwlwifi 0000:02:00.0: 0x00101040 | l2p_addr_match
[   17.124636] iwlwifi 0000:02:00.0: 0x00000005 | lmpm_pmg_sel
[   17.124637] iwlwifi 0000:02:00.0: 0x13011136 | timestamp
[   17.124639] iwlwifi 0000:02:00.0: 0x00004858 | flow_handler
[   17.124717] iwlwifi 0000:02:00.0: Start IWL Event Log Dump: nothing in log
Comment 1 The Linux kernel's regression tracker (Thorsten Leemhuis) 2024-06-11 12:16:27 UTC
was this a error that happened once, or is it reproducable? and did things use to work fine with earlier kernels, e.g. 6.9.y?
Comment 2 doru iorgulescu 2024-06-11 13:45:34 UTC
Yes it work ok with 6.9.y
Thank You
Regards
Comment 3 The Linux kernel's regression tracker (Thorsten Leemhuis) 2024-06-11 14:45:14 UTC
(In reply to doru iorgulescu from comment #2)
> Yes it work ok with 6.9.y

that only answered one of two questions. Here is a third: did you recheck if 6.9.y still works to rule out the problem is caused by a firmware update or something like that?
Comment 4 doru iorgulescu 2024-06-11 17:07:49 UTC
No firmware update only linux kernel 6.10.0-rc3
Thank You
Regards
Comment 5 The Linux kernel's regression tracker (Thorsten Leemhuis) 2024-06-17 09:47:32 UTC
I forwarded this to the list

Side note: there are a few additional instructions for handling cases like this you might want to follow: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging

And if the developer do not show up in the next few days or can't really help, you might need to perform a git bisection (https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html ) to find the change that causes the problem.
Comment 6 The Linux kernel's regression tracker (Thorsten Leemhuis) 2024-06-17 09:47:50 UTC
(In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from comment #5)
> I forwarded this to the list

Forgot the link: https://lore.kernel.org/regressions/f16d49f6-01a4-45c7-aabf-ab6a1b8bfe6e@leemhuis.info/
Comment 7 Miri Korenblit 2024-06-17 11:18:36 UTC
was this a error that happened once, or is it reproducable?
Comment 8 The Linux kernel's regression tracker (Thorsten Leemhuis) 2024-07-01 11:48:41 UTC
(In reply to Miri Korenblit from comment #7)
> was this a error that happened once, or is it reproducable?

doru iorgulescu: did you miss this or is there some reason why you didn't reply -- did the problem maybe vanish?
Comment 9 Maxim 2024-09-23 12:35:49 UTC
I noticed BUG 215635 first but this one seems more relatable.

I started to have microcode crashes precisely after updating from 6.9 to 6.10:
https://bugzilla.kernel.org/show_bug.cgi?id=215635#c41

From 2024-06-20 to 2024-07-19 there were no crashes and after that I routinely have around 5 crashes a day on average.
Comment 10 The Linux kernel's regression tracker (Thorsten Leemhuis) 2024-09-23 13:35:13 UTC
(In reply to Maxim from comment #9)
> I noticed BUG 215635 first but this one seems more relatable.

Word of advice: file a new bug and mention it afterwards here and in the other bug; anything else is a recipe to get ignored, at the symptoms you see can be caused by various issues that might or might not be related (especially in this particular case). 

https://linux-regtracking.leemhuis.info/post/frequent-reasons-why-linux-kernel-bug-reports-are-ignored/#you-reported-the-problem-in-a-reply-to-an-earlier-report
Comment 11 brent benjamin 2024-12-11 07:23:38 UTC Comment hidden (spam)

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