… “acpi=off” leads to a boot-process without boot-console and a wrong resolution with wayland / gnome …
In relation to my suspicion that the display card driver nouveau causes the problems, I turned off hyper threading in the BIOS and added “pci=biosirq” to the kernel parameters in grub configuration …
The laptop boots fine now again (with boot console and right resolution). The nouveau related interrupts looks like this:
grep nvkm /proc/interrupts
29: 0 (CPU 0) 103958 (CPU1) PCI-MSI 524288-edge nvkm
and not anymore like this before disabling hyper threading in the BIOS:
grep nvkm /proc/interrupts
29: 0 (CPU 0) 0 (CPU1) 1504756 (CPU 2) 0 (CPU 3) PCI-MSI 524288-edge nvkm
… I’ll wait and see what happens … I’ll report here …
… it was a try … no more … but the problem still exists …
I did some performance analyzing with perf while the error situation appears and get the following dump:
Samples: 57K of event 'cycles', Event count (approx.): 39393633680
Children Self Command Shared Object Symbol
+ 77,49% 0,00% kworker/u4:0+ev [kernel.kallsyms] [k] ret_from_fork â—†
+ 77,49% 0,00% kworker/u4:0+ev [kernel.kallsyms] [k] kthread â–’
+ 77,49% 0,00% kworker/u4:0+ev [kernel.kallsyms] [k] worker_thread â–’
+ 77,49% 0,00% kworker/u4:0+ev [kernel.kallsyms] [k] process_one_work â–’
+ 77,49% 0,00% kworker/u4:0+ev [nouveau] [k] nv50_disp_atomic_commit_tail â–’
- 73,26% 73,10% kworker/u4:0+ev [kernel.kallsyms] [k] ioread32 â–’
73,10% ret_from_fork â–’
kthread â–’
worker_thread â–’
process_one_work â–’
- nv50_disp_atomic_commit_tail â–’
- 44,75% nv50_wndw_flush_set â–’
- 29,07% base507c_ntfy_set â–’
- nv50_dmac_wait â–’
- 22,31% nvif_timer_wait_test â–’
nvif_device_time â–’
nvif_object_mthd â–’
- nvkm_ioctl â–’
- 22,31% nvkm_udevice_mthd â–’
- nv04_timer_read â–’
ioread32 â–’
6,71% ioread32 â–’
- 15,67% base827c_image_set â–’
- nv50_dmac_wait â–’
- 12,13% nvif_timer_wait_test â–’
nvif_device_time â–’
nvif_object_mthd â–’
- nvkm_ioctl â–’
- 12,13% nvkm_udevice_mthd â–’
- 12,12% nv04_timer_read â–’
ioread32 â–’
3,51% ioread32 â–’
- 15,77% nv50_disp_atomic_commit_wndw â–’
base507c_update â–’
- nv50_dmac_wait
- nv50_dmac_wait â–’
- 12,29% nvif_timer_wait_test â–’
nvif_device_time â–’
nvif_object_mthd â–’
nvkm_ioctl â–’
- nvkm_udevice_mthd â–’
- 12,29% nv04_timer_read â–’
ioread32 â–’
3,44% ioread32 â–’
- 12,59% base507c_ntfy_wait_begun â–’
- 8,10% nvif_timer_wait_test â–’
nvif_device_time â–’
nvif_object_mthd â–’
nvkm_ioctl â–’
- nvkm_udevice_mthd â–’
- 8,10% nv04_timer_read â–’
ioread32 â–’
4,47% ioread32 â–’
+ 62,36% 0,04% kworker/u4:0+ev [nouveau] [k] nv50_dmac_wait â–’
+ 56,97% 0,04% kworker/u4:0+ev [nouveau] [k] nvif_timer_wait_test â–’
+ 56,91% 0,04% kworker/u4:0+ev [nouveau] [k] nvif_device_time â–’
+ 56,87% 0,15% kworker/u4:0+ev [nouveau] [k] nvif_object_mthd â–’
+ 56,24% 0,23% kworker/u4:0+ev [nouveau] [k] nvkm_ioctl â–’
+ 55,49% 0,23% kworker/u4:0+ev [nouveau] [k] nvkm_udevice_mthd â–’
+ 55,20% 0,25% kworker/u4:0+ev [nouveau] [k] nv04_timer_read â–’
+ 46,19% 0,00% kworker/u4:0+ev [nouveau] [k] nv50_wndw_flush_set â–’
+ 29,98% 0,00% kworker/u4:0+ev [nouveau] [k] base507c_ntfy_set â–’
+ 16,21% 0,00% kworker/u4:0+ev [nouveau] [k] base827c_image_set â–’
+ 16,17% 0,00% kworker/u4:0+ev [nouveau] [k] nv50_disp_atomic_commit_wndw â–’
+ 16,17% 0,00% kworker/u4:0+ev [nouveau] [k] base507c_update â–’
+ 15,13% 0,03% kworker/u4:0+ev [nouveau]
It seems, that I’m not so wrong with my assessment. Since I don’t like NVIDA propriatory display drivers, I have to wait for updated nouveau kernel modules … you are welcome with any other suggestions …
This morning (12.12.2020) there was a kernel update in the fedora 33 update repository, so I switched from vmlinuz-5.9.12-200.fc33.x86_64 to 5.9.13-200.fc33.x86_64.
With this update there are many graphic related dependancies (like mesa-dri-drivers-20.2.4-1, mesa-libEGL-20.2.4-1, mesa-libGL-20.2.4-1, mesa-libOSMesa-20.2.4-1, mesa-libOpenCL-20.2.4-1, mesa-libgbm-20.2.4-1, mesa-libglapi-20.2.4-1, mesa-libxatracker-20.2.4-1, mesa-vulkan-drivers-20.2.3-1, …) included. I’ll cross my fingers …