All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105308] X log ballooning in size with "drmmode_wait_vblank failed for scanout update" and "get vblank counter failed"
Date: Sun, 29 Jul 2018 18:49:16 +0000	[thread overview]
Message-ID: <bug-105308-502-Gfkt3OCvPP@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105308-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 914 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=105308

--- Comment #14 from Mariusz Mazur <mariusz.g.mazur@gmail.com> ---
So, I'm not 100% sure yet, I need time to rebuild 4.14.28 with Michel's patch
and run it for a bit, but at this point I'm about 90% certain that a patch in
4.14.29 introduces a regression, as described in bug 106529. And from reading
the changelog and looking at the code, it does seem to me that this patch is
the most likely culprit.

Short version of what's wrong: on a multi-monitor setup, if the primary display
is on DP and this code toggles it off/on, the window manager doesn't take it
well and you end up with windows all over the place. 

(I don't know if this is the same codepath as is used with amdgpu.dc=1 on more
recent kernels, though I do now the same bug occurs on 4.16+ with dc=1.)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2062 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-07-29 18:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01 11:25 [Bug 105308] X log ballooning in size with "drmmode_wait_vblank failed for scanout update" and "get vblank counter failed" bugzilla-daemon
2018-03-01 11:26 ` bugzilla-daemon
2018-03-01 12:03 ` bugzilla-daemon
2018-03-01 12:32 ` bugzilla-daemon
2018-03-01 15:57 ` bugzilla-daemon
2018-03-01 16:10 ` bugzilla-daemon
2018-03-01 16:18 ` bugzilla-daemon
2018-03-01 16:25 ` bugzilla-daemon
2018-03-04 12:30 ` bugzilla-daemon
2018-03-04 12:31 ` bugzilla-daemon
2018-03-04 12:32 ` bugzilla-daemon
2018-03-04 12:36 ` bugzilla-daemon
2018-03-04 12:40 ` bugzilla-daemon
2018-03-08 18:24 ` bugzilla-daemon
2018-03-09 17:29 ` bugzilla-daemon
2018-07-29 18:49 ` bugzilla-daemon [this message]
2018-07-30  8:25 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-105308-502-Gfkt3OCvPP@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.