Thomas Bogendoerfer <[EMAIL PROTECTED]> : [...] > for normal interrupt delivery it doesn't matter, because there shouldn't > be any more interrupts coming in at that point. But netconsole uses > pcnet32_interrupt for polling the chip. So if during service of a > a real interrupt a polled pcnet32_interrupt call is done, the machine > will deadlock.
Even if the driver-agnostic part of the irq processing can be interrupted locally, the irq handlers are run sequentially on a given cpu. It does not leave a lot of room for a deadlock-prone printk(). It _can_ happen but I'd prefer to pinpoint a specific candidate path where it would have happened. -- Ueimor - 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
