On Thursday 27 April 2006 04:00, Jeff Garzik wrote: > [EMAIL PROTECTED] wrote: > > From: Bjorn Helgaas <[EMAIL PROTECTED]> > > > > Apparently the Intel PRO/100 device enables interrupts on reset. Unless > > firmware explicitly disables PRO/100 interrupts, we can get a flood of > > interrupts when a driver attaches to an unrelated device that happens to > > share the PRO/100 IRQ. > > > > This should resolve this "irq 11: nobody cared" bug report: > > http://bugzilla.kernel.org/show_bug.cgi?id=5918 > > > > Signed-off-by: Bjorn Helgaas <[EMAIL PROTECTED]> > > Cc: Jesse Brandeburg <[EMAIL PROTECTED]> > > Cc: Jeff Kirsher <[EMAIL PROTECTED]> > > Cc: John Ronciak <[EMAIL PROTECTED]> > > Cc: <[EMAIL PROTECTED]> > > Cc: <[EMAIL PROTECTED]> > > Signed-off-by: Andrew Morton <[EMAIL PROTECTED]> > > I'm really worried that we are burdening the kernel for a very very rare > condition. Do we want to apply this for one stupid firmware? > > Can't early userspace just run setpci to fix this one?
I don't think so, because the problem occurs as soon as any driver enables IRQ 11. I agree that it's rare, but it's a real pain to debug it and identify it when it occurs. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
