[Bug 104299] Crash on amdgpu_sync_get_fence - bugzilla-daemon

From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104299] Crash on amdgpu_sync_get_fence
Date: Wed, 27 Dec 2017 04:29:07 +0000	[thread overview]
Message-ID: <bug-104299-502-YiJdYQlfwp@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104299-502@http.bugs.freedesktop.org/>

[-- Attachment #1.1: Type: text/plain, Size: 822 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=104299

--- Comment #8 from Andrey Grodzovsky <andrey.grodzovsky@amd.com> ---
(In reply to higuita from comment #7)
> Created attachment 136398 [details]
> dmesg oops with kasan
> 
> Sure, there is the dmesg after a crash with kasan, this time over warthunder

Thanks, this seems like trying to access a fence which already was released,
but i can't pinpoint the faulting line in the code both for
amdgpu_sync_get_fence and for amdgpu_sync_resv, I am using addr2line for this
but the offset into the function shown in the backtrace doesn't make sense.
Maybe because our builds differ, can you try it and see if you get the exact
offending lines in both functions ?

Thanks,
Andrey

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1855 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel