From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91522] Tonga display lock on agd5f drm-next-4.3-wip since drm/amdgpu: fix syncing to VM updates
Date: Sat, 01 Aug 2015 15:16:43 +0000 [thread overview]
Message-ID: <bug-91522-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1100 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91522
Bug ID: 91522
Summary: Tonga display lock on agd5f drm-next-4.3-wip since
drm/amdgpu: fix syncing to VM updates
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: adf.lists@gmail.com
Tried agd5f drm-next-4.3-wip without enabling anything new. agd5f mesa/drm
amdgpu.
I can startx but doing anything 3d/vdpau results in a display lock.
Nothing is logged, there is no gpu reset. SysRq works (and gets logged).
bisecting using glxgears to trigger came up with -
commit 928db3aef53b0e74e26a6815890b6162cff2f4e7
Author: Christian König <christian.koenig@amd.com>
Date: Mon Jul 27 15:40:35 2015 +0200
drm/amdgpu: fix syncing to VM updates
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2479 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:[~2015-08-01 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-01 15:16 bugzilla-daemon [this message]
2015-08-05 13:14 ` [Bug 91522] Tonga display lock on agd5f drm-next-4.3-wip since drm/amdgpu: fix syncing to VM updates bugzilla-daemon
2015-11-27 15:13 ` 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-91522-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