https://bugzilla.kernel.org/show_bug.cgi?id=205915
--- Comment #15 from Manuel Ullmann (la...@posteo.de) ---
That fixed it. Thanks.
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel mailing list
https://bugzilla.kernel.org/show_bug.cgi?id=205915
--- Comment #14 from Alex Deucher (alexdeuc...@gmail.com) ---
See also:
https://bugzilla.kernel.org/show_bug.cgi?id=205915
https://bugzilla.kernel.org/show_bug.cgi?id=206393
https://bugzilla.kernel.org/show_bug.cgi?id=206575
--
You are
https://bugzilla.kernel.org/show_bug.cgi?id=205915
--- Comment #13 from Alex Deucher (alexdeuc...@gmail.com) ---
Does this series help?
https://patchwork.freedesktop.org/patch/353367/
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=205915
Manuel Ullmann (la...@posteo.de) changed:
What|Removed |Added
Attachment #287449|0 |1
is patch|
https://bugzilla.kernel.org/show_bug.cgi?id=205915
--- Comment #12 from Manuel Ullmann (la...@posteo.de) ---
Created attachment 287449
--> https://bugzilla.kernel.org/attachment.cgi?id=287449=edit
Call optimize bandwidth again.
I pinned the issue down to the four lines, which call
https://bugzilla.kernel.org/show_bug.cgi?id=205915
--- Comment #11 from Manuel Ullmann (la...@posteo.de) ---
Reverting 1ea8751bd28d1ec2b36a56ec6bc1ac28903d09b4 on HEAD, currently 5.5-rc7+,
seems to fix it. The revert should probably be limited to the 2 hunks in the
clock manager files to preserve
https://bugzilla.kernel.org/show_bug.cgi?id=205915
--- Comment #10 from Manuel Ullmann (la...@posteo.de) ---
Created attachment 286989
--> https://bugzilla.kernel.org/attachment.cgi?id=286989=edit
Kernel log of bad commit 1ea8751bd28d1ec2b36a56ec6bc1ac28903d09b4
--
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=205915
--- Comment #9 from Manuel Ullmann (la...@posteo.de) ---
Created attachment 286987
--> https://bugzilla.kernel.org/attachment.cgi?id=286987=edit
Xorg log of bad commit 1ea8751bd28d1ec2b36a56ec6bc1ac28903d09b4
--
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=205915
--- Comment #8 from Manuel Ullmann (la...@posteo.de) ---
Created attachment 286985
--> https://bugzilla.kernel.org/attachment.cgi?id=286985=edit
Kernel log of good commit 50575eb5b339683ee148189beae5eb53ccb3158b
--
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=205915
Manuel Ullmann (la...@posteo.de) changed:
What|Removed |Added
Attachment #286981|0 |1
is obsolete|
https://bugzilla.kernel.org/show_bug.cgi?id=205915
--- Comment #6 from Manuel Ullmann (la...@posteo.de) ---
Created attachment 286981
--> https://bugzilla.kernel.org/attachment.cgi?id=286981=edit
Xorg log on commit 50575eb5b339683ee148189beae5eb53ccb3158b
--
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=205915
Manuel Ullmann (la...@posteo.de) changed:
What|Removed |Added
CC||la...@posteo.de
---
https://bugzilla.kernel.org/show_bug.cgi?id=205915
--- Comment #4 from onil (o...@pm.me) ---
Please disregard comment #3, flickering still occurs when performance level is
"auto", after manually switching it to "low" or "high" flickering stops.
--
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=205915
--- Comment #3 from onil (o...@pm.me) ---
Problem only occurs when dpm_force_performance_level is set to "low" before
suspend. if dpm_force_performance_level is "auto" or "high" there is no
flickering after resume from suspend.
--
You are
https://bugzilla.kernel.org/show_bug.cgi?id=205915
--- Comment #2 from onil (o...@pm.me) ---
Created attachment 286367
--> https://bugzilla.kernel.org/attachment.cgi?id=286367=edit
dmesg after resume from suspend
--
You are receiving this mail because:
You are watching the assignee of the
https://bugzilla.kernel.org/show_bug.cgi?id=205915
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC|
16 matches
Mail list logo
