All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 205169] AMDGPU driver with Navi card hangs Xorg in fullscreen only.
Date: Tue, 15 Oct 2019 20:51:35 +0000	[thread overview]
Message-ID: <bug-205169-2300-oPiPx6bBca@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205169-2300@https.bugzilla.kernel.org/>

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

--- Comment #12 from Dmitri Seletski (drjoms@gmail.com) ---
(In reply to Dmitri Seletski from comment #11)
> (In reply to Pierre-Eric Pelloux-Prayer from comment #10)
> > "git bisect" identifies this commit as the problematic one: 617089d5837a
> > ("drm/amd/display: revert wait in pipelock").
> > 
> > Reverting this commit on top of amd-staging-drm-next seems to work fine.
> 
> uname -a
> Linux (none)dimko's Desktop 5.3.0-rc3+ #3 SMP PREEMPT Mon Oct 14 20:49:02
> IST 2019 x86_64 AMD Ryzen 5 1600 Six-Core Processor AuthenticAMD GNU/Linux
> 
> 
> git checkout 617089d5837a^
> 
> Issue no longer happens
> 
> Major downgrade, but no more problem.
> Which commit can I use to solve this issue?
> 
> Bug 205169 - AMDGPU driver with Navi card hangs Xorg in fullscreen only.
> (edit) 
> https://bugzilla.kernel.org/show_bug.cgi?id=204725
> 
> Sorry that I take advantage of you here.
> I will try to find 5.3.0 commit. I am new into all this stuff.

with regards to that other bug. It's there since moment when Navi driver was
first introduced.

-- 
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:[~2019-10-15 20:51 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-12 14:24 [Bug 205169] New: AMDGPU driver with Navi card hangs Xorg in fullscreen only bugzilla-daemon
2019-10-12 14:35 ` [Bug 205169] " bugzilla-daemon
2019-10-12 14:37 ` bugzilla-daemon
2019-10-12 14:37 ` bugzilla-daemon
2019-10-12 14:47 ` bugzilla-daemon
2019-10-12 14:48 ` bugzilla-daemon
2019-10-12 16:58 ` bugzilla-daemon
2019-10-13  8:14 ` bugzilla-daemon
2019-10-13  9:43 ` bugzilla-daemon
2019-10-13  9:54 ` bugzilla-daemon
2019-10-14  9:27 ` bugzilla-daemon
2019-10-14 20:04 ` bugzilla-daemon
2019-10-15 20:51 ` bugzilla-daemon [this message]
2019-10-30  6:11 ` bugzilla-daemon
2019-11-14 21:59 ` bugzilla-daemon
2019-11-14 22:50 ` bugzilla-daemon
2019-11-14 22:51 ` bugzilla-daemon
2019-11-15  0:06 ` bugzilla-daemon
2019-11-15  1:17 ` bugzilla-daemon
2019-11-15  6:20 ` bugzilla-daemon
2019-11-15 16:03 ` bugzilla-daemon
2019-11-15 19:08 ` bugzilla-daemon
2019-11-15 19:11 ` bugzilla-daemon
2019-11-15 19:52 ` bugzilla-daemon
2019-11-25  1:37 ` bugzilla-daemon
2019-11-25  1:39 ` bugzilla-daemon
2020-02-10 16:12 ` bugzilla-daemon
2021-08-03 15:03 ` 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-205169-2300-oPiPx6bBca@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.