From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93862] [Bisected] "drm/amdgpu: fix amdgpu_bo_pin_restricted VRAM placing v2" is bad
Date: Mon, 25 Jan 2016 20:41:38 +0000 [thread overview]
Message-ID: <bug-93862-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1099 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93862
Bug ID: 93862
Summary: [Bisected] "drm/amdgpu: fix amdgpu_bo_pin_restricted
VRAM placing v2" is bad
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: ernstp@gmail.com
Updating to the latest drm-next-4.6-wip I could no longer log in to Gnome
through GDM, I just got a black screen after entering my passwd. startx +
gnome-session worked though.
However if I ran Unigine Heaven with Tessellation there, I saw I got the frames
in the wrong order sometimes. This doesn't happen otherwise.
Bisecting was easy and pointed to:
78d0e182b6c1f5336f6e8cbb197f403276dabc7f
drm/amdgpu: fix amdgpu_bo_pin_restricted VRAM placing v2
Reverting that commit on top of drm-next-4.6-wip also solved the problem.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2355 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-01-25 20:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 20:41 bugzilla-daemon [this message]
2016-01-26 1:37 ` [Bug 93862] [Bisected] "drm/amdgpu: fix amdgpu_bo_pin_restricted VRAM placing v2" is bad bugzilla-daemon
2016-01-26 3:51 ` bugzilla-daemon
2016-01-26 4:00 ` bugzilla-daemon
2016-01-26 4:02 ` bugzilla-daemon
2016-01-26 7:43 ` bugzilla-daemon
2016-01-28 1:35 ` bugzilla-daemon
2016-01-29 8:33 ` bugzilla-daemon
2016-01-29 8:45 ` 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-93862-502@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).