From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91704] Tonga startx fails since mesa/drm 56d8dd6 amdgpu: make vamgr per device v2
Date: Thu, 20 Aug 2015 18:19:03 +0000 [thread overview]
Message-ID: <bug-91704-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1186 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91704
Bug ID: 91704
Summary: Tonga startx fails since mesa/drm 56d8dd6 amdgpu: make
vamgr per device v2
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: adf.lists@gmail.com
Created attachment 117820
--> https://bugs.freedesktop.org/attachment.cgi?id=117820&action=edit
xorg log
With latest libdrm git I can't startx due to a segfault shown in attached xorg
log.
dmesg logs several -
amdgpu 0000:01:00.0: bo ffff8800bd34b800 va 0x0000100000-0x0000100400 conflict
with 0x0000100000-0x0000100400
This happens with mesa/drm on commit
56d8dd6 amdgpu: make vamgr per device v2
On the commit before that -
ffa305d amdgpu: add flag to support 32bit VA address v4
I can startx without error but performance is broken eg. scrolling in xterm
takes about a second to refresh the screen.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2529 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-20 18:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 18:19 bugzilla-daemon [this message]
2015-08-20 20:50 ` [Bug 91704] Tonga startx fails since mesa/drm 56d8dd6 amdgpu: make vamgr per device v2 bugzilla-daemon
2015-08-20 21:20 ` bugzilla-daemon
2015-08-20 22:06 ` bugzilla-daemon
2015-08-21 3:56 ` bugzilla-daemon
2015-08-21 9:58 ` bugzilla-daemon
2015-08-21 11:54 ` bugzilla-daemon
2015-08-22 13:29 ` bugzilla-daemon
2015-08-22 13:31 ` bugzilla-daemon
2015-08-22 16:20 ` bugzilla-daemon
2015-08-22 19:36 ` bugzilla-daemon
2015-08-22 19:52 ` bugzilla-daemon
2015-08-23 9:17 ` bugzilla-daemon
2015-08-23 9:44 ` bugzilla-daemon
2015-08-23 10:55 ` bugzilla-daemon
2015-08-23 11:56 ` bugzilla-daemon
2015-08-23 14:07 ` bugzilla-daemon
2015-08-23 14:13 ` bugzilla-daemon
2015-08-24 4:00 ` bugzilla-daemon
2015-08-24 7:53 ` bugzilla-daemon
2015-08-24 11:25 ` bugzilla-daemon
2015-08-24 11:27 ` 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-91704-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 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.