Re: [Dri-devel] i810 sharing interrupts race condition..

2003-03-24 Thread Keith Whitwell
Dave Airlie wrote: I've just had the misfortune of having my NFSROOT system (lots of network interrupts), have its card sharing interrupts with the i810 graphics.. once I run anything 3d the kernel oops.. The attached patch contains the quick fix which is to check in thr irq handler if

Re: [Dri-devel] i810 sharing interrupts race condition..

2003-03-24 Thread Leif Delgass
On Mon, 24 Mar 2003, Keith Whitwell wrote: Dave Airlie wrote: I've just had the misfortune of having my NFSROOT system (lots of network interrupts), have its card sharing interrupts with the i810 graphics.. once I run anything 3d the kernel oops.. The attached patch contains the quick

Re: [Dri-devel] i810 sharing interrupts race condition..

2003-03-24 Thread Leif Delgass
On Mon, 24 Mar 2003, Keith Whitwell wrote: Leif Delgass wrote: On Mon, 24 Mar 2003, Keith Whitwell wrote: Dave Airlie wrote: I've just had the misfortune of having my NFSROOT system (lots of network interrupts), have its card sharing interrupts with the i810 graphics.. once I run

Re: [Dri-devel] i810 sharing interrupts race condition..

2003-03-24 Thread Keith Whitwell
It looks fine to me, though I can't test it myself. Even if it doesn't completely fix the problem, I think it's the 'Right Thing' to do. I've committed the i810/i830_dri.c fix to the DRI trunk (I also added the drmCtlUninstHandler symbol to the referenced symbol list in i810_driver.c). If

[Dri-devel] i810 sharing interrupts race condition..

2003-03-23 Thread Dave Airlie
I've just had the misfortune of having my NFSROOT system (lots of network interrupts), have its card sharing interrupts with the i810 graphics.. once I run anything 3d the kernel oops.. The attached patch contains the quick fix which is to check in thr irq handler if dev-dev_private is NULL or

Re: [Dri-devel] i810 sharing interrupts race condition..

2003-03-23 Thread Dave Airlie
I've attached a second patch to xc/xc/programs/Xserver/hw/xfree86/drivers/i810/i810_dri.c that may also fix the problem but which I haven't tested, yeah you can ignore the patch, but the idea is correct I think, the patch is bogus using variables from places that dont exist :-)... of course