From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 213391] AMDGPU retries page fault with some specific processes amdgpu and sometimes followed [gfxhub0] retry page fault until *ERROR* ring gfx timeout, but soft recovered
Date: Thu, 10 Jun 2021 12:51:52 +0000 [thread overview]
Message-ID: <bug-213391-2300-vM8ufvvVbS@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213391-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=213391
--- Comment #4 from Lahfa Samy (samy@lahfa.xyz) ---
I have about 1GB of VRAM currently set according to glxinfo:
Extended renderer info (GLX_MESA_query_renderer):
Vendor: AMD (0x1002)
Device: AMD Radeon(TM) Vega 10 Graphics (RAVEN, DRM 3.40.0, 5.12.9-arch1-1,
LLVM 12.0.0) (0x15d8)
Version: 21.2.0
Accelerated: yes
Video memory: 1024MB
Unified memory: no
Memory info (GL_ATI_meminfo):
VBO free memory - total: 42 MB, largest block: 42 MB
VBO free aux. memory - total: 2442 MB, largest block: 2442 MB
Texture free memory - total: 42 MB, largest block: 42 MB
Texture free aux. memory - total: 2442 MB, largest block: 2442 MB
Renderbuffer free memory - total: 42 MB, largest block: 42 MB
Renderbuffer free aux. memory - total: 2442 MB, largest block: 2442 MB
Memory info (GL_NVX_gpu_memory_info):
Dedicated video memory: 1024 MB
Total available memory: 4096 MB
Currently available dedicated video memory: 42 MB
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon(TM) Vega 10 Graphics (RAVEN, DRM 3.40.0,
5.12.9-arch1-1, LLVM 12.0.0)
How would I go about testing a patch ? (I probably need to rebuild the Linux
kernel with the patch, right and boot with it), I found this link, but it says
that the information in there is probably deprecated :
https://www.kernel.org/doc/html/v5.12/process/applying-patches.html
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-06-10 12:51 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 11:16 [Bug 213391] New: AMDGPU retries page fault with some specific processes amdgpu: [gfxhub0] retry page fault until *ERROR* ring gfx timeout, but soft recovered bugzilla-daemon
2021-06-10 11:33 ` [Bug 213391] " bugzilla-daemon
2021-06-10 11:43 ` bugzilla-daemon
2021-06-10 12:34 ` [Bug 213391] AMDGPU retries page fault with some specific processes amdgpu and sometimes " bugzilla-daemon
2021-06-10 12:34 ` [Bug 213391] AMDGPU retries page fault with some specific processes amdgpu and sometimes followed " bugzilla-daemon
2021-06-10 12:36 ` bugzilla-daemon
2021-06-10 12:51 ` bugzilla-daemon [this message]
2021-06-10 13:09 ` bugzilla-daemon
2021-06-10 13:19 ` bugzilla-daemon
2021-06-10 17:41 ` bugzilla-daemon
2021-06-10 19:45 ` bugzilla-daemon
2021-06-11 7:31 ` bugzilla-daemon
2021-06-11 23:32 ` bugzilla-daemon
2021-06-12 23:02 ` bugzilla-daemon
2021-06-13 17:43 ` bugzilla-daemon
2021-06-14 8:01 ` bugzilla-daemon
2021-06-15 22:14 ` bugzilla-daemon
2021-06-16 8:51 ` bugzilla-daemon
2021-06-16 10:46 ` bugzilla-daemon
2021-06-16 20:55 ` bugzilla-daemon
2021-06-18 18:27 ` bugzilla-daemon
2021-06-18 20:30 ` bugzilla-daemon
2021-06-19 12:15 ` bugzilla-daemon
2021-06-20 13:02 ` bugzilla-daemon
2021-06-20 21:07 ` bugzilla-daemon
2021-06-21 7:04 ` bugzilla-daemon
2021-06-21 18:55 ` bugzilla-daemon
2021-06-21 19:26 ` bugzilla-daemon
2021-06-29 23:55 ` bugzilla-daemon
2021-06-29 23:58 ` bugzilla-daemon
2021-06-30 19:00 ` bugzilla-daemon
2021-07-05 16:55 ` bugzilla-daemon
2021-07-06 17:35 ` bugzilla-daemon
2021-07-08 18:24 ` bugzilla-daemon
2021-07-08 18:28 ` bugzilla-daemon
2021-07-15 13:29 ` bugzilla-daemon
2021-07-15 13:31 ` bugzilla-daemon
2021-08-14 21:00 ` bugzilla-daemon
2021-09-10 11:46 ` bugzilla-daemon
2021-09-10 13:29 ` bugzilla-daemon
2021-11-19 13:28 ` 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-213391-2300-vM8ufvvVbS@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.