On Wed, 02 Apr 2008 10:49:19 -0500 James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx> wrote: > Reading the code for this, it seems that something fiddled with the > IRQ_DISABLED or IRQ_PENDING flags when it came time for the ->eoi() so > the gem interrupt is always held pending (because it's never ended). So Andrew's first hunch that interrupts were somehow involved is right. > Since the sym2 is on interrupts 16 and 17 and gem on 11 (and the > descriptors are separate entities in the irq_desc array) I can't really > see how sym2 would be doing this. Yeah, that has me baffled too. Still, the fact is that I can only trigger the bug by loading sym53c8xx before sungem. I have yet to find any other conditions that trigger it. Loading sungem before sym53c8xx on an affected kernel gives no trouble at all. -- Jos van der Ende <seraph@xxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
