From: Stephen Hemminger <shemminger@osdl.org>
To: Andrew Walrond <andrew@walrond.org>
Cc: "YOSHIFUJI Hideaki / ____________" <yoshfuji@linux-ipv6.org>,
netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: Linux-2.6.3 : [eth0: Too much work at interrupt, status=0x00000001.]
Date: Fri, 20 Feb 2004 11:34:27 -0800 [thread overview]
Message-ID: <20040220113427.0a088fb9@dell_ss3.pdx.osdl.net> (raw)
In-Reply-To: <200402201915.09342.andrew@walrond.org>
On Fri, 20 Feb 2004 19:15:09 +0000
Andrew Walrond <andrew@walrond.org> wrote:
> On Friday 20 Feb 2004 6:20 pm, YOSHIFUJI Hideaki / ____________ wrote:
> > In article <200402201803.12146.andrew@walrond.org> (at Fri, 20 Feb 2004
> 18:03:11 +0000), Andrew Walrond <andrew@walrond.org> says:
> >
> > I've got this several times, randomly, and
> > I had to go to the console to reboot the machine.
> >
>
> Well the machine and network (at least with just ssh access) is working fine
>
> I left the machine (which is a remote rack-mounted server) for an hour and now
> there is perhaps 120 of these warnings. Net is still working though.
>
> Unless anyone has any ideas, I'll move back to 2.4 on this machine
>
> Andrew
The driver needs to be converted to NAPI to sustain high network loads.
The existing driver allocates and copies each receive packet in the interrupt routine.
See the recent revision of 8139too to see what that entails.
next prev parent reply other threads:[~2004-02-20 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 18:03 Andrew Walrond
2004-02-20 18:20 ` YOSHIFUJI Hideaki / 吉藤英明
[not found] ` <200402201915.09342.andrew@walrond.org>
2004-02-20 19:34 ` Stephen Hemminger [this message]
2004-02-20 20:01 ` Andrew Walrond
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=20040220113427.0a088fb9@dell_ss3.pdx.osdl.net \
--to=shemminger@osdl.org \
--cc=andrew@walrond.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=yoshfuji@linux-ipv6.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
all inboxes | Powered by JetHome®