Re: [Dri-devel] Fault in radeon DRM module

2003-09-24 Thread Eric Anholt
On Wed, 2003-09-24 at 17:43, Linus Torvalds wrote: > On Tue, 9 Sep 2003, Michel Dänzer wrote: > > > > Absolutely, otherwise it's a bug. FWIW, the DRM from DRI CVS seems to > > work the same here as the one from the linuxppc-2.5 tree shortly before > > the -test5 merge. The only recent change I see

Re: [Dri-devel] Fault in radeon DRM module

2003-09-24 Thread Linus Torvalds
On Tue, 9 Sep 2003, Michel Dänzer wrote: > > Absolutely, otherwise it's a bug. FWIW, the DRM from DRI CVS seems to > work the same here as the one from the linuxppc-2.5 tree shortly before > the -test5 merge. The only recent change I see which might cause > problems is my Radeon AGP => GART clean

Re: [Dri-devel] Fault in radeon DRM module

2003-09-09 Thread Jon Smirl
--- Michel Dänzer <[EMAIL PROTECTED]> wrote: > You need to find out where the register gets overwritten. I don't see > any code doing it, and I've never experienced this problem. Are you SMP? I have hyperthreading turned on. I'll try it again with SMP turned off. = Jon Smirl [EMAIL PROTECTED

Re: [Dri-devel] Fault in radeon DRM module

2003-09-09 Thread Keith Whitwell
Linus Torvalds wrote: On Mon, 8 Sep 2003, Jon Smirl wrote: I think I have tracked this down to the DRM drivers in the kernel not matching the ones in DRI CVS. Some of the structures in the initialization IOCTL have changed which caused one of the ring pointers to initialize to zero instead of wha

Re: [Dri-devel] Fault in radeon DRM module

2003-09-09 Thread Michel Dänzer
On Tue, 2003-09-09 at 23:30, Jon Smirl wrote: > > This line in radeon_cp is causing the problem with the ring pointers. > dev_priv->agp_vm_start = RADEON_READ( RADEON_CONFIG_APER_SIZE ); > agp_vm_start is coming out zero and I don't think it should be. Indeed, as the name suggests, it's e

Re: [Dri-devel] Fault in radeon DRM module

2003-09-09 Thread Keith Whitwell
Linus Torvalds wrote: On Tue, 9 Sep 2003, Linus Torvalds wrote: I can do a new merge [ ... ] Is the "dri.freedesktop.org" tree up-to-date? Nothing has happened on it lately, and I wonder if people are still using the old one for development? In the meantime, I could add you to the sf developer

Fwd: Re: [Dri-devel] Fault in radeon DRM module

2003-09-09 Thread Jon Smirl
--- Jon Smirl <[EMAIL PROTECTED]> wrote: > Date: Tue, 9 Sep 2003 13:33:26 -0700 (PDT) > From: Jon Smirl <[EMAIL PROTECTED]> > Subject: Re: [Dri-devel] Fault in radeon DRM module > To: Linus Torvalds <[EMAIL PROTECTED]> > > I haven't located the exact ca

Re: [Dri-devel] Fault in radeon DRM module

2003-09-09 Thread Michel Dänzer
On Wed, 2003-09-10 at 01:17, Jon Smirl wrote: > In this case I loaded the radeon kernel driver from CVS. I am running XFree > from RH9. No code from embedded is involved. This is with i875P AGP. > > I first started X and it ran without problem. > I stopped it and started it again. > I get an oops

Re: [Dri-devel] Fault in radeon DRM module

2003-09-09 Thread Michel Dänzer
On Tue, 2003-09-09 at 22:11, Linus Torvalds wrote: > On Mon, 8 Sep 2003, Jon Smirl wrote: > > > > I think I have tracked this down to the DRM drivers in the kernel not matching > > the ones in DRI CVS. Some of the structures in the initialization IOCTL have > > changed which caused one of the ring

Re: [Dri-devel] Fault in radeon DRM module

2003-09-09 Thread Jon Smirl
In this case I loaded the radeon kernel driver from CVS. I am running XFree from RH9. No code from embedded is involved. This is with i875P AGP. I first started X and it ran without problem. I stopped it and started it again. I get an oops in radeon_do_cp_start() It may be that embedded and Xfre

Re: [Dri-devel] Fault in radeon DRM module

2003-09-09 Thread Eric Anholt
On Tue, 2003-09-09 at 13:12, Linus Torvalds wrote: > On Tue, 9 Sep 2003, Linus Torvalds wrote: > > > > I can do a new merge [ ... ] > > Is the "dri.freedesktop.org" tree up-to-date? Nothing has happened on it > lately, and I wonder if people are still using the old one for > development? It is

Re: [Dri-devel] Fault in radeon DRM module

2003-09-09 Thread Linus Torvalds
On Tue, 9 Sep 2003, Linus Torvalds wrote: > > I can do a new merge [ ... ] Is the "dri.freedesktop.org" tree up-to-date? Nothing has happened on it lately, and I wonder if people are still using the old one for development? Linus

Re: [Dri-devel] Fault in radeon DRM module

2003-09-09 Thread Linus Torvalds
On Mon, 8 Sep 2003, Jon Smirl wrote: > > I think I have tracked this down to the DRM drivers in the kernel not matching > the ones in DRI CVS. Some of the structures in the initialization IOCTL have > changed which caused one of the ring pointers to initialize to zero instead of > what it needed.

Re: [Dri-devel] Fault in radeon DRM module

2003-09-09 Thread Keith Whitwell
Jon Smirl wrote: I think I have tracked this down to the DRM drivers in the kernel not matching the ones in DRI CVS. Some of the structures in the initialization IOCTL have changed which caused one of the ring pointers to initialize to zero instead of what it needed. The minor version number prob

Re: [Dri-devel] Fault in radeon DRM module

2003-09-08 Thread Jon Smirl
I think I have tracked this down to the DRM drivers in the kernel not matching the ones in DRI CVS. Some of the structures in the initialization IOCTL have changed which caused one of the ring pointers to initialize to zero instead of what it needed. The minor version number probably should have

Re: [Dri-devel] Fault in radeon DRM module

2003-09-08 Thread Linus Torvalds
On Sun, 7 Sep 2003, Jon Smirl wrote: > > I'm getting this with standalone Mesa not DRI. Can a someone more familar with > the R200 kernel DRM driver give me a clue as to what is not being set up > correctly? I die in RADEON_PURGE_CACHE() in radeon_do_cp_start(). More precisely: > Unable to handl

[Dri-devel] Fault in radeon DRM module

2003-09-07 Thread Jon Smirl
I'm getting this with standalone Mesa not DRI. Can a someone more familar with the R200 kernel DRM driver give me a clue as to what is not being set up correctly? I die in RADEON_PURGE_CACHE() in radeon_do_cp_start(). There also looks to be a bug. After the fault there is a radeon_vm_shm_close. Th