On Sun, Jan 23, 2005 at 06:47:09PM +0100, Jan Gukelberger wrote: > On Thu, 2005-01-20 at 21:31 +0200, Ville Syrj�l� wrote: > > > > It looks like some other interrupt source besides vsync got enabled on the > > card, or maybe some other device on the same interrupt went nuts and since > > matroxfb doesn't handle the interrupts the kernel disabled it. > > Well, according to lspci there is only a USB controller on the same IRQ > as the Matrox. I can't really imagine that the USB controller goes crazy > exactly at the moment when the DFB app is started while it runs without > problems for days as long the DFB app isn't started. (Admitted, I > couldn't imagine this whole problem before I heard about it. ;) > > Is there a chance the mga module from your Mesa-embedded-2-branch is > involved into this?
I'm pretty sure I disabled the irq code. > Btw, what does this message indicate: > "[drm:mga_dma_init] *ERROR* mga_dma_init called without lock held" The "X-server" (ie. the code in src/drv/mga/server) should grap the drm lock before calling the DMA init ioctl(). I think it does in fact call some lock grabbing function but apparently it doesn't work correctly. I've never seen any ill effects from this though. -- Ville Syrj�l� [EMAIL PROTECTED] http://www.sci.fi/~syrjala/
