https://bugzilla.suse.com/show_bug.cgi?id=1180344 https://bugzilla.suse.com/show_bug.cgi?id=1180344#c2 --- Comment #2 from Adam Stephens --- Created attachment 844695 --> https://bugzilla.suse.com/attachment.cgi?id=844695&action=edit cpuinfo -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1180344 https://bugzilla.suse.com/show_bug.cgi?id=1180344#c4 --- Comment #4 from Adam Stephens --- Problem still exists in 5.10.2 from Kernel:Stable. kernel-default-5.10.2-1.1.g572ce1d.x86_64 -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1180344 Adam Stephens changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Kernel 5.10.1 fails to boot |Kernel 5.10 fails to boot |with workqueue lockup |with workqueue lockup -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1180344 https://bugzilla.suse.com/show_bug.cgi?id=1180344#c15 Bit Juggler changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suse.junky@t-online.de --- Comment #15 from Bit Juggler --- Same problem here. The journal shows Dez 25 16:58:45 WORKSTATION kernel: Intel(R) Wireless WiFi driver for Linux Dez 25 16:58:45 WORKSTATION kernel: iwlwifi 0000:6e:00.0: enabling device (0000 -> 0002) Dez 25 16:58:45 WORKSTATION kernel: BUG: unable to handle page fault for address: ffffadee03d6127b Dez 25 16:58:45 WORKSTATION kernel: #PF: supervisor write access in kernel mode Dez 25 16:58:45 WORKSTATION kernel: #PF: error_code(0x0003) - permissions violation Dez 25 16:58:45 WORKSTATION kernel: PGD 100000067 P4D 100000067 PUD 1001cb067 PMD 107da2067 PTE 80000002a185d061 Dez 25 16:58:45 WORKSTATION kernel: Oops: 0003 [#1] SMP PTI Dez 25 16:58:45 WORKSTATION kernel: CPU: 3 PID: 72 Comm: kworker/3:1 Tainted: G U O 5.10.1-1-default #1 openSUSE Tumbleweed Dez 25 16:58:45 WORKSTATION kernel: Hardware name: TUXEDO P65xHP/P65xHP, BIOS 1.05.04RTR 02/22/2017 Dez 25 16:58:45 WORKSTATION kernel: Workqueue: events request_firmware_work_func Dez 25 16:58:45 WORKSTATION kernel: RIP: 0010:iwl_dbg_tlv_alloc_region+0x27/0x180 [iwlwifi] Dez 25 16:58:45 WORKSTATION kernel: Code: 00 00 00 0f 1f 44 00 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 08 8b 46 04 44 8b 66 10 44 8b 6e 14 83 f8 3f 0f 86 0b 01 00 00 <c6> 46 37 00 48 89 fb > Dez 25 16:58:45 WORKSTATION kernel: RSP: 0018:ffffadee002dfce0 EFLAGS: 00010212 Dez 25 16:58:45 WORKSTATION kernel: RAX: 0000000000000040 RBX: ffff8fdb4b9e4018 RCX: 0000000000000000 Dez 25 16:58:45 WORKSTATION kernel: RDX: ffffffffc0f081b0 RSI: ffffadee03d61244 RDI: ffff8fdb4b9e4018 Dez 25 16:58:45 WORKSTATION kernel: RBP: 0000000000000000 R08: 0000000000000080 R09: 0000000000000001 Dez 25 16:58:45 WORKSTATION kernel: R10: ffffadee03d6128c R11: 0000000000000040 R12: 000000000000000c Dez 25 16:58:45 WORKSTATION kernel: R13: 0000000000000006 R14: ffff8fdc00bd8800 R15: ffff8fdc008ea800 Dez 25 16:58:45 WORKSTATION kernel: FS: 0000000000000000(0000) GS:ffff8feabecc0000(0000) knlGS:0000000000000000 Dez 25 16:58:45 WORKSTATION kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dez 25 16:58:45 WORKSTATION kernel: CR2: ffffadee03d6127b CR3: 0000000310c92004 CR4: 00000000003706e0 Dez 25 16:58:45 WORKSTATION kernel: Call Trace: Dez 25 16:58:45 WORKSTATION kernel: iwl_dbg_tlv_alloc+0x79/0x120 [iwlwifi] Dez 25 16:58:45 WORKSTATION kernel: iwl_req_fw_callback+0x10f0/0x2480 [iwlwifi] Dez 25 16:58:45 WORKSTATION kernel: ? devres_add+0x1e/0x60 Dez 25 16:58:45 WORKSTATION kernel: ? fw_add_devm_name.part.0+0x5c/0x80 Dez 25 16:58:45 WORKSTATION kernel: ? assign_fw+0x6d/0x230 Dez 25 16:58:45 WORKSTATION kernel: request_firmware_work_func+0x4d/0x90 Dez 25 16:58:45 WORKSTATION kernel: process_one_work+0x1df/0x370 Dez 25 16:58:45 WORKSTATION kernel: worker_thread+0x50/0x400 Dez 25 16:58:45 WORKSTATION kernel: ? process_one_work+0x370/0x370 Dez 25 16:58:45 WORKSTATION kernel: kthread+0x11b/0x140 Dez 25 16:58:45 WORKSTATION kernel: ? __kthread_bind_mask+0x60/0x60 Dez 25 16:58:45 WORKSTATION kernel: ret_from_fork+0x22/0x30 Dez 25 16:58:45 WORKSTATION kernel: Modules linked in: btrtl snd_compress btbcm iwlwifi btintel snd_pcm_dmaengine kvm(+) fjes(-) r8169 videodev bluetooth snd_pcm irqbypass realtek snd_timer c> Dez 25 16:58:45 WORKSTATION kernel: CR2: ffffadee03d6127b Dez 25 16:58:45 WORKSTATION kernel: ---[ end trace 8e03a10eccb1ee9d ]--- Dez 25 16:58:45 WORKSTATION kernel: RIP: 0010:iwl_dbg_tlv_alloc_region+0x27/0x180 [iwlwifi] Dez 25 16:58:45 WORKSTATION kernel: Code: 00 00 00 0f 1f 44 00 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 08 8b 46 04 44 8b 66 10 44 8b 6e 14 83 f8 3f 0f 86 0b 01 00 00 <c6> 46 37 00 48 89 fb > Dez 25 16:58:45 WORKSTATION kernel: RSP: 0018:ffffadee002dfce0 EFLAGS: 00010212 Dez 25 16:58:45 WORKSTATION kernel: RAX: 0000000000000040 RBX: ffff8fdb4b9e4018 RCX: 0000000000000000 Dez 25 16:58:45 WORKSTATION kernel: RDX: ffffffffc0f081b0 RSI: ffffadee03d61244 RDI: ffff8fdb4b9e4018 Dez 25 16:58:45 WORKSTATION kernel: RBP: 0000000000000000 R08: 0000000000000080 R09: 0000000000000001 Dez 25 16:58:45 WORKSTATION kernel: R10: ffffadee03d6128c R11: 0000000000000040 R12: 000000000000000c Dez 25 16:58:45 WORKSTATION kernel: R13: 0000000000000006 R14: ffff8fdc00bd8800 R15: ffff8fdc008ea800 Dez 25 16:58:45 WORKSTATION kernel: FS: 0000000000000000(0000) GS:ffff8feabecc0000(0000) knlGS:0000000000000000 Dez 25 16:58:45 WORKSTATION kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dez 25 16:58:45 WORKSTATION kernel: CR2: ffffadee03d6127b CR3: 0000000310c92004 CR4: 00000000003706e0 However blacklisting iwlwifi is not really an option. I will use kernel 5.9.14 for the time being. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1180344 https://bugzilla.suse.com/show_bug.cgi?id=1180344#c22 --- Comment #22 from Frank Kr�ger --- (In reply to Takashi Iwai from comment #21)

