From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 85207] New: agd5f drm-next-3.19-wip + Unreal Elemental sometimes = list_add corruption/hung task
Date: Sun, 19 Oct 2014 21:07:33 +0000 [thread overview]
Message-ID: <bug-85207-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1527 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=85207
Bug ID: 85207
Summary: agd5f drm-next-3.19-wip + Unreal Elemental sometimes =
list_add corruption/hung task
Product: DRI
Version: XOrg CVS
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: adf.lists@gmail.com
Created attachment 108075
--> https://bugs.freedesktop.org/attachment.cgi?id=108075&action=edit
dmesg when Unreal Elemental hangs on start
R9270X Sometime running unreal elemental demo it hangs at startup with errors
in dmesg attached.
This doesn't always happen.
Mesa is currently on winsys/radeon: Use a single buffer cache manager again,
previously produced with slightly older.
Haven't seen on drm-next-3.18-wip (but really need to test more with current
mesa)
Possibly unrelated, but new for drm-next-3.19-wip I get below when running
Unigine Valley - it runs OK.
Oct 17 11:15:35 ph4 kernel: radeon 0000:01:00.0: GPU fault detected: 146
0x0af03504
Oct 17 11:15:35 ph4 kernel: radeon 0000:01:00.0:
VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00010E57
Oct 17 11:15:35 ph4 kernel: radeon 0000:01:00.0:
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x10035004
Oct 17 11:15:35 ph4 kernel: VM fault (0x04, vmid 8) at page 69207, read from
VGT (53)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2948 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:[~2014-10-19 21:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 21:07 bugzilla-daemon [this message]
2014-10-19 21:14 ` [Bug 85207] agd5f drm-next-3.19-wip + Unreal Elemental sometimes = list_add corruption/hung task bugzilla-daemon
2014-10-20 9:21 ` bugzilla-daemon
2014-10-20 17:13 ` bugzilla-daemon
2014-10-21 9:54 ` bugzilla-daemon
2014-10-21 13:11 ` bugzilla-daemon
2014-10-22 13:45 ` bugzilla-daemon
2014-10-23 9:03 ` bugzilla-daemon
2014-10-23 22:17 ` bugzilla-daemon
2014-10-30 9:55 ` bugzilla-daemon
2014-12-30 9:54 ` bugzilla-daemon
2015-01-08 2:00 ` bugzilla-daemon
2015-01-08 15:48 ` bugzilla-daemon
2015-01-08 15:48 ` bugzilla-daemon
2015-07-30 11:49 ` bugzilla-daemon
2015-08-02 11:40 ` bugzilla-daemon
2015-08-02 11:41 ` 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-85207-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.