On Sun, Mar 31, 2013 at 9:55 PM, Jiri Kosina <jkosina@xxxxxxx> wrote: > On Thu, 21 Mar 2013, Daniel Vetter wrote: > >> Indeed, this is pretty useful and allowed me to quickly reproduce that >> phantom irq on my gm45. Thanks to module reloading we can even reset the >> kernel's irq disabling logic and so test different tricks quickly without >> rebooting. Really useful. > > Daniel, > > out of curiosity, have you been able to make some sense of the phantom > legacy IRQs on GM45 systems, or are we just staying with my original > bandaid (disabling GMBUS IRQs), declaring GM45 broken in this respect? I've played around with dummy-irq on my own gm45 and afaict every gmbus interrupt generates both an msi and a legacy pci interrupt when msi is enabled. Everything else (= other interrupt sources) seems to work as expected, and disabling msi also papers over the issue. There's also scary comments in our gm45 irq handler that we need msi to paper over some other races. So I've decided that I don't want to dwell any longer in this particular dungeon and that your bandaid (of just disabling this mess) is the real fix. Thanks, Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
