https://bugzilla.kernel.org/show_bug.cgi?id=197925
kwka...@gmx.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=197925
--- Comment #15 from Harry Wentland (harry.wentl...@amd.com) ---
Thanks for the update.
If all original issues are closed can we mark this resolved? We can open new
tickets for new issues. Ideally we have one ticket per problem as some of them
ar
https://bugzilla.kernel.org/show_bug.cgi?id=197925
--- Comment #14 from kwka...@gmx.com ---
(In reply to Harry Wentland from comment #13)
> kwkaess, are you talking about the error message when saying "still not
> fixed" or the (arguably more disruptive and important) non-desirable
> behaviors men
https://bugzilla.kernel.org/show_bug.cgi?id=197925
Harry Wentland (harry.wentl...@amd.com) changed:
What|Removed |Added
CC||harry.wentl...@a
https://bugzilla.kernel.org/show_bug.cgi?id=197925
--- Comment #12 from kwka...@gmx.com ---
Still not fixed v4.15-11781-g413879a10b0b
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel mailing list
dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=197925
--- Comment #11 from Charles (ylang-yl...@libertysurf.fr) ---
Hi team,
Just to say... same error :
[drm:hwss_wait_for_blank_complete [amdgpu]] *ERROR* DC: failed to blank crtc!
with 4.15-rc4
(on the same noteboook)
--
You are receiving this
https://bugzilla.kernel.org/show_bug.cgi?id=197925
Charles (ylang-yl...@libertysurf.fr) changed:
What|Removed |Added
CC||ylang-yl...@liberty
https://bugzilla.kernel.org/show_bug.cgi?id=197925
--- Comment #9 from kwka...@gmx.com ---
#3 is fixed in both my monitor configurations.
#2 the behavior is still identical to Comment 5.
--
You are receiving this mail because:
You are watching the assignee of the bug.
__
https://bugzilla.kernel.org/show_bug.cgi?id=197925
--- Comment #8 from kwka...@gmx.com ---
As of 4.15.0-rc3-00086-g032b4cc8ff84:
#3 is fixed when in single internal monitor configuration. (Yes!)
I will, again, recheck #2 and #3 when I have an external monitor attached.
--
You are receiving thi
https://bugzilla.kernel.org/show_bug.cgi?id=197925
--- Comment #7 from kwka...@gmx.com ---
I have confirmed that the bug (with modified behavior as described above) is
still present on my hardware (Carrizo, specifically Toshiba L55D-C with AMD
A10-8700P), as of 4.15.0-rc2.
--
You are receiving t
https://bugzilla.kernel.org/show_bug.cgi?id=197925
--- Comment #6 from Miłosz Rachwał (kbz...@milek7.pl) ---
I just tested kernel built from Linus tree and everything works now, so
probably it is already fixed.
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
https://bugzilla.kernel.org/show_bug.cgi?id=197925
--- Comment #5 from kwka...@gmx.com ---
Half fixes #2:
On first idle and resume from idle after boot, everything works. Internal
monitor backlight shuts off, both screens turn back on. The second time, the
internal backlight stays on upon enterin
https://bugzilla.kernel.org/show_bug.cgi?id=197925
Miłosz Rachwał (kbz...@milek7.pl) changed:
What|Removed |Added
CC||kbz...@milek7.pl
---
https://bugzilla.kernel.org/show_bug.cgi?id=197925
--- Comment #3 from kwka...@gmx.com ---
running very recent kernel, 4.15.0-rc1-00396-ga0651c7fa2c0 (as automatically
labelled), with recent AMD_DC fixes.
Fixes 1 - backlight now shuts off.
Makes 3 worse - It put my internal monitor in a state (
https://bugzilla.kernel.org/show_bug.cgi?id=197925
beniwtv (beni...@relamp.tk) changed:
What|Removed |Added
CC||beni...@relamp.tk
--- Comme
https://bugzilla.kernel.org/show_bug.cgi?id=197925
--- Comment #1 from kwka...@gmx.com ---
From the initial description, 3) does not occur when external monitor is not
attached.
Also, the backlight can be adjusted manually.
--
You are receiving this mail because:
You are watching the assignee o
16 matches
Mail list logo
