From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 200869] New: UVD cause amdgpu crash on CIK: [amdgpu]] UVD not responding, trying to reset the VCPU
Date: Mon, 20 Aug 2018 18:47:08 +0000 [thread overview]
Message-ID: <bug-200869-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=200869
Bug ID: 200869
Summary: UVD cause amdgpu crash on CIK: [amdgpu]] UVD not
responding, trying to reset the VCPU
Product: Drivers
Version: 2.5
Kernel Version: 4.17.17
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: janpieter.sollie@dommel.be
Regression: No
Created attachment 277985
--> https://bugzilla.kernel.org/attachment.cgi?id=277985&action=edit
attachments from the firepro machine
no VDPAU or VAAPI is possible with my firepro w5100 card, using a bonaire chip.
The module needs to be loaded 3 times before the card is initialized
successfully. 3 times is not a random number: it's every time like that:
- First time, the UVD is failing,
- Second time, the SDMA is failing
- Third time, the GFX ring buffer test fails, but the GPU works
when using HW acceleration, the GPU crashes again, and the process turns to
zombie
View kernel log for more details
Attached:
- dmesg log
- Xorg log
- ps aux
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-08-20 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 18:47 bugzilla-daemon [this message]
2018-08-21 6:18 ` [Bug 200869] UVD cause amdgpu crash on CIK: [amdgpu]] UVD not responding, trying to reset the VCPU bugzilla-daemon
2018-08-21 18:34 ` 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-200869-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.