Fixes screen flicker issue introduced in 5.9.12. Test suite results:

Test suite called with default
./default/cachedrop                                              FAIL    
./default/insert_leap_second                                     PASS    
./default/libhugetlbfs                                           SKIP    
./default/memfd                                                  PASS    
./default/modsign                                                PASS    
./default/mq-memory-corruption                                   PASS    
./default/paxtest                                                SKIP    
./default/posix_timers                                           PASS    
./default/selinux-dac-controls                                   PASS    
./default/stack-randomness                                       PASS    
./default/sysfs-perms                                            PASS    
./default/timer-overhead                                         PASS    

Test suite complete                                              FAIL   

Works on Acer Aspire Intel® Core™ i7-3632QM CPU @ 2.20GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000. wi-fi: Qualcomm Atheros AR9485 Wireless Network Adapter vendor: Lite-On driver: ath9k v: kernel pcie: speed: 2.5 GT/s lanes: 1

Passed ALL kernel regression tests.

Looks ok for me. Works on baremetal (non UEFI mode) AMD Ryzen5 3600, Mainboard MSI B450M Mortar Max with prop. nvidia driver (515.76) from rpmfusion.org (GTX980 card). Works with Gnome-Desktop (Xorg).

Default & performance tests pass (KVM)

Default and performance regression tests PASS on both a Dell XPS 13 9350 laptop and on a NUC6.

1) Dell XPS 13 9350, Intel Core i7-6560U CPU @ 2.20GHz × 4, Mesa Intel Iris(R) Graphics 540 (SKL GT3). This laptop with an Intel GPU didn't have the flickering problem on 5.19.12 and is still working fine with 5.19.13.

2) NUC6i5SYK, Intel Core i5-6260U CPU @ 1.80GHz × 4, Mesa Intel Iris(R) Graphics 540 (SKL GT3).

@nivag can you explain how this fails to boot? Does 5.19.12 boot on that system? The only difference between the 2 kernels is a revert of some i915 patches which can potentially damage laptop hardware. If you are seeing any issue not related to i915, it is likely systemd or firmware related. We need to figure it out though because the longer it takes for this update to make stable, the more exposure users have to potential damage.

./runtests.sh PASS on 5.19.13-200.fc36.x86_64 with Intel Core i7-4720HQ, NVIDIA GM204M [GeForce GTX 970M] driver: nouveau

cat /proc/sys/kernel/tainted 
0

I tested multiple applications on it; works properly as virtualization/KVM host including PCI passthrough (intel_iommu=on). No issues.

./runtests.sh -t performance not yet tested.

The issue with Intel video on Dell Precision 7510 is resolved.

@jforbes

This is hand transcribed, so there maybe typos...

0b00 1048575 sr0 driver: sr Kernel panic - not syncing: VFS: Unable to mount root fs on uknown-block(0.0) CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.19.13-200.fc36.x86-64 #1 Hardware name: LENOVO 4236DK9/4236DK9, BIOS 83ETG3WW (1.33) 07/29/2011 Call Trace: <TASK> dump_stack_lvl+0x44/0x5c panic+0xfb/0x2b1 mount_block_root+0x13f/0x1d9 prepare_namespace+0x13b/0x16a kernel_init_freeable+0x23f/0x24e ? rest_init+0xd0/0xd0 kernel_init+0x16/0x140 ret_from_fork+0x22/0c30 </TASK> Kernel Offset: 0x24000000 from 0xffffffff81000000 (relocation range 0xffffffff80000000-0xffffffffbfffff)

This is hand transcribed, so there maybe typos...

0b00 1048575 sr0

driver: sr

Kernel panic - not syncing: VFS: Unable to mount root fs on uknown-block(0.0)

CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.19.13-200.fc36.x86-64 #1

Hardware name: LENOVO 4236DK9/4236DK9, BIOS 83ETG3WW (1.33) 07/29/2011

Call Trace:

<TASK>

dump_stack_lvl+0x44/0x5c

panic+0xfb/0x2b1

mount_block_root+0x13f/0x1d9

prepare_namespace+0x13b/0x16a

kernel_init_freeable+0x23f/0x24e

? rest_init+0xd0/0xd0

kernel_init+0x16/0x140

ret_from_fork+0x22/0c30

</TASK>

Kernel Offset: 0x24000000 from 0xffffffff81000000 (relocation range 0xffffffff80000000-0xffffffffbfffff)

5.19.12 boots fine and I can log in as my normal use test cases all passed

@nivag - it seems initramfs of your kernel is missing, corrupt or empty. This usually happens when scripts that generate it do not complete successfully, for whatever reason (lack of space, interrupted mid run etc.).

Works for me: all using the Mate Desktop Environment. (Results for sirius & mercury copied from above.)

sirius: desktop 16GB Intel i7-3770 CPU desktop (SSD + 5 hard drives in RAID-6) real:10m39.751s user:4m38.572s sys:4m56.453s

sedna: laptop 8GB Intel i5-2520M CPU Lenovo T420 (SSD only) real:8m58.366s user:3m24.996s sys:4m28.498s // ran faster than normal! Deleted & reinstalled -- laptop ran out of battery near end of previous install

mercury: laptop 32GB AMD Ryzen 7 5700U with Radeon 5500 Graphics (SSD only) rea1:19m42.440s user:9m28.090s sys:7m32.605s

*** I’m intensely curious as to the reason for why sedna seems to randomly fluctuate between short (normally under 11 minutes) & extremely long (100+ minutes) elapsed times for the performance test!

Fixes display issues and kernel panic on my 11th Gen Intel laptop that occur with 5.9.12. All good now.

Default & performance tests pass (KVM)

and now 5.19.14 is out ;-) @jforbes Thank you for buildung and pushing 5.19.13 so fast to the Fedora-Users.