[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <18334.34546.45174.858242@fisica.ufpr.br>
Date: Mon, 28 Jan 2008 23:52:50 -0200
From: carlos@...ica.ufpr.br (Carlos Carvalho)
To: Stephen Hemminger <shemminger@...ux-foundation.org>
Cc: netdev@...r.kernel.org
Subject: Re: appearing again: kernel: eth0: too many iterations (6) in
nv_nic_irq
Stephen Hemminger (shemminger@...ux-foundation.org) wrote on 28 January 2008 08:06:
>On Mon, 28 Jan 2008 11:32:55 -0200
>carlos@...ica.ufpr.br (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 majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists