dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: dri-devel@lists.freedesktop.org
Subject: radeon: writeback-issues since kernel 2.6.34 on ATI FireMV 2200 PCI
Date: Mon, 02 Jan 2012 23:07:52 +0100	[thread overview]
Message-ID: <4F022AB8.2020308@gmx.de> (raw)

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

             reply	other threads:[~2012-01-02 22:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-02 22:07 Helge Deller [this message]
2012-01-03 14:27 ` radeon: writeback-issues since kernel 2.6.34 on ATI FireMV 2200 PCI Alex Deucher
2012-01-03 23:12   ` Helge Deller
2012-01-03 23:37     ` Alex Deucher
2012-01-04 19:33       ` Helge Deller

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=4F022AB8.2020308@gmx.de \
    --to=deller@gmx.de \
    --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