[root@raven linux]# file
/lib/modules/4.18.0-rc1+/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko
/lib/modules/4.18.0-rc1+/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko:
ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV),
BuildID[sha1]=14495041edc0ecb2d4159e8ee15e87f345ae2ef9, with debug_info,
not stripped
Tom
On 07/18/2018 12:44 PM, Michel Dänzer wrote:
On 2018-07-18 06:17 PM, Michel Dänzer wrote:
On 2018-07-18 06:05 PM, Tom St Denis wrote:
Hi Christian,
This patch:
[root@raven linux]# git bisect bad
90f362bdf0d0d06a126a5fd35b084436dd8250ad is the first bad commit
commit 90f362bdf0d0d06a126a5fd35b084436dd8250ad
Author: Christian König <[email protected]>
Date: Mon Jul 16 14:58:48 2018 +0200
drm/amdgpu: change ring priority after pushing the job
Pushing a job can change the ring assignment of an entity.
Signed-off-by: Christian König <[email protected]>
Reviewed-by: Chunming Zhou <[email protected]>
:040000 040000 9a09d3e9d055e4f5024019861c334ee9cc0bd11b
522540c31c3d1a4f4a6fbac75e985e9a7f7e93c9 M drivers
causes a KASAN while running piglit. It's reproduceable 100% of the
time. The commit before this doesn't not cause a KASAN.
I got the attached KASAN use-after-free report while running piglit
today, could be the same?
Sorry, that was for a different issue. Here's the KASAN report.
Tom, what does the file command say about the amdgpu.ko file loaded on
your system?
_______________________________________________
amd-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
