https://bugzilla.kernel.org/show_bug.cgi?id=212545
--- Comment #2 from aeder.re...@gmail.com ---
Ok, so I decided to run a git bisect on the upstream stable kernels seeing as
it was very likely this is a hardware specific bug and the result was the
following:
4932d37055e7a459a92424c4d21ebf8c2c0fb19a is the first bad commit
commit 4932d37055e7a459a92424c4d21ebf8c2c0fb19a
Author: Christian König <christian.koe...@amd.com>
Date: Tue Dec 8 16:19:42 2020 +0100
drm/amdgpu: limit the amdgpu_vm_update_ptes trace point
The text output should not be more than a page, so only print the first
32 page table entries.
If we need all of them we can still look into the binary trace.
Signed-off-by: Christian König <christian.koe...@amd.com>
Reviewed-by: Shashank Sharma <shashank.sha...@amd.com>
Signed-off-by: Alex Deucher <alexander.deuc...@amd.com>
drivers/gpu/drm/amd/amdgpu/amdgpu_trace.h | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
I'm not entirely sure how to proceed from this point onwards though.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
