From: "Ortwin Glück" <odi@odi.ch>
To: "Christian König" <christian.koenig@amd.com>,
linux-kernel@vger.kernel.org
Subject: Re: [bisected] drm/radeon: fences regression
Date: Sun, 23 Mar 2014 11:05:46 +0100 [thread overview]
Message-ID: <532EB1FA.20009@odi.ch> (raw)
In-Reply-To: <532DC200.7070409@amd.com>
On 03/22/2014 06:01 PM, Christian König wrote:
> Hi Ortwin,
>
> unfortunately the iMacs are notorious problematic and it's likely that something
> didn't worked before and you never noticed it because the kernel didn't
> complained. Have you ever tried to use UVD on that system?
3.12 says:
[ 7.719140] [drm] UVD initialized successfully.
Video playback was never a problem. I can use mplayer with the vdpau backend, or
VLC with the VA-API backend to play H.264 videos with no problem.
I don't know exactly if that uses UVD. No idea how to verify.
> On the other hand the failed UVD init shouldn't affect the rest of the system
> (3D should work fine), so there is really something odd here.
My guess is, the UVD init failure is not the cause, but the result of fences
code or reset detection not working properly any more. The text output (console
fb) is still fine. But when it starts Xorg the login screen is mostly black with
some colored squares where the widgets of the login screen are, and a properly
rendered and working mouse cursor sprite. Also there are delays when starting up
Xorg during which the screen goes black - I think it's waiting for fences.
When I login (KDE with compositing) the screen goes black and the monitor makes
a sound like not properly sync'ing. Then it looks like the kernel hangs.
> Please open up a bug report on
> https://bugs.freedesktop.org/enter_bug.cgi?product=DRI component DRM/Radeon and
> attach at least the full dmesg output of 3.13 as well as 3.12.
https://bugs.freedesktop.org/show_bug.cgi?id=76501
prev parent reply other threads:[~2014-03-23 10:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-22 15:16 [bisected] drm/radeon: fences regression Ortwin Glück
2014-03-22 17:01 ` Christian König
2014-03-23 10:05 ` Ortwin Glück [this message]
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=532EB1FA.20009@odi.ch \
--to=odi@odi.ch \
--cc=christian.koenig@amd.com \
--cc=linux-kernel@vger.kernel.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.