From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andy Furniss <adf.lists@gmail.com>
Subject: Radeon Rv790 "Forbidden register 0x0030 in cs at 9"
Date: Thu, 31 Oct 2013 11:58:21 +0000
Message-ID: <527245DD.5090408@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <dri-devel-bounces@lists.freedesktop.org>
Received: from mail-we0-f173.google.com (mail-we0-f173.google.com
	[74.125.82.173])
	by gabe.freedesktop.org (Postfix) with ESMTP id 0EAC4EE6BD
	for <dri-devel@lists.freedesktop.org>;
	Thu, 31 Oct 2013 04:58:24 -0700 (PDT)
Received: by mail-we0-f173.google.com with SMTP id u57so2555488wes.18
	for <dri-devel@lists.freedesktop.org>;
	Thu, 31 Oct 2013 04:58:22 -0700 (PDT)
Received: from [192.168.0.3] (149.15.208.46.dyn.plus.net. [46.208.15.149])
	by mx.google.com with ESMTPSA id td6sm2278066wic.10.2013.10.31.04.58.21
	for <dri-devel@lists.freedesktop.org>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 31 Oct 2013 04:58:21 -0700 (PDT)
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/dri-devel>,
	<mailto:dri-devel-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/dri-devel>
List-Post: <mailto:dri-devel@lists.freedesktop.org>
List-Help: <mailto:dri-devel-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/dri-devel>,
	<mailto:dri-devel-request@lists.freedesktop.org?subject=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

Noticed this in dmesg today, it doesn't seem to break anything and it's 
not reproducable.

[ 2605.261326] Forbidden register 0x0030 in cs at 9
[ 2605.261335] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !

Seems it was triggered by mplayer using vdpau just for display, though 
grepping kern.log only found one other on Oct 22nd.

mplayer has been used far more than just twice in this period.

Running drm-fixes today and drm-next on the 22nd.