Hi, On Sat, Oct 22, 2011 at 08:47:33AM +0800, Adrian Chadd wrote: > > At this point I'd really suggest whacking other devices into the slot > to see if they generate the same kind of behaviour. Looks like you had it right from the start. After unloading the jme module [*1*] I cannot reproduce the IRQ storm any more. From looking at dmesg it should have been obvious, since it also gets IRQ 17 assigned. I don't know how I missed that, I was sure I had checked. Sorry guys, for most likely wasting your time. And thanks for your patience. Best, Clemens [*1*] $ lspci 06:00.5 Ethernet controller: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller (rev 03)) $ dmesg|grep -i jme [ 6.160187] jme: JMicron JMC2XX ethernet driver version 1.0.8 [ 6.160278] jme 0000:06:00.5: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 6.160305] jme 0000:06:00.5: setting latency timer to 64 [ 6.161154] jme 0000:06:00.5: eth0: JMC250 Gigabit Ethernet chiprev:23 pcirev:3 macaddr:bc:ae:c5:2f:91:47 [ 18.354697] jme 0000:06:00.5: PCI INT A disabled -- 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
