On Sat, May 13, 2000 at 07:41:01PM +0100, Kenn Humborg wrote:
> Scanning of ID 0 is now silent, and that makes things a bit
> different when the card interrupts after the scan of ID 1. From
> my reading of this, it looks like either:
>
> o The card is interrupting, but doesn't actually have any results
> for us. AscISR() doesn't find any work to do, so asc_isr_callback
> never gets called.
>
> o Something else is interrupting on IRQ 11. I don't think this is
> likely because I can see all my cards generating interrupts on
> other IRQs (via /proc/interrupts).
>
> I'm going to try printk()s in AscISR and friends and see if I can
> figure out what condition is causing asc_isr_callback() not to be
> called.
I've found out that AscISR() is calling AscIsrChipHalted().
AscIsrChipHalted() gets a halt code of 0 from the card, which
isn't something it's able to deal with. I've tried adding
a catch-all else clause to the end of AscIsrChipHalted() to
clear the halt condition and return both 0 and ERR. Neither
makes any difference.
I guess it is now definitely an Advansys issue, rather than a
generic Linux SCSI one. So over to [EMAIL PROTECTED]!
Later,
Kenn
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
