[Bug 100577] DC + TearFree display lock

https://bugs.freedesktop.org/show_bug.cgi?id=100577 Andy Furniss changed: What|Removed |Added Resolution|--- |WORKSFORME

[Bug 100577] DC + TearFree display lock

https://bugs.freedesktop.org/show_bug.cgi?id=100577 --- Comment #16 from Andy Furniss --- Created attachment 132467 --> https://bugs.freedesktop.org/attachment.cgi?id=132467=edit xrandr --verbose on 4.14-wip showing all modes This is xrandr on 4.14-wip - the higher modes

[Bug 100577] DC + TearFree display lock

https://bugs.freedesktop.org/show_bug.cgi?id=100577 --- Comment #15 from Andy Furniss --- It seems the errors in the dmesg are created when I do xrandr --verbose. -- You are receiving this mail because: You are the assignee for the

[Bug 100577] DC + TearFree display lock

https://bugs.freedesktop.org/show_bug.cgi?id=100577 --- Comment #14 from Andy Furniss --- Created attachment 132466 --> https://bugs.freedesktop.org/attachment.cgi?id=132466=edit xrandr --verbose higher clocks missing -- You are receiving this mail because: You are the

[Bug 100577] DC + TearFree display lock

https://bugs.freedesktop.org/show_bug.cgi?id=100577 --- Comment #13 from Andy Furniss --- Created attachment 132465 --> https://bugs.freedesktop.org/attachment.cgi?id=132465=edit dmesg on current staging memclk is stuck high + some errors -- You are receiving this mail

[Bug 100577] DC + TearFree display lock

https://bugs.freedesktop.org/show_bug.cgi?id=100577 --- Comment #12 from Andy Furniss --- Hmm, so I just booted back into current staging to get a dmesg and xrandr and ended up noticing 2 more issues. My monitor is 1920x1080 and can do 120Hz but pref and used by default is

[Bug 100577] DC + TearFree display lock

https://bugs.freedesktop.org/show_bug.cgi?id=100577 --- Comment #11 from Alex Deucher --- (In reply to Andy Furniss from comment #10) > Ugh, not 3.7s, I mean amd-staging-4.9s didn't peg memclk high. I don't still > have all the 4.11s I've ever built so don't know when this

[Bug 100577] DC + TearFree display lock

https://bugs.freedesktop.org/show_bug.cgi?id=100577 --- Comment #10 from Andy Furniss --- (In reply to Andy Furniss from comment #9) > One nit I notice is I may not be comparing like with like as current and > some older 4.11s I still have around all seem to peg memory

[Bug 100577] DC + TearFree display lock

https://bugs.freedesktop.org/show_bug.cgi?id=100577 --- Comment #9 from Andy Furniss --- Can't reproduce this on current amd-staging-4.11 will keep trying and close soon if OK. One nit I notice is I may not be comparing like with like as current and some older 4.11s I still

[Bug 100577] DC + TearFree display lock

https://bugs.freedesktop.org/show_bug.cgi?id=100577 --- Comment #8 from Andy Furniss --- I can still reproduce this. Seems I may just get lucky runs - one 90 mins no issue, stopped and started again later and it locked after 20. -- You are receiving this mail because: You

[Bug 100577] DC + TearFree display lock

https://bugs.freedesktop.org/show_bug.cgi?id=100577 --- Comment #7 from Harry Wentland --- This might've been fixed by Mario's patches plus Andrey's scanline change d58f8724e636 Mario Kleiner drm/amd/display: Prevent premature pageflip when comitting in vblank. (v3)

[Bug 100577] DC + TearFree display lock

https://bugs.freedesktop.org/show_bug.cgi?id=100577 --- Comment #6 from Andy Furniss --- Testing current amd-staging-4.9 + patch from Bug 101053 I can't reproduce this anymore. It was a couple of hours running, I'll try longer and with 4.11 over the next few days and either

[Bug 100577] DC + TearFree display lock

https://bugs.freedesktop.org/show_bug.cgi?id=100577 --- Comment #5 from Michel Dänzer --- (In reply to Nikola Forró from comment #4) > Which makes me think I'm experiencing a different issue, because this bug > was reported long before that commit emerged. Indeed; please

[Bug 100577] DC + TearFree display lock

https://bugs.freedesktop.org/show_bug.cgi?id=100577 --- Comment #4 from Nikola Forró --- Bisected to this commit: https://cgit.freedesktop.org/~agd5f/linux/commit/?h=amd-staging-4.9=afbeb2d0961b2139bcf6553a710e6a8ae5d09d34 Which makes me think I'm experiencing a

[Bug 100577] DC + TearFree display lock

https://bugs.freedesktop.org/show_bug.cgi?id=100577 --- Comment #3 from Nikola Forró --- Created attachment 131193 --> https://bugs.freedesktop.org/attachment.cgi?id=131193=edit dmesg -- You are receiving this mail because: You are the assignee for the

[Bug 100577] DC + TearFree display lock

https://bugs.freedesktop.org/show_bug.cgi?id=100577 --- Comment #2 from Nikola Forró --- Same problem here. It was definitely working fine several weeks ago. I'll try to bisect the issue if I'll find reliable reproducer. -- You are receiving this mail because: You are

[Bug 100577] DC + TearFree display lock

https://bugs.freedesktop.org/show_bug.cgi?id=100577 Michel Dänzer changed: What|Removed |Added CC|mic...@daenzer.net | --- Comment #1

[Bug 100577] DC + TearFree display lock

https://bugs.freedesktop.org/show_bug.cgi?id=100577 Bug ID: 100577 Summary: DC + TearFree display lock Product: DRI Version: DRI git Hardware: Other OS: All Status: NEW Severity: normal