From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92087] [Radeon/Tonga] lockup in valley demo
Date: Wed, 23 Sep 2015 09:04:01 +0000 [thread overview]
Message-ID: <bug-92087-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1227 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92087
Bug ID: 92087
Summary: [Radeon/Tonga] lockup in valley demo
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: edward.ocallaghan@koparo.com
Hi,
Upon running the valley demo I experience I lockup after a while. I can recover
by switching to another virtual term and killing X.
dmesg shows this repeatedly with only a difference of the value after the fault
id? of 146 after the lockup:
--------------------
VM fault (0x00, vmid 0) at page 0, read from '' (0x00000000) (0)
amdgpu 0000:01:00.0: GPU fault detected: 146 0x02704004
amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000
amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
--------------------
This is with mesa 11.0.1 (8ae8feca) + kern 4.3.0-rc2 + libdrm 2.4.65
No idea how to get a card state dump with amdgpu?
Edward.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2443 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-09-23 9:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 9:04 bugzilla-daemon [this message]
2015-09-24 15:41 ` [Bug 92087] [Radeon/Tonga] lockup in valley demo bugzilla-daemon
2015-09-24 15:43 ` 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-92087-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.