Messages in this thread | | | Subject | Re: 2.6.20->2.6.21 - networking dies after random time | From | Thomas Gleixner <> | Date | Thu, 26 Jul 2007 10:10:31 +0200 |
| |
On Thu, 2007-07-26 at 10:13 +0200, Jarek Poplawski wrote: > > I wanted to test them all on 2.6.22.1, but I didn't have enough time. > > I've verified only that 2.6.22.1 has the same problem. I can test it > > later, but I can report results back at beginning of next week. > > > So, everything is clear - any changes are good! > Except the signed-off ones... > > Thanks Marcin, > Jarek P. > > PS: Now, it seems to me Thomas could be the nearest. BTW, could somebody > give me some tip, how these re-triggered interrupts are skipped on dev's > reset before enable_irq?
I think the correct solution is really not to resend level type interrupts. If the interrupt line is still active, then the interrupt comes up by itself. I'm cooking a patch for that.
The other question is:
Is the driver confused by the resent irq or is the chip-set unhappy about the resend ?
We could figure the latter out by activating the software based resend method.
tglx
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |