Article View: chico.ect.help
Article #3Re: Grr.. Linux: eth0: Infinite loop in interupt, Status FFFF
From: David Coons
Date: Mon, 28 Oct 1996 00:00
Date: Mon, 28 Oct 1996 00:00
45 lines
3160 bytes
3160 bytes
In article <54hmse$gup@charnel.ecst.csuchico.edu>,
David A. Ranch <dranch@ecst.csuchico.edu> wrote:
>I'm hoping someone can help me with this problem I'm having. On a Linux
>box, I'm getting the following SYSLOG error:
>
> Kernel: eth0: Infinte loop in interupt, Status FFFF
Donald Becker <becker@cesdis.gsfc.nasa.gov> wrote:
: The message comes from the 3Com 3C509 driver.
: It's there to inform you that something has gone horribly wrong.
: In this case, status 0xffff, the card has disappeared from the I/O space!
: More likely one of the following is the problem:
: the card isn't seated correctly
: your hardware (especially the power supply) is flakey
: you had a power hit
: you tried to insert a second 3c509 module, deactivating all of the card.
: you ran an ISA Plug-and-Play activation program
We have a similar problem on our P166 with a 3c509 ISA card running
Slackware96 and kernel 2.0.0. The most common console messages are:
Waiting for 3c509 to discard packet, status 2011.
Waiting for 3c509 to discard packet, status 2001.
which don't cause any problems, but still make us wonder. Occasionally,
we get:
eth0: Infinite loop in interrupt, status 2011.
and again, it appears harmless, since things keep running normally. Also,
every now and then we get also harmless sequences like this:
eth0: Couldn't allocate a sk_buff of size 1514.
eth0: Couldn't allocate a sk_buff of size 1514.
eth0: Couldn't allocate a sk_buff of size 962.
and
Couldn't get a free page.....
The only thing of note about our configuration is that a NeXT box
sitting next door is running software that uses write() calls to
plunk 3MB files onto the Linux box over NFS, where the Linux box
is the NFS server.
-------------------------------------------------------------------------------
dcoons __ __ ____ ___ ___ ____
dcoons@primenet.com /__)/__) / / / / /_ /\ / /_ /
/ / \ / / / / /__ / \/ /___ /-------------------------------------------------------------------------------
Technical Details
Message-ID:
<5521pl$hbv@nnrp1.news.primenet.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<54hmse$gup@charnel.ecst.csuchico.edu> <54r3jo$cib@beowulf.gsfc.nasa.gov>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 102b32,798335fbf270b51f X-Google-Attributes: gid102b32,public X-Google-Thread: 10869b,798335fbf270b51f X-Google-Attributes: gid10869b,public X-Google-Thread: f9b51,798335fbf270b51f X-Google-Attributes: gidf9b51,public X-Google-Thread: 10669a,798335fbf270b51f X-Google-Attributes: gid10669a,public X-Google-Thread: 10fe8a,798335fbf270b51f X-Google-Attributes: gid10fe8a,public From: David Coons <dcoons@primenet.com> Subject: Re: Grr.. Linux: eth0: Infinite loop in interupt, Status FFFF Date: 1996/10/28 Message-ID: <5521pl$hbv@nnrp1.news.primenet.com> X-Deja-AN: 192684972 references: <54hmse$gup@charnel.ecst.csuchico.edu> <54r3jo$cib@beowulf.gsfc.nasa.gov> organization: Primenet (602)416-7000 x-posted-by: dcoons@206.165.5.106 (dcoons) newsgroups: chico.ect.help,comp.os.linux.setup,comp.os.linux.hardware,comp.os.linux.networking,comp.sys.ibm.pc.hardware.networking