Red Hat Bugzilla – Bug 179422
eth0: too many iterations (6) in nv_nic_irq.
Last modified: 2007-11-30 17:11:22 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Description of problem:
The kernel likes to print "eth0: too many iterations (6) in nv_nic_irq." all the time. This did not happen with FC4 on the same hardware.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.Get annoying messages
Actual Results: The system should run but not complain.
Expected Results: The system works but like to complain about eth0.
The ethernet hardware uses the forcedeth driver.
# lspci | grep -i eth
00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3)
03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E Gigabit Ethernet Controller (rev 15)
The message is annoying, but not necessarily bad. You might try the adding a
line like this to /etc/modprobe.conf:
options forcedeth max_interrupt_work=10
If the message comes back after that, it should say "too many iterations (11)"
instead. There is nothing magic about 10, you should experiment to find the
lowest number that provides few or none of those messages.
Please do that, and post the number here...thanks!
I see the message sometimes at max_interrupt_work=15 but not, so far, at
The upstream developers are aware of the issue -- hopefully they will fix it
In the meantime, it looks like you have a reasonable work-around. Thanks for
Could you send me the output of "cat /proc/interrupts"?
# cat /proc/interrupts
0: 13446558 IO-APIC-edge timer
1: 134 IO-APIC-edge i8042
7: 1 IO-APIC-edge parport0
8: 0 IO-APIC-edge rtc
9: 0 IO-APIC-level acpi
12: 134 IO-APIC-edge i8042
15: 482757 IO-APIC-edge ide1
50: 0 IO-APIC-level NVidia CK804
66: 1 PCI-MSI sky2
74: 2 IO-APIC-level ohci1394
217: 50725 IO-APIC-level libata, ohci_hcd:usb1
225: 2984474 IO-APIC-level libata, ehci_hcd:usb2
233: 5558065 IO-APIC-level eth0
The current kernel is 2.6.15-1.1948_FC5
Is there anything in particular that triggers the message? ie. running a
particular application, etc.
Created attachment 124704 [details]
Output of lsmod
See attachment for output of lsmod.
The messages seems to come mostly when running yum or when the cron-jobs are
run at night - anything that stress the system a bit. Since this is running
FC5test2 the machine is just used for testing small things.