From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107152] GPU fault detected: 146 / VM_CONTEXT1_PROTECTION_FAULT / ring gfx timeout
Date: Sun, 05 Aug 2018 19:59:27 +0000 [thread overview]
Message-ID: <bug-107152-502-rVNkGVbjcv@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107152-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1072 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107152
--- Comment #11 from dwagner <jb5sgc1n.nya@20mm.eu> ---
I did some additional experiments to understand what is so special about the
"Othan" video that playing it causes amdgpu to crash relatively fast.
Since the only "odd" parameter of it is its "6 fps" frame rate, I tried
replaying other videos, first at their normal rate (like 24 fps), which did not
cause quick crashes, then at an artificially lower set rate - and indeed, that
causes fast crashing regardless of what video I play.
The framerate that caused the "quickest" crashing seemed to be 3 fps, running
> mpv --no-correct-pts --fps=3 --ao=null some_arbitrary_video.webm
was usually crashing amd-staging-drm-next within < 1 minute for me.
Just some random thought: Could the reason be some timed hysteresis in power
management of the GPU?
Would there be some possibility to lock the GPU on a specific power level to
then try if those crashes still occur?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1974 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:[~2018-08-05 19:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-07 20:03 [Bug 107152] GPU fault detected: 146 / VM_CONTEXT1_PROTECTION_FAULT / ring gfx timeout bugzilla-daemon
2018-07-07 20:04 ` bugzilla-daemon
2018-07-07 20:05 ` bugzilla-daemon
2018-07-30 21:12 ` bugzilla-daemon
2018-07-31 21:41 ` bugzilla-daemon
2018-07-31 21:45 ` bugzilla-daemon
2018-08-02 21:25 ` bugzilla-daemon
2018-08-02 21:54 ` bugzilla-daemon
2018-08-03 16:54 ` bugzilla-daemon
2018-08-03 23:42 ` bugzilla-daemon
2018-08-03 23:48 ` bugzilla-daemon
2018-08-05 19:59 ` bugzilla-daemon [this message]
2018-08-08 23:13 ` bugzilla-daemon
2018-08-09 16:25 ` bugzilla-daemon
2018-08-09 20:56 ` bugzilla-daemon
2019-01-24 6:45 ` 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-107152-502-rVNkGVbjcv@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