Thread View: chico.ect.help
3 messages
3 total messages
Started by David A. Ranch
Tue, 22 Oct 1996 00:00
Grr.. Linux: eth0: Infinite loop in interupt, Status FFFF
Author: David A. Ranch
Date: Tue, 22 Oct 1996 00:00
Date: Tue, 22 Oct 1996 00:00
33 lines
2339 bytes
2339 bytes
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
After this, all communications to the ethernet card stop until I reboot
the machine. One person mentioned that it could be related to the IP
bridging. Any ideas will be greatly appreciated!
Details include:
Hardware: 486/i66 clone (Chaintech MB), 256k cache, 8MB RAM,
Cirrus Login 5428 VLB video card, Winbond-based EIDE VLB
controller, Aztec sound card (SBP clone), 3Com 3C509B ethernet
card (coax), 3 IDE HDs, 1 Panasonic CD-ROM (SBP interface), and
one 3.5" floppy drive.
Software: Linux kernel v2.0.20 compiled via GCC v2.6.3 (with the
following kernel options:
"IP forwaring", "IP Firewall", "IP masqrading" and the rest
of the kernel is standard. I'm also running Diald (dynamic
PPP dialer). I've seen this same error with v1.3.x kernels
without the IP Masq but with the IP forwarding still on)
Please send replied to dranch@ecst.csuchico.edu and I will re-post my
results. Thanks!
--David
--
+----------------------------------------------------------------------------+
| David A. Ranch - ISDN/Cablemodems/PCs dranch@ecst.csuchico.edu |
+---- ----+
+----- For more detailed info, check out: www.ecst.csuchico.edu/~dranch -----+
Re: Grr.. Linux: eth0: Infinite loop in interupt, Status FFFF
Author: Donald Becker
Date: Fri, 25 Oct 1996 00:00
Date: Fri, 25 Oct 1996 00:00
31 lines
2248 bytes
2248 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 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! >After this, all communications to the ethernet card stop until I reboot >the machine. One person mentioned that it could be related to the IP >bridging. Any ideas will be greatly appreciated! While IP bridging has a few really unusual bugs, this isn't likely related to it. 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 -- Donald Becker becker@cesdis.gsfc.nasa.gov USRA-CESDIS, Center of Excellence in Space Data and Information Sciences. Code 930.5, Goddard Space Flight Center, Greenbelt, MD. 20771 301-286-0882 http://cesdis.gsfc.nasa.gov/pub/people/becker/whoiam.html
Re: Grr.. Linux: eth0: Infinite loop in interupt, Status FFFF
Author: 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 /__)/__) / / / / /_ /\ / /_ /
/ / \ / / / / /__ / \/ /___ /-------------------------------------------------------------------------------
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads