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 13:14:12 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0218640817==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 222DB8923C for ; Wed, 27 Dec 2017 13:14:12 +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 --===============0218640817== Content-Type: multipart/alternative; boundary="15143804520.8D9D5.1948"; charset="UTF-8" --15143804520.8D9D5.1948 Date: Wed, 27 Dec 2017 13:14:12 +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 #10 from Andrey Grodzovsky --- (In reply to higuita from comment #9) > Created attachment 136400 [details] > dmesg oops with kasan 2 >=20 > Another crash, this time in RUST, just to see if it helps in any way >=20 > i know how to build stuff, but i have no idea how to debug the kernel :) >=20 > can you please give me some pointers how to find and give you the needed > info? NP, check answer here https://stackoverflow.com/questions/13468286/how-to-read-understand-analyze= -and-debug-a-linux-kernel-panicand=20 to obtain the function address within your amdgpu.ko just do=20 nm -C drivers/gpu/drm/amd/amdgpu/amdgpu.ko | grep amdgpu_sync_get_fence nm -C drivers/gpu/drm/amd/amdgpu/amdgpu.ko | grep amdgpu_sync_resv The offset into the function you can see from the dmesg dump=20 amdgpu_sync_get_fence+0x91/0xe0 so 91 is the offset Thanks, Andrey (In reply to higuita from comment #9) > Created attachment 136400 [details] > dmesg oops with kasan 2 >=20 > Another crash, this time in RUST, just to see if it helps in any way >=20 > i know how to build stuff, but i have no idea how to debug the kernel :) >=20 > can you please give me some pointers how to find and give you the needed > info? --=20 You are receiving this mail because: You are the assignee for the bug.= --15143804520.8D9D5.1948 Date: Wed, 27 Dec 2017 13:14:12 +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

Comme= nt # 10 on bug 10429= 9 from Andrey Grodzovsky 
(In reply to higuita from comment #9)
> Created at=
tachment 136400 [details]
> dmesg oops with kasan 2
>=20
> Another crash, this time in RUST, just to see if it helps in any way
>=20
> i know how to build stuff, but i have no idea how to debug the kernel =
:)
>=20
> can you please give me some pointers how to find and give you the need=
ed
> info?

NP, check answer here
https://stackoverflow.com/qu=
estions/13468286/how-to-read-understand-analyze-and-debug-a-linux-kernel-pa=
nicand=20

to obtain the function address within your amdgpu.ko just do=20

nm -C drivers/gpu/drm/amd/amdgpu/amdgpu.ko | grep amdgpu_sync_get_fence
nm -C drivers/gpu/drm/amd/amdgpu/amdgpu.ko | grep amdgpu_sync_resv

The offset into the function you can see from the dmesg dump=20
amdgpu_sync_get_fence+0x91/0xe0 so 91 is the offset

Thanks,
Andrey

(In reply to higuita from comment #=
9)
> Created at=
tachment 136400 [details]
> dmesg oops with kasan 2
>=20
> Another crash, this time in RUST, just to see if it helps in any way
>=20
> i know how to build stuff, but i have no idea how to debug the kernel =
:)
>=20
> can you please give me some pointers how to find and give you the need=
ed
> info?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15143804520.8D9D5.1948-- --===============0218640817== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0218640817==--