<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [4.18rc2] RX470 dGPU on hybrid laptop freezes screen after use"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107045#c21">Comment # 21</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [4.18rc2] RX470 dGPU on hybrid laptop freezes screen after use"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107045">bug 107045</a>
from <span class="vcard"><a class="email" href="mailto:andrey.grodzovsky@amd.com" title="Andrey Grodzovsky <andrey.grodzovsky@amd.com>"> <span class="fn">Andrey Grodzovsky</span></a>
</span></b>
<pre>(In reply to taijian from <a href="show_bug.cgi?id=107045#c20">comment #20</a>)
<span class="quote">> OK, here is a new twist: upon further investigating this, I came across some
> weird backlight behaviour that I originally reported here:
> <a href="https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/53">https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/53</a>. However, as
> it turns out, this is not a gnome issue but a kernel one.
>
> Namely, doing
>
> echo X > /sys/class/backlight/intel_backlight/brightness
>
> will wake my dGPU, even though it really shouldn't be involved at all (and
> does not have a /sys/class/backlight device registered). Furthermore,
> repeatedly invoking this command before the dGPU has had the chance to go
> back to sleep will not do anything. Thirdly, this seems to be a very good
> way to get the system to hard lock up.
>
> So, is this an amdgpu issue? A i915 issue? ACPI? where should I take this
> bug report?</span >
What do you mean by 'wake' the dGPU? This should be a separate ticket which you
can submit here + attach dmesg after this 'wake'.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>