From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 67571] BUG: unable to handle kernel paging in amd E350 hdmi init
Date: Mon, 23 Dec 2013 18:42:27 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
Received: from mail.kernel.org (mail.kernel.org [198.145.19.201])
by gabe.freedesktop.org (Postfix) with ESMTP id B0FA6F9FEF
for ;
Mon, 23 Dec 2013 10:42:29 -0800 (PST)
Received: from mail.kernel.org (localhost [127.0.0.1])
by mail.kernel.org (Postfix) with ESMTP id 124C12076B
for ;
Mon, 23 Dec 2013 18:42:29 +0000 (UTC)
Received: from bugzilla1.web.kernel.org (bugzilla1.web.kernel.org
[172.20.200.51])
by mail.kernel.org (Postfix) with ESMTP id 9094720768
for ;
Mon, 23 Dec 2013 18:42:27 +0000 (UTC)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: dri-devel-bounces@lists.freedesktop.org
Errors-To: dri-devel-bounces@lists.freedesktop.org
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
https://bugzilla.kernel.org/show_bug.cgi?id=67571
--- Comment #5 from Alex Deucher ---
(In reply to Eric Valette from comment #4)
> Thanks. Indeed it fixes the bug that carsh the kernel buy I still have this:
>
> [drm] ib test on ring 0 succeeded in 0 usecs
> [ 27.400271] [drm] ib test on ring 3 succeeded in 1 usecs
> [ 37.421526] radeon 0000:00:01.0: GPU lockup CP stall for more than
> 10001msec
> [ 37.421559] radeon 0000:00:01.0: GPU lockup (waiting for
> 0x0000000000000004 last fence id 0x0000000000000002 on ring 5)
> [ 37.421570] [drm:uvd_v1_0_ib_test] *ERROR* radeon: fence wait failed
> (-35).
> [ 37.441641] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB
> on ring 5 (-35).
Make sure you have the uvd and latest rlc ucode installed in order to use UVD.
> [ 37.441664] [drm] Found smc ucode version: 0x00010200
> [ 38.411143] [drm:dce4_afmt_write_speaker_allocation] *ERROR* Couldn't
> read Speaker Allocation Data Block: 0
This error is harmless, it's just telling you that the monitor provides invalid
speak allocation information. Audio support should still work.
> [ 42.249879] [drm] Disabling audio 0 support
Can you attach your full dmesg log? You should only see this message during
suspend, shutdown, or gpu reset. This is unrelated to patch.
>
> Does this mean I will get no audio via HDMI?
You should still get audio unless the GPU is hung and the driver is not able to
reset it.
--
You are receiving this mail because:
You are watching the assignee of the bug.