DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=from:to:subject:date:user-agent:cc:references:in-reply-to
         :mime-version:content-disposition:message-id:content-type
         :content-transfer-encoding;
        b=nFaFaywDVwEA2tEQMqnMm6/fnwJZksx6/AenRC9RMT9uLxhtLsqXmJTakiPm9cxKqe
         Y0CJfuCBEJc8ilJPJ+qdyDu1aOGcT/JaqlLGa4epp/syvz1rH6oxqguvJkZ86ckVFpp8
         +wrR1YWYQt5EBKZqutPjEknd0mArhQTV0Az70=
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: "Dave Airlie" <airlied@gmail.com>
Subject: Re: vanilla kernels hang randomly under Fedora 10 on system with Radeon card
Date: Thu, 4 Dec 2008 01:07:36 +0100
User-Agent: KMail/1.10.3 (Linux/2.6.28-rc6-next-20081128; KDE/4.1.3; i686; ; )
Cc: linux-kernel@vger.kernel.org, Benny Amorsen <benny+usenet@amorsen.dk>
References: <200812012342.32575.bzolnier@gmail.com> <21d7e9970812012118r7196a507me0a25fe967f60ff4@mail.gmail.com> <200812031510.52685.bzolnier@gmail.com>
In-Reply-To: <200812031510.52685.bzolnier@gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200812040107.36616.bzolnier@gmail.com>
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 5059
Lines: 95

On Wednesday 03 December 2008, Bartlomiej Zolnierkiewicz wrote:
> On Tuesday 02 December 2008, Dave Airlie wrote:
> > On Tue, Dec 2, 2008 at 8:42 AM, Bartlomiej Zolnierkiewicz
> > <bzolnier@gmail.com> wrote:
> > >
> > > Hi,
> > >
> > > After Fedora 9 -> Fedora 10 upgrade vanilla kernels which previously
> > > worked fine (next-20081128 and next-20081121) started to hang randomly
> > > on my Pentium M / 855PM / RV350 laptop.  Since (surprisingly) stock
> > > Fedora kernel (2.6.27.5-117.fc10.i686) was not affected I got the idea
> > > that either userspace changes uncovered some kernel regression or some
> > > Fedora specific patch must be fixing the issue.  Unfortunately vanilla
> > > 2.6.27 also freezed so after the usual pain caused by hitting bunch of
> > > unrelated problems [1] it turned out that drm-modesetting-radeon.patch
> > > is the magic patch and CONFIG_DRM_RADEON_KMS is the magic change.  With
> > > the patch and enabling the option next-20081128 works stable again...
> > >
> > > Since the following error gets logged by kernel:
> > >
> > > [drm:drm_buffer_object_validate] *ERROR* Failed moving buffer. cef578c0 1444 4000027 10000a0
> > > [drm:drm_buffer_object_validate] *ERROR* Out of aperture space or DRM memory quota.
> > >
> > > and it also seems that system is more responsive now (it was kind of
> > > sluggish previously) my draft theory is that F9 -> F10 triggered some
> > > AGP memory management bug and CONFIG_DRM_RADEON_KMS happens to fix it
> > > but I'll leave figuring this up to the more knowledgeable people... ;)
> > 
> > Well KMS is a purely Fedora thing, and enabling it completely avoids
> > the old driver codepaths so
> > while it might fix it, its more by accident than design.
> > 
> > I'm trying to track down the rv3xx hangs with hpa at the moment as he
> > sees them also, something in
> >  the 2.6.26->2.6.27 timeframe. I'm hoping running the 2.6.26 drm on
> > the 2.6.27 will help narrow it down.
> > 
> > Bisecting 2.6.26->2.6.27 might also help.
> 
> It could be a different issue.  I tried 2.6.26, 2.6.25 and 2.6.24
> and they all hang (they all worked fine with Fedora 9)...
> 
> I will try some older kernels but I start thinking that the xorg's ati
> driver update is the main cause (xorg-x11-drv-ati-6.8.0-19.fc9.i386.rpm
> -> xorg-x11-drv-ati-6.9.0-54.fc10.i386.rpm).

I just went straight to trying downgrading the driver and the older driver
indeed works fine.  Then I tried to narrow down the problem and the lucky
winner this time is the cute (== undocumented and unsigned-off) patch
called radeon-6.9.0-remove-limit-heuristics.patch.  The newer driver with
only this patch reverted fixes hangs for vanilla kernels and drm errors
for Fedora kernel.  Also performance problems that I've noticed in the
meantime (slower playback of 720p videos, sluggish window scrolling in
kmail) are completely gone.  That being said I'm not entirely sure whether
the patch introduced the bug or it was only the trigger for it...

FWIW I've noticed that the patch seems to change the allocation+layout of
memory used by the driver:

@@ -524,13 +521,13 @@
 (II) RADEON(0): Depth moves disabled by default
 (==) RADEON(0): Not using accelerated EXA DownloadFromScreen hook
 (II) RADEON(0): Allocating from a screen of 65536 kb
-(II) RADEON(0): Will use 32 kb for hardware cursor 0 at offset 0x00bb8000
-(II) RADEON(0): Will use 32 kb for hardware cursor 1 at offset 0x00bbc000
-(II) RADEON(0): Will use 12000 kb for front buffer at offset 0x00000000
-(II) RADEON(0): Will use 12000 kb for back buffer at offset 0x00bc0000
-(II) RADEON(0): Will use 12000 kb for depth buffer at offset 0x01778000
-(II) RADEON(0): Will use 14720 kb for textures at offset 0x02330000
-(II) RADEON(0): Will use 14784 kb for X Server offscreen at offset 0x03190000
+(II) RADEON(0): Will use 32 kb for hardware cursor 0 at offset 0x011e0000
+(II) RADEON(0): Will use 32 kb for hardware cursor 1 at offset 0x011e4000
+(II) RADEON(0): Will use 18304 kb for front buffer at offset 0x00000000
+(II) RADEON(0): Will use 18304 kb for back buffer at offset 0x011e8000
+(II) RADEON(0): Will use 18304 kb for depth buffer at offset 0x023c8000
+(II) RADEON(0): Will use 5248 kb for textures at offset 0x035a8000
+(II) RADEON(0): Will use 5344 kb for X Server offscreen at offset 0x03ac8000
 drmOpenDevice: node name is /dev/dri/card0
 drmOpenDevice: open result is 11, (OK)
 drmOpenDevice: node name is /dev/dri/card0

full Xorg logs at kernel.org/pub/linux/kernel/people/bart/f9_to_f10_grind/

Thanks,
Bart

PS Since I was busy with debugging the problem I haven't noticed that you
have released the new driver package (xorg-x11-drv-ati-6.9.0-59.fc10),
however since it still contains the patch in question I don't think that
it would help (anyway I'll test it tomorrow, I'm too tired now)...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/