Re: [Xen-devel] [GIT PULL] devel/pat + devel/kms.fixes-0.5 on RV730 PRO [Radeon HD 4650] Stack trace

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

On Wed, Aug 18, 2010 at 05:48:47AM -0700, Boris Derzhavets wrote:
> Just surfing Net for 2-3 hr concerning "dracut" on Fedora 13.
> Several "warnings"  at the end of dmesg log. Seems like reaction
> on some system events scheduled to run on regular basis, but not
> user's activity.

I am pretty sure you are hitting this bug:

https://bugzilla.redhat.com/show_bug.cgi?id=558190
https://bugzilla.redhat.com/show_bug.cgi?id=537981
 that got fixed in v2.6.33 with this patch:

commit 4c7886791264f03428d5424befb1b96f08fc90f4
Author: Jerome Glisse <jglisse@xxxxxxxxxx>
Date:   Fri Nov 20 14:29:23 2009 +0100

    drm/radeon/kms: Rework radeon object handling
    
    The locking & protection of radeon object was somewhat messy.
    This patch completely rework it to now use ttm reserve as a
    protection for the radeon object structure member. It also
    shrink down the various radeon object structure by removing
    field which were redondant with the ttm information. Last it
    converts few simple functions to inline which should with
    performances.
    
    airlied: rebase on top of r600 and other changes.

and backporting this back to xen/stable-2.32.x.. is not something
I am going to do.

Looking in in kernel-2.6.32.8-58.fc12.x86_64 the patch that fixed this was
drm-upgrayedd.patch  which is a mega-update of DRM to 2.6.33.

It even has nouveau bits in it.

So, you will have to wait till 2.6.36 rebase is complete. Or
you can try back-porting those patches. Or wait a couple of days
and wait for me to rebase my devel/next.drm, which has DRM from
2.6.34.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel