in the meantime I find out that the system generates permanently interrupts from the pcnet32 chip after calling request_irq.
You are correct, the problem is outside of the pcnet32 driver, because the driver from kernel version 2.4.18 is also producing that problem. In both driver version, the code near by the call request_irq is the same. Next week I will go forward to analyze that problem. I think the article you found is helpful.
Many thanks to you, best regards, Frank
Don Fry wrote:
Frank,
Last evening I was contacted by someone else that has had this same issue on a 4694-245 box and they have tracked down the problem to a change in the pci bridge irq code. See the following article for more details. http://lwn.net/Articles/38879/
The problem appears to be outside the pcnet32 driver. I don't know any
more than this.
- : 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
