All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199357] amdgpu: hang a few seconds after logging in, most likely due to regression
Date: Wed, 11 Apr 2018 20:36:02 +0000	[thread overview]
Message-ID: <bug-199357-2300-BHg7oeTy9L@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199357-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=199357

--- Comment #5 from Harry Wentland (harry.wentland@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 blinking/flickering display if redshift/nightlight is on. 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 implementation.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-04-11 20:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-11 12:26 [Bug 199357] New: amdgpu: hang a few seconds after logging in, most likely due to regression bugzilla-daemon
2018-04-11 12:27 ` [Bug 199357] " bugzilla-daemon
2018-04-11 13:37 ` bugzilla-daemon
2018-04-11 17:37 ` bugzilla-daemon
2018-04-11 18:35 ` bugzilla-daemon
2018-04-11 20:36 ` bugzilla-daemon [this message]
2018-04-12  8:06 ` bugzilla-daemon
2018-04-12 11:41 ` bugzilla-daemon
2018-04-12 11:42 ` bugzilla-daemon
2018-04-13 10:16 ` bugzilla-daemon
2018-04-17  7:03 ` bugzilla-daemon
2018-04-17 14:59 ` 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-199357-2300-BHg7oeTy9L@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.