On Wednesday 12 November 2008 15:29:52 Brian J. Murrell wrote: > On Wed, 2008-11-12 at 15:22 +0100, Michael Buesch wrote: > > On Wednesday 12 November 2008 14:22:46 Brian J. Murrell wrote: > > > I can see in the bottom-half where all of those are handled except > > > B43_IRQ_DMA. I don't see anywhere in the whole driver where that is > > > handled in fact. > > > > It's handled implicitely by the DMA handling. You can ignore that IRQ. > > OK. > > > What's not handled correctly is the PMQ and TBTT indication IRQs. > > See the FIXMEs and TODOs in the code that handle these IRQs. > > Indeed. So that's the root of the high softirqs on an AP?
Well, could be, if they trigger often (hundreds of times per second), maybe because the IRQ needs to be ACKed in some way, for example. I don't know. >From your logs it's rather hard to tell, because the logs don't have timestamps. So if you show me a log with lots of $foobar triggering, I don't know whether it is due to the long runtime or due to a real flood. So I cannot get a "feeling" of what's going on. But that special feeling often is _the_ key to resolve strange IRQ issues. So it would be cool, if you could turn on printk timestamps in the kernel config "kernel hacking" menu. -- Greetings Michael. _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
