On 05/02/01 20:55 Jeff Garzik wrote:
> [EMAIL PROTECTED] wrote:
> >
> > On Mon, 5 Feb 2001, Matthew Harrell wrote:
> >
> > > : Ouch. After applying the attached patch, do any of the assertions
> > > : trigger? (You should get a message 'Assertion failed! ...' right
before
> > > : the oops)
> > >
> > > : + assert (chan->sgtable != NULL);
> > >
> > > Yep, I get this one "chan->sgtable != NULL". I have no idea what
this means
> > > but I got it one out of the two times I tried.
> > >
> >
> > Is there any other device on the same irq?
>
> Yes, it looks like:
>
> Matthew Harrell wrote:
> > PCI: Found IRQ 10 for device 00:14.5
> > PCI: The same IRQ used for device 00:04.0
>
> The attached patch, sent to Matthew privately, apparently has fixed his
> problem. Right now it looks like an out-of-band interrupt... The
> interrupt is enabled via request_irq, and its shared so the interrupt
> handler will be called. However the channel isn't active so the SG
> table hasn't been allocated yet.
But your interrupt status register should indicate that it wasn't the
sound device that generated the interrupt...
Matthew, can you try the attached patched and report the output?
You should apply it on a clean 2.4.1 (without the patches Jeff sent you).
Try only sound playback.
Rui Sousa
(See attached file: patch)
patch
