From mboxrd@z Thu Jan 1 00:00:00 1970 From: Helge Deller Subject: radeon: writeback-issues since kernel 2.6.34 on ATI FireMV 2200 PCI Date: Mon, 02 Jan 2012 23:07:52 +0100 Message-ID: <4F022AB8.2020308@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by gabe.freedesktop.org (Postfix) with SMTP id 69CD69E7FD for ; Mon, 2 Jan 2012 14:07:54 -0800 (PST) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org I'm facing the problem with the radeon drm driver, that I now manually need to set the kernel module parameter radeon.no_wb to 1 at bootup, else X just hangs in average up to 8 seconds per minute without any real activity (X or the video driver just seems to wait for something..). Fedora 13 (kernel 2.6.34.9-69.fc13.x86_64) worked without problems, while all following Fedora distributions including F16 have this problem. I'm using a dual-DVI ATI RV280 [FireMV 2200 PCI]. I did compared the sources of those kernels and the only obvious change to me is in radeon_ring.c: radeon_ring_free_size() where those lines were added at the top of the function: if (rdev->wb.enabled) rdev->cp.rptr = le32_to_cpu(rdev->wb.wb[RADEON_WB_CP_RPTR_OFFSET/4]); Given the problems I'm seeing (X-Windows hangs for a few seconds every time) this fits with the idea, that the driver is waiting for a free slot but can't find any (maybe due to wrong values returned by not-working WB?). I'm wondering, if "rdev->wb.enabled" is correct in this place and if "dev_priv->writeback_works" shouldn't be used instead here? Helge