Am Donnerstag 25 November 2010 schrieb Tim Blechmann: > > > > >> Mind to put a (maybe rate limited) printk into the interrupt thread > > > > >> that prints out "reg" > > > > >> and "reg_mcu" so that we can see which interrupts get triggered? > > > > > > > > > > log attached, generated with: > > > > Thanks. Unfortunately nothing special in there. Mostly RX and TX > > > > interrupts. So there must be something else ... > > > > > > Tim, is this on x86 hw? Or something else? > > > > I don't know if this will do any good or harm but it could be worth a try > > as the spec for rt61pci says something like: "Don't enable interrupt > > mitigation in the same write as releasing the other masks.". Since we > > always write a mitigation period of 0xff == "No mitigation period" we can > > simply leave interrupt mitigation disabled. > > > > I really don't have any clue if this will fix anything but it might be > > worth a try. > > i have been running this patch for a few days and i haven't experienced the > problem again. Ok, I'll officially submit the patch soon ... > according to `top', the kernel thread `irq/16-0000:08:' still is the kernel > thread, that is using the most cpu time (after an uptime of 8 hours) it is about > 50 seconds, while the second most expensive kernel thread (`kworker/2:1') takes > below 5 seconds of cpu time. No idea :( Helmut -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
