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: Thu, 02 Aug 2018 21:54:20 +0000 [thread overview]
Message-ID: <bug-107152-502-UINX6Mpr9P@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107152-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1277 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107152
--- Comment #7 from dwagner <jb5sgc1n.nya@20mm.eu> ---
(In reply to Andrey Grodzovsky from comment #6)
> dwanger, how quickly is this reproducible ?
With the above video playback test (which I should refer to as the "Othan"
test, because that is the name of the song in the video) actually quite fast -
never took more than 10 minutes so far to get to the crash.
> A wild guess, what if you boot kernel with IOMMU disabled ? Add iommu=off to
> grub command line.
Tried this: No difference, two attempts with current amd-staging-drm-next, one
with hw_update_mode=0 and one with hw_update_mode=3, both crashed in < 1 minute
of replay.
Interestingly, the "Othan test" can even crash the 4.13 kernel quicker then the
usual one or two days of uptime I can get with that old kernel.
There isn't really anything special with the video other than it being encoded
at only 6 frames per second.
And btw., the video replay crashes even with --vo=xv, so without mpv making use
of opengl. Replay does not crash with --vo=null.
In contrast, when I replay videos with the usual 24fps, this runs much longer
without crashing.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2232 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-02 21:54 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 [this message]
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
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-UINX6Mpr9P@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