From: Stephen Hemminger <shemminger@linux-foundation.org>
To: carlos@fisica.ufpr.br (Carlos Carvalho)
Cc: netdev@vger.kernel.org
Subject: Re: appearing again: kernel: eth0: too many iterations (6) in nv_nic_irq
Date: Mon, 28 Jan 2008 08:06:56 -0800 [thread overview]
Message-ID: <20080128080656.1cc8a4e0@deepthought> (raw)
In-Reply-To: <18333.55687.621653.838538@fisica.ufpr.br>
On Mon, 28 Jan 2008 11:32:55 -0200
carlos@fisica.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?
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> 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 <stephen.hemminger@vyatta.com>
next prev parent reply other threads:[~2008-01-28 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 13:32 appearing again: kernel: eth0: too many iterations (6) in nv_nic_irq Carlos Carvalho
2008-01-28 16:06 ` Stephen Hemminger [this message]
2008-01-29 1:52 ` Carlos Carvalho
2008-01-29 1:07 ` Andy Gospodarek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080128080656.1cc8a4e0@deepthought \
--to=shemminger@linux-foundation.org \
--cc=carlos@fisica.ufpr.br \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.