From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 153121] UVD not responding, trying to reset the VCPU, ATI Mobility Radeon HD 5650
Date: Mon, 15 Aug 2016 10:56:45 +0000 [thread overview]
Message-ID: <bug-153121-2300-7VmxzIrhUh@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-153121-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=153121
Felix Schwarz <felix.schwarz@oss.schwarz.eu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |felix.schwarz@oss.schwarz.e
| |u
--- Comment #19 from Felix Schwarz <felix.schwarz@oss.schwarz.eu> ---
(In reply to Christian König from comment #18)
> If I remember correctly the message is perfectly normal for Caicos systems,
> cause those shouldn't have an UVD block.
I think at least some Caicos systems have an UVD block:
$ lspci | grep AMD
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI Audio
[Radeon HD 6400 Series]
$ lspci -n
01:00.0 0300: 1002:6779
01:00.1 0403: 1002:aa98
This is a Radeon HD 6450 (which is Caicos AFAIK).
$ dmesg | grep -i uvd
[ 2.184334] [drm] UVD initialized successfully.
--
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 prev parent reply other threads:[~2016-08-15 10:56 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 8:52 [Bug 153121] New: UVD not responding, trying to reset the VCPU, ATI Mobility Radeon HD 5650 bugzilla-daemon
2016-08-15 8:54 ` [Bug 153121] " bugzilla-daemon
2016-08-15 8:55 ` bugzilla-daemon
2016-08-15 8:55 ` bugzilla-daemon
2016-08-15 8:56 ` bugzilla-daemon
2016-08-15 8:57 ` bugzilla-daemon
2016-08-15 8:57 ` bugzilla-daemon
2016-08-15 8:58 ` bugzilla-daemon
2016-08-15 8:59 ` bugzilla-daemon
2016-08-15 9:01 ` bugzilla-daemon
2016-08-15 9:06 ` bugzilla-daemon
2016-08-15 9:07 ` bugzilla-daemon
2016-08-15 9:07 ` bugzilla-daemon
2016-08-15 9:22 ` bugzilla-daemon
2016-08-15 9:38 ` bugzilla-daemon
2016-08-15 9:41 ` bugzilla-daemon
2016-08-15 9:51 ` bugzilla-daemon
2016-08-15 9:54 ` bugzilla-daemon
2016-08-15 10:03 ` bugzilla-daemon
2016-08-15 10:56 ` bugzilla-daemon [this message]
2016-08-15 11:18 ` bugzilla-daemon
2016-08-16 14:01 ` bugzilla-daemon
2016-08-16 14:02 ` bugzilla-daemon
2016-08-16 14:03 ` bugzilla-daemon
2016-08-16 14:04 ` bugzilla-daemon
2016-08-16 14:05 ` bugzilla-daemon
2016-08-16 14:17 ` bugzilla-daemon
2016-08-16 14:18 ` bugzilla-daemon
2016-08-18 5:13 ` bugzilla-daemon
2016-08-18 6:18 ` bugzilla-daemon
2016-08-18 6:28 ` bugzilla-daemon
2016-08-18 6:28 ` bugzilla-daemon
2016-08-22 11:52 ` bugzilla-daemon
2016-08-22 11:54 ` bugzilla-daemon
2016-08-29 9:32 ` bugzilla-daemon
2016-09-02 16:22 ` bugzilla-daemon
2016-09-02 16:22 ` bugzilla-daemon
2016-09-02 16:26 ` bugzilla-daemon
2016-09-14 13:12 ` bugzilla-daemon
2016-09-14 13:20 ` bugzilla-daemon
2016-09-18 10:30 ` 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-153121-2300-7VmxzIrhUh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).