From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104527] Amdgpu locks up occasionally when running 3d applications
Date: Sun, 07 Jan 2018 15:07:01 +0000 [thread overview]
Message-ID: <bug-104527-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2122 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104527
Bug ID: 104527
Summary: Amdgpu locks up occasionally when running 3d
applications
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: hramrach@gmail.com
Created attachment 136597
--> https://bugs.freedesktop.org/attachment.cgi?id=136597&action=edit
kernel messages
Linux 4.14.0 libdrm 2.4.89 mesa 17.3.1 on Debian
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Baffin [Radeon RX 460] [1002:67ef] (rev cf)
After lockup I see this message:
[150509.194713] amdgpu 0000:01:00.0: GPU fault detected: 147 0x00004802
[150509.194718] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[150509.194720] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0A048002
[150509.194722] amdgpu 0000:01:00.0: VM fault (0x02, vmid 5) at page 0, read
from 'TC0' (0x54433000) (72)
but similar message earlier did not cause lockup
[112552.659698] amdgpu 0000:01:00.0: GPU fault detected: 147 0x07f04802
[112552.659702] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x0003F8FE
[112552.659704] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0A048002
[112552.659706] amdgpu 0000:01:00.0: VM fault (0x02, vmid 5) at page 260350,
read from 'TC0' (0x54433000) (72)
Earlier versions of kernel+mesa would occasionally lock up displaying garbage
randomly at any time. I have not seen that for a while but the card still
occasionally locks up when running a 3D application. After lock up the card
keeps showing static screen of something the application rendered and movable
cursor. It *seems* to happen most often when there is some setup in progress
like loading a new scene.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3528 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-01-07 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-07 15:07 bugzilla-daemon [this message]
2018-01-07 15:55 ` [Bug 104527] Amdgpu locks up occasionally when running 3d applications bugzilla-daemon
2018-01-08 5:36 ` bugzilla-daemon
2019-11-19 8:28 ` 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-104527-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