Wireless was causing my issue, with kernel 5.10.1, as shown in the bug report above. I disabled the wireless setting in the uefi settings and my desktop started fine. Which is a decent workround for me but so good for thos with a laptop.
According to SDB:Linuxrc - openSUSE Wiki it’s (only) plymouth=0, and I’ve also seen suggested noplymouth. Are all three interchangable? If yes, is that in every Plymouth-enabled distro? If no, does which works depend on context, or the distro’s own configuration options for Grub and/or kernel?
Hi
Default on my RPI3’s, Leap and SLES…
cat /etc/os-release | grep PRETTY_NAME
PRETTY_NAME="openSUSE Leap 15.1"
cat /etc/default/grub | grep GRUB_CMDLINE_LINUX_DEFAULT
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 splash=silent plymouth.enable=0 swiotlb=512 cma=300M console=ttyS1,115200n8 root=UUID=7f06244a-9113-4c4f-8e84-9dd013f4b8d9 rw "
cat /etc/os-release | grep PRETTY_NAME
PRETTY_NAME="SUSE Linux Enterprise Server 15 SP1"
cat /etc/default/grub | grep GRUB_CMDLINE_LINUX_DEFAULT
GRUB_CMDLINE_LINUX_DEFAULT="plymouth.enable=0 swiotlb=512 cma=64M console=tty console=ttyS0,115200n8 root=UUID=d827c872-c70e-45fe-8952-e23e89b5ee45 rw "
The journal shows that there is a problem with iwlwifi.
kernel: Intel(R) Wireless WiFi driver for Linux
kernel: iwlwifi 0000:6e:00.0: enabling device (0000 -> 0002)
kernel: BUG: unable to handle page fault for address: ffffadee03d6127b
kernel: #PF: supervisor write access in kernel mode
kernel: #PF: error_code(0x0003) - permissions violation
kernel: PGD 100000067 P4D 100000067 PUD 1001cb067 PMD 107da2067 PTE 80000002a185d061
kernel: Oops: 0003 #1] SMP PTI
kernel: CPU: 3 PID: 72 Comm: kworker/3:1 Tainted: G U O 5.10.1-1-default #1 openSUSE Tumbleweed
kernel: Hardware name: TUXEDO P65xHP/P65xHP, BIOS 1.05.04RTR 02/22/2017
kernel: Workqueue: events request_firmware_work_func
kernel: RIP: 0010:iwl_dbg_tlv_alloc_region+0x27/0x180 [iwlwifi]
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 >
kernel: RSP: 0018:ffffadee002dfce0 EFLAGS: 00010212
kernel: RAX: 0000000000000040 RBX: ffff8fdb4b9e4018 RCX: 0000000000000000
kernel: RDX: ffffffffc0f081b0 RSI: ffffadee03d61244 RDI: ffff8fdb4b9e4018
kernel: RBP: 0000000000000000 R08: 0000000000000080 R09: 0000000000000001
kernel: R10: ffffadee03d6128c R11: 0000000000000040 R12: 000000000000000c
kernel: R13: 0000000000000006 R14: ffff8fdc00bd8800 R15: ffff8fdc008ea800
kernel: FS: 0000000000000000(0000) GS:ffff8feabecc0000(0000) knlGS:0000000000000000
kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: CR2: ffffadee03d6127b CR3: 0000000310c92004 CR4: 00000000003706e0
kernel: Call Trace:
kernel: iwl_dbg_tlv_alloc+0x79/0x120 [iwlwifi]
kernel: iwl_req_fw_callback+0x10f0/0x2480 [iwlwifi]
kernel: ? devres_add+0x1e/0x60
kernel: ? fw_add_devm_name.part.0+0x5c/0x80
kernel: ? assign_fw+0x6d/0x230
kernel: request_firmware_work_func+0x4d/0x90
kernel: process_one_work+0x1df/0x370
kernel: worker_thread+0x50/0x400
kernel: ? process_one_work+0x370/0x370
kernel: kthread+0x11b/0x140
kernel: ? __kthread_bind_mask+0x60/0x60
kernel: ret_from_fork+0x22/0x30
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>
kernel: CR2: ffffadee03d6127b
kernel: --- end trace 8e03a10eccb1ee9d ]---
kernel: RIP: 0010:iwl_dbg_tlv_alloc_region+0x27/0x180 [iwlwifi]
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 >
kernel: RSP: 0018:ffffadee002dfce0 EFLAGS: 00010212
kernel: RAX: 0000000000000040 RBX: ffff8fdb4b9e4018 RCX: 0000000000000000
kernel: RDX: ffffffffc0f081b0 RSI: ffffadee03d61244 RDI: ffff8fdb4b9e4018
kernel: RBP: 0000000000000000 R08: 0000000000000080 R09: 0000000000000001
kernel: R10: ffffadee03d6128c R11: 0000000000000040 R12: 000000000000000c
kernel: R13: 0000000000000006 R14: ffff8fdc00bd8800 R15: ffff8fdc008ea800
kernel: FS: 0000000000000000(0000) GS:ffff8feabecc0000(0000) knlGS:0000000000000000
kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: CR2: ffffadee03d6127b CR3: 0000000310c92004 CR4: 00000000003706e0
This is an Intel Wireless-AC 9260 Bluetooth Adapter.
Regards
susejunky
Hi
You would need to ensure all the modules that taint the kernel are removed, then see if it duplicates, if so a bug report would likely be acted on…
linuxrc is completely irrelevant here.
Thanks for the hint! Although i’m not aware of any module in my system that would taint the kernel.
But lets have a look
> journalctl |grep taint
Dez 25 20:45:19 TRAGFIX kernel: Setting dangerous option enable_fbc - **taint**ing kernel
Dez 25 20:45:19 TRAGFIX kernel: Setting dangerous option enable_guc - **taint**ing kernel
>
??? Those are valid options of the i915 kernel module. How can they taint the kernel (and why does kernel 5.9.14 work with those options set)???
However i removed the settings, rebuild the 5.10.1-init-file and booted kernel 5.10.1 …
… and the boot process still got stuck and the journal showed the same iwlwifi crash.
So i guess the problem is (as already supposed in post #19 by fkrueger) somehow related to iwlwifi …
Regards
susejunky
Hi
It would appear so… 
After problems with booting (seems same as others) I made a fresh installation(from usb) with upgrading sw from network. Booting was unsuccessful. I use “esc” to see how the booting was continued and I noteced that once booting was trying many times to start Trurbo-print-manager, another time the booting failed to Bluetooth and again also to network connection. I use wired (lan) connection but wlan is available too.
Operating System: openSUSE Tumbleweed 20201201KDE Plasma Version: 5.20.3
KDE Frameworks Version: 5.76.0
Qt Version: 5.15.2
Kernel Version: 5.9.11-1-default
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-8559U CPU @ 2.70GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa DRI Intel® Iris® Plus Graphics 655
**System: Host:** localhost **Kernel:** 5.9.11-1-default x86_64 **bits:** 64 **Desktop:** KDE Plasma 5.20.3
**Distro:** openSUSE Tumbleweed 20201201
**Machine: Type:** Mini-pc **System:** Intel Client Systems **product:** NUC8i7BEH **v:** J72992-306 **serial:** <superuser/root required>
**Mobo:** Intel **model:** NUC8BEB **v:** J72688-306 **serial:** <superuser/root required> **UEFI:** Intel
**v:** BECFL357.86A.0073.2019.0618.1409 **date:** 06/18/2019
**CPU: Topology:** Quad Core **model:** Intel Core i7-8559U **bits:** 64 **type:** MT MCP **L2 cache:** 8192 KiB
**Speed:** 600 MHz **min/max:** 400/4500 MHz **Core speeds (MHz):** **1:** 600 **2:** 600 **3:** 600 **4:** 600 **5:** 600 **6:** 600 **7:** 601 **8:** 600
**Graphics: Device-1:** Intel Iris Plus Graphics 655 **driver:** i915 **v:** kernel
**Display:** x11 **server:** X.org 1.20.9 **driver:** modesetting **unloaded:** fbdev,vesa **resolution:** <xdpyinfo missing>
**OpenGL:** **renderer:** Mesa DRI Intel Iris Plus Graphics 655 (CFL GT3) **v:** 4.6 Mesa 20.2.3
**Audio: Device-1:** Intel Cannon Point-LP High Definition Audio **driver:** snd_hda_intel
**Sound Server:** ALSA **v:** k5.9.11-1-default
**Network: Device-1:** Intel Cannon Point-LP CNVi [Wireless-AC] **driver:** iwlwifi
**IF:** wlp0s20f3 **state:** down **mac:** 92:c7:4e:0a:43:b8
**Device-2:** Intel Ethernet I219-V **driver:** e1000e
**IF:** eno1 **state:** up **speed:** 100 Mbps **duplex:** full **mac:** 1c:69:7a:00:6a:55
**Drives: Local Storage:** **total:** 1.14 TiB **used:** 29.92 GiB (2.6%)
**ID-1:** /dev/nvme0n1 **vendor:** Samsung **model:** SSD 970 EVO Plus 250GB **size:** 232.89 GiB
**ID-2:** /dev/sda **vendor:** Samsung **model:** SSD 860 EVO 1TB **size:** 931.51 GiB
**Partition: ID-1:** / **size:** 230.38 GiB **used:** 29.84 GiB (13.0%) **fs:** btrfs **dev:** /dev/nvme0n1p2
**ID-2:** /home **size:** 230.38 GiB **used:** 29.84 GiB (13.0%) **fs:** btrfs **dev:** /dev/nvme0n1p2
**ID-3:** /opt **size:** 230.38 GiB **used:** 29.84 GiB (13.0%) **fs:** btrfs **dev:** /dev/nvme0n1p2
**ID-4:** /var **size:** 230.38 GiB **used:** 29.84 GiB (13.0%) **fs:** btrfs **dev:** /dev/nvme0n1p2
**Swap: ID-1:** swap-1 **type:** partition **size:** 2.00 GiB **used:** 0 KiB (0.0%) **dev:** /dev/nvme0n1p3
**Sensors: System Temperatures:** **cpu:** 36.0 C **mobo:** 27.8 C
**Fan Speeds (RPM):** N/A
**Info: Processes:** 254 **Uptime:** N/A **Memory:** 7.63 GiB **used:** 1.14 GiB (14.9%) **Shell:** bash **inxi:** 3.1.00
Hi
So tested live GNOME (20201224) on the laptop with an E2-7110 with R2 GPU and AC 3165/iwlwifi all good, connects fine 433M/b@5.2GHz on 5.10.1 kernel… can duplicate the issue on the A10-9600P model no desktop, can boot to console with nomodeset and runlevel 3.
Same errors with 5.10.1-default kernel (tumbleweed 20201222 & 20201224). Machine boots fine with 5.9.XX kernels, but hangs either at the “Tumbleweed” loading page (i.e. never makes it to LUKS decrypt) or prints a page of
> BUG: workqueue lockup – pool cpus=13 node=0 flags=0 nice=0 stuck for 254s!
- Lenovo T14 with Ryzen 4750U
- Tumbleweed 20201224
I missed this the first time around. I have Tumbleweed on an SSD. I should try an old-school drive to see what happens.
just to confirm I’m also seeing this.
On a Lenovo thinkcentre
Using iwlwifi
intel gpu
exiting plymouth I see a continue scroll of . . .
A start job is running for user login management
A start job is running for HOLD until boot process finishes up
A start job is running for purge old kernels
reverting to 5.9.xx kernel all is good
Well I just updated my TW/KDE ASUS I7 laptop to this level and it boots fine. It has an SSD and uses Wi-Fi and all working perfectly as far as I can see. So now to undrstand the differences between this laptop and my desktop which fails with this kernel.
Stuart
Hi All,
Exact identical error for me with kernel 5.10.1 - using plasma.
In the meantime I’ve reverted back to previous kernel in order to boot my laptop. Asus Tuf Gaming Machine
Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz
Memory: 15.5 GiB of RAM
Graphics Processor: GeForce GTX 1050 Ti/PCIe/SSE2
I see the same, plus other stuff, on my Lenovo IdeaPad.
I just tried the workaround described at
https://bugzilla.suse.com/show_bug.cgi?id=1180344#c16
Now Kernel 5.10.1 boots fine on my machine and i can’t see any further problems so far.
Regards
susejunky
Well I thought in for a penny in for a pound I might as well try that, and it worked - my desktop now boots with kernel 5.10.1.
Stuart
The above worked for me too.
[QUOTE=broadstairs;2991304]I just tried the workaround described at
https://bugzilla.suse.com/show_bug.cgi?id=1180344#c16
Now Kernel 5.10.1 boots fine on my machine and i can’t see any further problems so far.
/QUOTE]
I was about to say the same thing. I was snooping around for something else and found this too. I added that, powered down and booted 3 times (for good luck) and I run kernel 5.10.1 too. :good:
Dare I say that @broadstairs kindly pointed us to a “fix”? Thanks!!