On Fri, Aug 10, 2007 at 10:05:40AM +0200, Thomas Gleixner wrote: > On Thu, 2007-08-09 at 17:54 +0200, Jarek Poplawski wrote: > > I'm not sure I don't miss anything (a little in hurry now), but this > > warning's aim was purely diagnostical and nothing wrong is meant! > > Unless there is something wrong... Then please try to be more explicit. > > > > If you prefer to not see this, there is my patch proposal somewhere > > in this older thread: > > Subject: [patch] genirq: temporary fix for level-triggered IRQ resend > > Date: Wed, 8 Aug 2007 13:00:37 +0200 > > > > On the other hand, if it works OK, it would be better to let it be > > tested more like this... > > Hmm. This solution is still just pampering over the real problem. The > delayed disable just re-sends level interrupts unnecessarily. I have a > fix (needs some testing) for this, which I send out tomorrow, when I'm > really back from vacation. > > But suppressing the resend is not fixing the driver problem. The problem > can show up with spurious interrupts and with interrupts on a shared PCI > interrupt line at any time. It just might take weeks instead of minutes. Doesn't it look like a little change of mind? Well, there are probably (but need more testing) two other solutions: _SW_RESEND and disabling without delay for levels only... Jarek P. - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
