On Tue, 08 Feb 2005 00:42:29 +0100, Roland Scheidegger <[EMAIL PROTECTED]> wrote: > > Linux agpgart interface v0.100 (c) Dave Jones > > agpgart: Detected an Intel i875 Chipset. > > agpgart: Maximum main memory to use for agp memory: 198M > > agpgart: AGP aperture is 32M @ 0xe0000000 > > [drm] Initialized drm 1.0.0 20040925 > > PCI: Obtained IRQ 16 for device 0000:01:00.0 > > [drm] Initialized radeon 1.12.1 20041216 on minor 0: > > agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0. > > agpgart: Putting AGP V3 device at 0000:00:00.0 into 4x mode > > agpgart: Putting AGP V3 device at 0000:01:00.0 into 4x mode > > [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held, > > held 0 owner 00000000 c9958f6c > > [drm:drm_unlock] *ERROR* Process 6699 using kernel context 0 > > mtrr: reg: 1 has count=0 > > mtrr: reg: 1 has count=0
My guess is that xen is not setting up the shared memory between agp/drm and mesa. This is probably because agp/drm are running in the supervisor kernel and X is in the user one. Mesa set the lock in the user kernel copy, but the supervisor has a different copy of the shared memory and the lock is not set there. Arbitrary sharing memory between the user and supervisor kernel like DRM does is one of the things Xen is designed to prevent. I believe xen has a mode where you can assign hardware exclusively to a user kernel. You'll need to do that and then run apg/drm/mesa all in the same user kernel. Without that I think you need changes to xen or drm. This is just a guess based on the log, I have not tried running Xen and drm. Running agp/drm in the supervisor kernel implies that you are trying to share it between user kernels. Doing that would require the implementation of virtual AGP/DRM devices. -- Jon Smirl [EMAIL PROTECTED] ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