I haven't had time to take a deeper look (and the bug doesn't hit on my machine), but as a blind shot, I built a kernel with the patch with a revert of the commit in the relevant code path. Can anyone test a kernel package in OBS home:tiwai:bsc1180344? Just to be sure.

Tried your kernel, but failed with "bad shim signature". -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1180344 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.kernel.org | |/show_bug.cgi?id=210733 -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1180344 https://bugzilla.suse.com/show_bug.cgi?id=1180344#c24 --- Comment #24 from Frank Kr�ger --- (In reply to Takashi Iwai from comment #21)

I haven't had time to take a deeper look (and the bug doesn't hit on my machine), but as a blind shot, I built a kernel with the patch with a revert of the commit in the relevant code path. Can anyone test a kernel package in OBS home:tiwai:bsc1180344? Just to be sure.

Disabling secure boot and booting kernel-default-5.10.2-1.1.gcb6a1b3.x86_64 from home:tiwai:bsc1180344 results in a black screen. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1180344 https://bugzilla.suse.com/show_bug.cgi?id=1180344#c26 --- Comment #26 from Frank Kr�ger --- (In reply to Takashi Iwai from comment #25)

Then you're hitting a problem that is something else than this bug. I guess you get the same result from the kernel in OBS Kernel:stable, too?

