From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107928] Screen regularly turns black, reboot needed
Date: Sun, 07 Oct 2018 21:10:16 +0000 [thread overview]
Message-ID: <bug-107928-502-YXxMXRxq3S@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107928-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1889 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107928
--- Comment #4 from dwagner <jb5sgc1n.nya@20mm.eu> ---
@ Vik-T: The way you describe your symptoms let it seem possible to me that you
are experiencing the very same long-standing bug that I reported in
https://bugs.freedesktop.org/show_bug.cgi?id=102322
If you want to verify if that bug and yours are actually the same, you could
try the following:
(a) Check whether you experience your bug also after disabling dynamic power
management. To do this, switch to manual power management like this:
> cd /sys/class/drm/card0/device
> echo manual >power_dpm_force_performance_level
> echo 0 >pp_dpm_mclk
> echo 0 >pp_dpm_sclk
In my case, the bug does not occur while clocks are set manually. Cave: These
settings are ignored/overwritten by the amdgpu driver after each display mode
change and each off/on of display output or monitor. So this test has meaning
only if manual settings are re-activated after each such display mode change /
on-switching. (This bug I reported with
https://bugs.freedesktop.org/show_bug.cgi?id=107141 )
(b) You could check if you can reproduce the symptom more quickly with a
certain load pattern:
(1) Enable dynamic power management (which is also the default)
(2) Start X11, but not any client (or desktop environment) that draws anything
on the screen
(3) Replay an (at least 1080p) video with only 3 frames per second, e.g. via:
"mpv --no-correct-pts --fps=3 --ao=null some_arbitrary_video.webm"
This kind of load causes (at least in the case of my system) frequent changes
to the pp_dpm_mclk and pp_dpm_sclk values, and the system crashes after only a
short while (seconds up to 15 minutes) under this kind of load, with the
symptom (blanked screen, system crash) you described.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3100 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-10-07 21:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 9:44 [Bug 107928] Screen regularly turns black, reboot needed bugzilla-daemon
2018-09-14 9:51 ` bugzilla-daemon
2018-09-14 10:01 ` bugzilla-daemon
2018-10-07 15:48 ` bugzilla-daemon
2018-10-07 21:10 ` bugzilla-daemon [this message]
2018-10-07 22:16 ` bugzilla-daemon
2018-10-08 22:02 ` bugzilla-daemon
2018-10-14 14:16 ` bugzilla-daemon
2018-10-14 14:16 ` bugzilla-daemon
2018-10-14 17:26 ` bugzilla-daemon
2018-10-17 22:35 ` bugzilla-daemon
2018-10-19 0:51 ` bugzilla-daemon
2018-10-19 7:23 ` bugzilla-daemon
2018-10-19 16:07 ` bugzilla-daemon
2018-11-05 20:12 ` bugzilla-daemon
2018-11-06 18:56 ` bugzilla-daemon
2019-11-19 8:55 ` 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-107928-502-YXxMXRxq3S@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