Comment 7 for bug 2056445

Revision history for this message
Mario Limonciello (superm1) wrote (last edit ):

> Am I missing something to get the proposed
kernel?

I guess the same reason it's not migrating is the reason you can't install it? Maybe some kernel team members can comment.

> It sounds like GTT access is what causes this issue, and that using the
bios option won't guarantee that it will never happen. Is that correct?

If you look at your journal from when this issue occurs you'll see an IOMMU page fault. This is the IOMMU reporting that there was an attempted access at memory that is out of the region that the GPU is allowed to access. This can happen when there is a userspace driver bug (IE mesa) or a misconfigured driver (IE amdgpu) or a faulty firmware (IE the BIOS).

There have been cases of a white screen caused by an incorrect memory addressing mask on systems with 64GB, but that's been fixed a long time now.

It is definitely an attempt at accessing outside of VRAM but I have a suspicion the address attempting to be addressed is ALSO outside of GTT.

> Interesting. If there's any extra info (or testing) I can provide to help
with debugging/fixing this issue, please let me know.

If you can add your details for your "specific" FW13 AMD to the upstream bug maybe others who are affected can help with building the pattern.
I mean the memory vendor, speed of memory, amount, channel configuration.

What you do to trigger it, etc.