Yes, but your kernel with the "iwlwifi dbg revert" boots fine with 'options iwlwifi enable_ini=0'. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1180344 https://bugzilla.suse.com/show_bug.cgi?id=1180344#c28 --- Comment #28 from Frank Kr�ger --- When boot fails, I can see Dez 27 09:48:27 kernel: iwlwifi 0000:03:00.0: enabling device (0000 -> 0002) Dez 27 09:48:27 kernel: iwlwifi 0000:03:00.0: api flags index 2 larger than supported by driver Dez 27 09:48:27 kernel: RIP: 0010:iwl_dbg_tlv_alloc_region+0x27/0x180 [iwlwifi] Dez 27 09:48:27 kernel: iwl_dbg_tlv_alloc+0x79/0x120 [iwlwifi] Dez 27 09:48:27 kernel: iwl_req_fw_callback+0x10f0/0x2480 [iwlwifi] Dez 27 09:48:27 kernel: Modules linked in: btrtl snd_intel_dspcfg btbcm soundwire_intel btintel tps6598x roles soundwire_generic_allocation soundwire_cadence bluetooth snd_hda_codec snd_hda_core uvcvideo kvm_amd videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_hwdep kvm videobuf2_common soundwire_bus iwlwifi videodev ecdh_generic snd_soc_core dmi_sysfs ftsteutates pcc_cpufreq(-) cfg80211 irqbypass ecc mc snd_compress joydev snd_pcm_dmaengine pcspkr efi_pstore snd_pcm thinkpad_acpi wmi_bmof r8169 sp5100_tco i2c_piix4 k10temp realtek snd_timer snd_rn_pci_acp3x mdio_devres snd_pci_acp3x ledtrig_audio ipmi_devintf libphy rfkill ipmi_msghandler ucsi_acpi(+) snd typec_ucsi typec soundcore ac tiny_power_button i2c_multi_instantiate i2c_scmi button acpi_cpufreq xfs nls_iso8859_1 nls_cp437 vfat fat libcrc32c fuse configfs amdgpu iommu_v2 gpu_sched ttm i2c_algo_bit rtsx_pci_sdmmc drm_kms_helper mmc_core syscopyarea sysfillrect sysimgblt fb_sys_fops cec xhci_pci xhci_pci_renesas crct10dif_pclmul Dez 27 09:48:27 gropius kernel: RIP: 0010:iwl_dbg_tlv_alloc_region+0x27/0x180 [iwlwifi] Using the above-mentioned workaround it boots fine: Dez 27 09:54:33 kernel: iwlwifi 0000:03:00.0: enabling device (0000 -> 0002) Dez 27 09:54:33 kernel: iwlwifi 0000:03:00.0: api flags index 2 larger than supported by driver Dez 27 09:54:33 kernel: iwlwifi 0000:03:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.22 Dez 27 09:54:33 kernel: iwlwifi 0000:03:00.0: loaded firmware version 59.601f3a66.0 cc-a0-59.ucode op_mode iwlmvm Dez 27 09:54:34 kernel: iwlwifi 0000:03:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 Dez 27 09:54:34 kernel: iwlwifi 0000:03:00.0: base HW address: a8:7e:ea:04:a8:67 Dez 27 09:54:34 NetworkManager[826]: <info> [1609059274.8447] rfkill3: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:02.3/0000:03:00.0/ieee80211/phy0/rfkill3) (driver iwlwifi) Dez 27 09:54:34 gropius kernel: iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0 -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1180344 https://bugzilla.suse.com/show_bug.cgi?id=1180344#c30 --- Comment #30 from Frank Kr�ger --- (In reply to Takashi Iwai from comment #29)

