appearing again: kernel: eth0: too many iterations (6) in nv_nic_irq
It seems that this problem with NVidia's nic comes up more and more... From time to time we get this in the log: Jan 27 14:43:12 duvel kernel: eth0: too many iterations (6) in nv_nic_irq. We algo get Jan 27 11:32:43 duvel kernel: KERNEL: assertion ((int)tcp_packets_in_flight(tp) = 0) failed at net/ipv4/tcp_input.c (1274) But at different moments, as shown above. Are they related? What's the meaning of the assertion failed one? The messages are more likely to appear when traffic is high (500Mb/s). This is with 2.6.22.16. Any suggestions? -- To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: appearing again: kernel: eth0: too many iterations (6) in nv_nic_irq
On Mon, 28 Jan 2008 11:32:55 -0200 [EMAIL PROTECTED] (Carlos Carvalho) wrote: It seems that this problem with NVidia's nic comes up more and more... From time to time we get this in the log: Jan 27 14:43:12 duvel kernel: eth0: too many iterations (6) in nv_nic_irq. We algo get Jan 27 11:32:43 duvel kernel: KERNEL: assertion ((int)tcp_packets_in_flight(tp) = 0) failed at net/ipv4/tcp_input.c (1274) But at different moments, as shown above. Are they related? What's the meaning of the assertion failed one? The messages are more likely to appear when traffic is high (500Mb/s). This is with 2.6.22.16. Any suggestions? -- To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Use NAPI which is available as configuration option in this driver. Increase the max_interrupt_work from the ridiculously low value of 5 to something more larger like 15, with module parameter in /etc/modprobe.d/options: options forcedeth max_interrupt_work=15 Also, see if you motherboard supports MSI, if so add msi=1 module parameter -- Stephen Hemminger [EMAIL PROTECTED] -- To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: appearing again: kernel: eth0: too many iterations (6) in nv_nic_irq
On Mon, Jan 28, 2008 at 11:32:55AM -0200, Carlos Carvalho wrote: It seems that this problem with NVidia's nic comes up more and more... From time to time we get this in the log: Jan 27 14:43:12 duvel kernel: eth0: too many iterations (6) in nv_nic_irq. We algo get Jan 27 11:32:43 duvel kernel: KERNEL: assertion ((int)tcp_packets_in_flight(tp) = 0) failed at net/ipv4/tcp_input.c (1274) But at different moments, as shown above. Are they related? What's the meaning of the assertion failed one? The messages are more likely to appear when traffic is high (500Mb/s). This is with 2.6.22.16. Any suggestions? I've noticed that when running the latest forcedeth on an older base kernel (2.6.18 in my case) that enable_irq and disable_irq don't quite behave the same way with using MSI as they do with INTx. 2.6.24 works great on the same hardware so something has changed between at leat 2.6.18 and now to make life better. I've been meaning to look at those calls and figure out if we can replace them with simple calls to disable the hardware IRQs only, but haven't had a chance yet. -- To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: appearing again: kernel: eth0: too many iterations (6) in nv_nic_irq
Stephen Hemminger ([EMAIL PROTECTED]) wrote on 28 January 2008 08:06: On Mon, 28 Jan 2008 11:32:55 -0200 [EMAIL PROTECTED] (Carlos Carvalho) wrote: It seems that this problem with NVidia's nic comes up more and more... From time to time we get this in the log: Jan 27 14:43:12 duvel kernel: eth0: too many iterations (6) in nv_nic_irq. We algo get Jan 27 11:32:43 duvel kernel: KERNEL: assertion ((int)tcp_packets_in_flight(tp) = 0) failed at net/ipv4/tcp_input.c (1274) But at different moments, as shown above. Are they related? What's the meaning of the assertion failed one? The messages are more likely to appear when traffic is high (500Mb/s). This is with 2.6.22.16. Any suggestions? Use NAPI which is available as configuration option in this driver. Already in use. Increase the max_interrupt_work from the ridiculously low value of 5 to something more larger like 15, with module parameter in /etc/modprobe.d/options: options forcedeth max_interrupt_work=15 Will try. Also, see if you motherboard supports MSI, if so add msi=1 module parameter It does, I have this in the config: CONFIG_ARCH_SUPPORTS_MSI=y CONFIG_PCI_MSI=y How can I set these options with the driver compiled in the kernel and not as a module? I can change the max_interrupt_work in the source but what about msi? Any ideas about the assertion ((int)tcp_packets_in_flight...? -- To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: too many iterations (6) in nv_nic_irq
Carl-Daniel Hailfinger wrote: Hi Jeff, IIRC you had too many iterations (6) in nv_nic_irq appear regularly in your dmesg with kernel 2.6.16. Did this disappear in more recent kernels? If not, can you try the disable_msi and disable_msix module parameters if they help in your case? Yes, it disappeared in recent kernels. Jeff - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
forcedeth: eth0: too many iterations (6) in nv_nic_irq.
kern.log looks like this: Dec 29 14:25:37 superman kernel: eth0: too many iterations (6) in nv_nic_irq. Dec 29 14:26:11 superman kernel: eth0: too many iterations (6) in nv_nic_irq. Dec 29 14:27:12 superman last message repeated 299 times Dec 29 14:28:13 superman last message repeated 221 times Dec 29 14:29:00 superman last message repeated 432 times Dec 29 14:29:50 superman last message repeated 219 times New messages are generated as soon as I load the eth0-interface. Is this message considered an error, or is it normal under load? If it is normal to get the message, it maybe should be changed to a debug-only message? System info: kernel: 2.6.15-rc6 amd64 SMP CPU:Athlon 64 X2 3800+ Ethernet: nVidia CK804 Ethernet Controller rev a3 with forcedeth driver superman:~# cat /proc/interrupts CPU0 CPU1 0: 106459 172278185IO-APIC-edge timer 1: 0 1465IO-APIC-edge i8042 8: 0 0IO-APIC-edge rtc 9: 0 0 IO-APIC-level acpi 12: 1912IO-APIC-edge i8042 14: 0 37IO-APIC-edge ide0 58: 79 345100 IO-APIC-level skge 217: 199446 157669267 IO-APIC-level eth0 225: 45827 972316 IO-APIC-level libata 233: 44121 963146 IO-APIC-level libata NMI: 0 0 LOC: 172392700 172392678 ERR: 0 MIS: 0 superman:~# / Anders - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
