Hi, On Saturday 06 November 2004 01:04, Ben Skeggs wrote: > Hello, > > I've been trying to get the experimental r300.sf.net driver to work on > my machine. I've compiled and installed it ok, but everytime I start > the X server with DRI enabled, the top of the screen is corrupted, which > I'm assuming is the xterms that are supposed to be showing. However, > the mouse pointer is draw correctly, and I'm still able to move it. > > I've posted what I captured in syslog, and my xorg log below. > > The card is a Powercolor Radeon 9600 256MB (RV350 AP), I tested with > vanilla 2.6.9 with reiser4 patched in.
Thanks for testing on AFAIK untested hardware. (from just before the SysRq message) > Nov 6 06:05:44 [kernel] [drm:drm_ioctl] pid=9718, cmd=0x4008642a, > nr=0x2a, dev 0xe200, auth=1 > Nov 6 06:05:44 [kernel] [drm:drm_ioctl] pid=9718, cmd=0xc010644d, > nr=0x4d, dev 0xe200, auth=1 > Nov 6 06:05:44 [kernel] [drm:drm_ioctl] pid=9718, cmd=0xc0286429, > nr=0x29, dev 0xe200, auth=1 > Nov 6 06:05:44 [kernel] [drm:drm_ioctl] pid=9718, cmd=0xc010644d, > nr=0x4d, dev 0xe200, auth=1 > Nov 6 06:05:44 [kernel] [drm:drm_ioctl] pid=9718, cmd=0xc0286429, > nr=0x29, dev 0xe200, auth=1 > Nov 6 06:05:44 [kernel] [drm:drm_ioctl] pid=9718, cmd=0xc010644d, > nr=0x4d, dev 0xe200, auth=1 This is a lock, followed by indirect and freelist_get calls. There are two things that concern me: 1. There's a lot less debug output than I get. Also, it's interesting that radeon_cp_dispatch_indirect itself appears to hang. That's not completely impossible, but I've never seen it happen. (or maybe it just seems that way in your syslog because we don't get full debug messages). 2. There are no calls to cp_idle between indirect buffer emits. This indicates that you are running an old DDX, and not X.Org CVS + patch from r300_driver CVS. The latest patch contains a workaround for a known lockup problem. Said problem shouldn't cause a lockup unless a 3D client is running, but you never know... Some more things: 3. A lockup on X server startup is usually a sign for bad microcode, though you do have the correct log message in syslog. 4. Your card has 256MB memory while I can only test with 128MB. Has anybody successfully experimented in any way (r300_demo or r300_driver) with 256MB cards? I remember seeing that the large memory versions had some paging hacks, and there might be related differences that cause the lockup here. cu, Nicolai
pgpuYC189RfMS.pgp
Description: PGP signature