Thanks, that shows that the problem still persists.

I refreshed the same repo with another shot, now a new kernel is being built. Please check it later again. It'll be based on 5.10.3.

5.10.3-1.g0a5cd07-default x86_64 from your repo works fine (without the workaround)! -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1180344 Frank Kr�ger changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1180344 https://bugzilla.suse.com/show_bug.cgi?id=1180344#c33 --- Comment #33 from Takashi Iwai --- Created attachment 844708 --> https://bugzilla.suse.com/attachment.cgi?id=844708&action=edit Tentative fix patch -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1180344 https://bugzilla.suse.com/show_bug.cgi?id=1180344#c35 Arjen de Korte changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #844708|0 |1 is obsolete| | --- Comment #35 from Arjen de Korte --- Created attachment 844714 --> https://bugzilla.suse.com/attachment.cgi?id=844714&action=edit Fix for bug 1180344 -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1180344 https://bugzilla.suse.com/show_bug.cgi?id=1180344#c37 --- Comment #37 from Arjen de Korte --- (In reply to Klein Kravis from comment #36)

Same issue on my ThinkBook 13s IWL (See bug: 1180376) Would blacklisting iwlwifi prevent WiFi from working?

You don't need to blacklist iwlwifi (which would indeed prevent WiFi from working). In https://bugzilla.suse.com/show_bug.cgi?id=1180344#c16 a workaround is described which will temporary fix this problem. It disables the debug logging, which is where the problem seems to be in. Unless you're actively involved in the iwlwifi development, it is highly unlikely that you need the debuglog anyway. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1180344 https://bugzilla.suse.com/show_bug.cgi?id=1180344#c39 Thomas Rother changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |t.rother@netzwissen.de --- Comment #39 from Thomas Rother --- I also have the same issue on a dell precision 7530. Just for info (I am not deep in kernel dev issues) and for understanding: So the only current solutions are a) either disable iwlwifi with "options iwlwifi enable_ini=0" and boot kernel 5.10, but with loosing wireless functionality as a consequence b) go back to 5.9 Is that correct? -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1180344 https://bugzilla.suse.com/show_bug.cgi?id=1180344#c42 Huy Phung changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |huy.phung1292@gmail.com --- Comment #42 from Huy Phung --- *** Bug 1180396 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1180344 https://bugzilla.suse.com/show_bug.cgi?id=1180344#c49 --- Comment #49 from Adam Stephens --- (In reply to Frank Kr�ger from comment #45)

JFYI: kernel-default-5.10.3-2.1.g73f6c2f.x86_64 from Kernel:stable boots fine without the above-mentioned workaround. Thx.

I can confirm that I'm able to boot into 5.10.3 without any workarounds. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1180344 https://bugzilla.suse.com/show_bug.cgi?id=1180344#c51 Michal Kube��ek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #51 from Michal Kube��ek --- (In reply to Thomas Rother from comment #50)

Also confirmed, kernel 5.10.3 works without workarounds. Marking resolved fixed

That would be premature. First, 5.10.3 certainly does not work without workaround, only our KotD snapshot does, thanks to Takashi's patch. Even current mainline (or 5.11-rc2) does not have the issue addressed, AFAICS. Thus I would prefer to keep the bug open until we have some response from upstream and until a fix (Takashi's, Arjen's or some other) is on its way to mainline. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1180344 https://bugzilla.suse.com/show_bug.cgi?id=1180344#c53 --- Comment #53 from Arjen de Korte --- (In reply to Axel Braun from comment #52)

I have upgraded to Kernel 5.10.3 without workaround and iwlwifi works....

That is because Takashi patched out the offending code in Kernel 5.10.3 before it was released in Tumbleweed. But upstream Kernel 5.10.3 (and 5.10.4 as well) is still broken. That's why it is probably a good idea to leave this open, as the upstream fix is not available. FWIW, upstream might choose a completely different approach to fix this. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1180344 https://bugzilla.suse.com/show_bug.cgi?id=1180344#c55 --- Comment #55 from Takashi Iwai --- It must be just laziness :) I've prepared a patch to add const, but it's not for 5.11 (and still waiting for the reaction of this bug itself), so the patch hasn't been submitted yet. -- You are receiving this mail because: You are the assignee for the bug.