https://bugzilla.kernel.org/show_bug.cgi?id=199357
--- Comment #11 from Alex Deucher (alexdeuc...@gmail.com) ---
Yes, the revert cc'ed stable so it will show up in 4.16 as well.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=199357
--- Comment #10 from Mathias Tillman (master.ho...@gmail.com) ---
Since that commit was pushed to v4.16, shouldn't it also be reverted on
linux-stable to make it to a future 4.16.y release?
--
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=199357
Mathias Tillman (master.ho...@gmail.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.kernel.org/show_bug.cgi?id=199357
Mathias Tillman (master.ho...@gmail.com) changed:
What|Removed |Added
Attachment #275291|0 |1
is
https://bugzilla.kernel.org/show_bug.cgi?id=199357
--- Comment #7 from Mathias Tillman (master.ho...@gmail.com) ---
Wanted to add some more info. The soft lock up will release after approximately
30 seconds, but after a few seconds it will lock up again and repeat.
Looking at the kernel log, it
https://bugzilla.kernel.org/show_bug.cgi?id=199357
--- Comment #6 from Michel Dänzer (mic...@daenzer.net) ---
(In reply to Harry Wentland from comment #5)
> I'm reluctant to just revert the offending commit as it's not incorrect
> but seems to expose some other flaws in our atomic check/commit
>
https://bugzilla.kernel.org/show_bug.cgi?id=199357
--- Comment #5 from Harry Wentland (harry.wentl...@amd.com) ---
I've no idea why this causes "flip_done timed out" and locks the system right
now, but we're currently also dealing with some more fallout from that change,
in particular
https://bugzilla.kernel.org/show_bug.cgi?id=199357
--- Comment #4 from Christian König (christian.koe...@amd.com) ---
Thanks, yeah that is clearly DC (display core).
Harry can you take a look?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=199357
--- Comment #3 from Mathias Tillman (master.ho...@gmail.com) ---
I've just finished running a bisect now, and I have concluded that commit
36cc549d59864b7161f0e23d710c1c4d1b9cf022 (drm/amd/display: disable CRTCs with
NULL FB on their primary
https://bugzilla.kernel.org/show_bug.cgi?id=199357
Christian König (christian.koe...@amd.com) changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=199357
--- Comment #1 from Mathias Tillman (master.ho...@gmail.com) ---
Created attachment 275293
--> https://bugzilla.kernel.org/attachment.cgi?id=275293=edit
Hardware info
--
You are receiving this mail because:
You are watching the assignee of
11 matches
Mail list logo
