On Tuesday 21 October 2008 05:39:42 Brian J. Murrell wrote: > On Mon, 2008-10-20 at 12:49 +0200, Michael Buesch wrote: > > > > What do you base this assumption on? > > Inference. Nothing more. > > > I think it's simply an unacked IRQ. > > I'm willing to believe anything that sounds plausible. By unacked IRQ > do you mean a software bug somewhere?
I'm talking about an IRQ that's triggered by the firmware, but the driver doesn't correctly ACK it. So it will keep triggering. There are some of these types of IRQs. One being the noise sample IRQ. This is trivial to find out. Simply printk the reason in the IRQ handler (but remove the TX and RX IRQ bits, otherwise the logs will be flooded). You will notice when one IRQ keeps triggering for a long period of time. -- Greetings Michael. _______________________________________________ openwrt-users mailing list [email protected] http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
