http://bugzilla.kernel.org/show_bug.cgi?id=10374 ------- Comment #13 from anonymous@xxxxxxxxxxxxxxxxxxxx 2008-04-02 08:50 ------- Reply-To: James.Bottomley@xxxxxxxxxxxxxxxxxxxxx On Wed, 2008-04-02 at 16:09 +0200, Jos van der Ende wrote: > Finally, bisecting is done. :-) Thanks for doing this ... we'd never have found it by looking at the driver code ... > Well, it took more reboots than a typical Windows XP installation (and > thank the heavens for my Sparc64 cross compiler on my Core 2 Duo), but > this seems to be the culprit: > > 5a606b72a4309a656cd1a19ad137dc5557c4b8ea is first bad commit 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). 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. James -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. -- 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
