Arch Linux User Repository

• Leaving eclairvoyant's comment pinned because it contains some useful information.
• Patch policy is different, but similar.
  • Primary purpose of this package are the ACS override and i915 VGA arbiter patches.
  • Upstream Arch patches will be applied to maintain parity with the standard kernel.
  • No other patches will be added.
• Package does have options that can be changed, like building with clang or disabling Arch patches.
  • Defaults will match Arch packages, except when incompatible with this package's primary patches.
  • Options are subject to change. Read PKGBUILD for details.
• Avoid commenting and flagging at the same time for the same issue.
  • Flag for common issues with standard solutions, like new releases, key changes, etc.
  • Comment for issues requiring explanation or debugging.
    • Use a pastebin for blocks of text more than a few lines.

This package exists for the specific purpose of adding ported patches based on those originally created by Alex Williamson for:

• Bypassing the default IOMMU grouping by overriding PCIe ACS support, and

• Enabling VGA arbitration support on Intel iGPUs.

Arbitrary patches will not be added.

Refer to the wiki on PCI passthrough and this blog post on IOMMU groups for risks/caveats before using this package.

Regular AUR etiquette applies as well (knowledge of makepkg and searching the wiki/Arch forums is expected, and AUR helpers or Arch-based distros that are not Arch Linux are unsupported).

I'll admit I don't know much in the ways of DRI or internal kernel workings. There's a patchset that has been penned by Andrey Grodzovsky, a Software Engineer at AMD, that purports to resolve some of these issues. For those using AMDGPU who are experiencing issues, I suggest you read his patch summary, and look into testing these patches on your system(s).

I hope that in the coming days/weeks more detailed information and better patches will be released; it looks like this, at the very least, has the attention of AMD.

https://lists.freedesktop.org/archives/dri-devel/2020-May/265386.html

QEMU5 update is breaking windows VM's on newer Ryzen processors. Apparently fix is to disable amd-stibp in the cpu flags or use earlier kernel for the moment. Various workarounds in the vfio discord.

I get the same error as purploid, AMD host GPU, passing down an Nvidia; last kernel update seems to have broken something because switching to LTS fixed it. I'm on x570 chipset if that matters

markzz: I am not. I am using AMDGPU for my host system and am passing an nvidia card to the guest VM. It's possible there was another change somewhere along the way but this issue popped up after upgrading from 5.6.8 to 5.6.10-1.

I am finding that the LTS kernel doesn't give me this issue. Now that I can boot the Windows guest, the only thing I can see in the minidump file is NTOSKRNL.exe crashing which doesn't give me much to go on and I haven't had any major updates on the guest VM in a while.

purploid: Are you using i915 VGA arbitration?

@slowbro thank you, but I have already set that option.

These GSOD/BSOD errors only started after I updated to this kernel. I switched to vfio-lts and it's working again.

I'll try the non-lts version in a few updates and see if that stabilizes things.

@purploid https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF#Bluescreen_at_boot_since_Windows_10_1803

@markzz I am currently unable to boot my Windows VM with "KERNEL SECURITY CHECK FAILURE" Blue/Green Screen of Death.

I have attempted to boot into Windows Installer as well and I am seeing the same behaviour on a brand new ISO from MS.

Anyone who uses this PKGBUILD that actually uses the i915 VGA Arbitration patch, please let me know if you are currently having issues. It looks like to me that there's an issue in the current patch, but I do not personally use that part of this kernel.

I will be updating to 5.6.10.arch1-2 in the coming hours and would like to know if anyone can confirm my hunch.

Pushed commit 757f0700.