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: Wed, 08 Aug 2018 23:13:20 +0000 [thread overview]
Message-ID: <bug-107152-502-aF31HaM47l@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107152-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1191 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107152
--- Comment #12 from dwagner <jb5sgc1n.nya@20mm.eu> ---
Indeed, I found my theory confirmed by many experiments: If I use a script like
> #!/bin/bash
> cd /sys/class/drm/card0/device
> echo manual >power_dpm_force_performance_level
> # low
> echo 0 >pp_dpm_mclk
> echo 0 >pp_dpm_sclk
> # medium
> #echo 1 >pp_dpm_mclk
> #echo 1 >pp_dpm_sclk
> # high
> #echo 1 >pp_dpm_mclk
> #echo 6 >pp_dpm_sclk
to enforce just any performance level, then the crashes do not occur anymore -
also with the "low frame rate video test".
So it seems that the transition from one "dpm" performance level to another,
with a certain probability, causes these crashes. And the more often the
transitions occur, the sooner one will experience them.
The dynamic power management issue can now be pursued with the original bug
report https://bugs.freedesktop.org/show_bug.cgi?id=102322 for the
vm_update_mode=0 case - there is probably not much sense in keeping this bug
report open just because errors also occur with wm_update_mode=3, just less
often.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2332 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-08 23:13 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
2018-08-08 23:13 ` bugzilla-daemon [this message]
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-aF31HaM47l@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 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.