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 13:14:12 +0000 [thread overview]
Message-ID: <bug-104299-502-cShDNPpREZ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104299-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1389 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104299
--- Comment #10 from Andrey Grodzovsky <andrey.grodzovsky@amd.com> ---
(In reply to higuita from comment #9)
> Created attachment 136400 [details]
> dmesg oops with kasan 2
>
> Another crash, this time in RUST, just to see if it helps in any way
>
> i know how to build stuff, but i have no idea how to debug the kernel :)
>
> 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
to obtain the function address within your amdgpu.ko just do
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
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
>
> Another crash, this time in RUST, just to see if it helps in any way
>
> i know how to build stuff, but i have no idea how to debug the kernel :)
>
> can you please give me some pointers how to find and give you the needed
> info?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2862 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
next prev parent reply other threads:[~2017-12-27 13:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-17 3:20 [Bug 104299] Crash on amdgpu_sync_get_fence bugzilla-daemon
2017-12-18 9:37 ` bugzilla-daemon
2017-12-18 15:21 ` bugzilla-daemon
2017-12-19 3:13 ` bugzilla-daemon
2017-12-19 3:19 ` bugzilla-daemon
2017-12-19 3:31 ` bugzilla-daemon
2017-12-24 4:41 ` bugzilla-daemon
2017-12-26 22:39 ` bugzilla-daemon
2017-12-27 4:29 ` bugzilla-daemon
2017-12-27 5:33 ` bugzilla-daemon
2017-12-27 13:14 ` bugzilla-daemon [this message]
2019-11-19 8:27 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-104299-502-cShDNPpREZ@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox