From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 107045] [4.18rc2] RX470 dGPU on hybrid laptop freezes screen
after use
Date: Tue, 28 Aug 2018 22:14:39 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0402703708=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id 012046E424
for ; Tue, 28 Aug 2018 22:14:39 +0000 (UTC)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============0402703708==
Content-Type: multipart/alternative; boundary="15354944780.abf044CE8.26800"
Content-Transfer-Encoding: 7bit
--15354944780.abf044CE8.26800
Date: Tue, 28 Aug 2018 22:14:38 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D107045
--- Comment #21 from Andrey Grodzovsky ---
(In reply to taijian from comment #20)
> OK, here is a new twist: upon further investigating this, I came across s=
ome
> weird backlight behaviour that I originally reported here:
> https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/53. However, =
as
> it turns out, this is not a gnome issue but a kernel one.
>=20
> Namely, doing=20
>=20
> echo X > /sys/class/backlight/intel_backlight/brightness
>=20
> 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.
>=20
> So, is this an amdgpu issue? A i915 issue? ACPI? where should I take this
> bug report?
What do you mean by 'wake' the dGPU? This should be a separate ticket which=
you
can submit here + attach dmesg after this 'wake'.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15354944780.abf044CE8.26800
Date: Tue, 28 Aug 2018 22:14:38 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
Comme=
nt # 21
on bug 10704=
5
from Andrey Grodzovsky
(In reply to taijian from comment #20)
> OK, here is a new twist: upon further investigat=
ing this, I came across some
> weird backlight behaviour that I originally reported here:
> https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/53. Ho=
wever, as
> it turns out, this is not a gnome issue but a kernel one.
>=20
> Namely, doing=20
>=20
> echo X > /sys/class/backlight/intel_backlight/brightness
>=20
> 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 g=
ood
> way to get the system to hard lock up.
>=20
> So, is this an amdgpu issue? A i915 issue? ACPI? where should I take t=
his
> bug report?
What do you mean by 'wake' the dGPU? This should be a separate ticket which=
you
can submit here + attach dmesg after this 'wake'.
You are receiving this mail because:
- You are the assignee for the bug.
=
--15354944780.abf044CE8.26800--
--===============0402703708==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============0402703708==--