From: Andy Gospodarek <andy@greyhouse.net>
To: Carlos Carvalho <carlos@fisica.ufpr.br>
Cc: netdev@vger.kernel.org
Subject: Re: appearing again: kernel: eth0: too many iterations (6) in nv_nic_irq
Date: Mon, 28 Jan 2008 20:07:06 -0500 [thread overview]
Message-ID: <20080129010706.GC21912@gospo.usersys.redhat.com> (raw)
In-Reply-To: <18333.55687.621653.838538@fisica.ufpr.br>
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.
prev parent reply other threads:[~2008-01-29 1: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
2008-01-29 1:52 ` Carlos Carvalho
2008-01-29 1:07 ` Andy Gospodarek [this message]
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=20080129010706.GC21912@gospo.usersys.redhat.com \
--to=andy@greyhouse.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).