β¦ β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 β¦