Josef Johansson

The Xen processor (-19) from ACPI errors go away if I boot the kernel with nosmt, obviously. In the console with lightdm never started it can survive at least 5-6...

There is a problem with installing xorg-x11-driver-amdgpu, X won't start with errors related to unwind information not existing.I tried installing kernel-devel to make the amdgpu driver happy but it did...

Compiling the kernel without the mentioned flags above I managed to do a sleep/resume a lot longer. When X is running it still dies on 'failed to terminate hdcp ta'...

For those wondering how to build xen, here is my builder.conf. ``` # Since it's a very upstream branch INSECURE_SKIP_CHECKING = vmm-xen GIT_URL_vmm_xen = https://github.com/marmarek/qubes-vmm-xen BRANCH_vmm_xen = update-4.14.3 COMPONENTS =...

amdgpu xorg driver now works with xorg-x11-drv-amdgpu-21.0.0-1 (https://fedora.pkgs.org/33/fedora-updates-x86_64/xorg-x11-drv-amdgpu-21.0.0-1.fc33.x86_64.rpm.html), not stable during suspend/resume or removing jitter after resume.

@johnnyboy-3 do you have xorg-x11-drv-amdgpu installed?

@johnnyboy-3 the correct _kernel_ parameter should be nosmt btw. It's odd that xen_acpi_processor tries to send updates to XEN on thread number 2 on each processor, even though the kernel...

cool, so like a normal VM then. So like xen_acpi_processor trying to send up information about 16 cores can just be ignored. Trying to understand and pin down exactly what...

I just tried out kernel 5.15-rc5 and it's still the same behavior, however I had the laptop in sleep for the whole night and it woke up fine. Still this...

Yay, latest kernel-ark with ``` CONFIG_SND_SOC_AMD_RENOIR=n CONFIG_DRM_AMD_DC_HDCP=n CONFIG_DRM_AMD_SECURE_DISPLAY=n CONFIG_HSA_AMD_SVM=n CONFIG_AMD_MEM_ENCRYPT=n ``` booting with kernel options `pci=nomsi` Now it actually suspends/resumes correctly. Attached is lspci -vv with Enable+ selected. [lscpi-msi.log](https://github.com/QubesOS/qubes-issues/files/7296624/lscpi-msi.log)