From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 104299] Crash on amdgpu_sync_get_fence Date: Wed, 27 Dec 2017 04:29:07 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1513428515==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id A46BA8936B for ; Wed, 27 Dec 2017 04:29:07 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1513428515== Content-Type: multipart/alternative; boundary="15143489470.3998f2A4.28574"; charset="UTF-8" --15143489470.3998f2A4.28574 Date: Wed, 27 Dec 2017 04:29:07 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D104299 --- Comment #8 from Andrey Grodzovsky --- (In reply to higuita from comment #7) > Created attachment 136398 [details] > dmesg oops with kasan >=20 > Sure, there is the dmesg after a crash with kasan, this time over warthun= der 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 th= is 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 --=20 You are receiving this mail because: You are the assignee for the bug.= --15143489470.3998f2A4.28574 Date: Wed, 27 Dec 2017 04:29:07 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 8 on bug 10429= 9 from Andrey Grodzovsky 
(In reply to higuita from comment #7)
> Created atta=
chment 136398 [details]
> dmesg oops with kasan
>=20
> Sure, there is the dmesg after a crash with kasan, this time over wart=
hunder

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 th=
is
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.
= --15143489470.3998f2A4.28574-- --===============1513428515== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1513428515==--