From: Holger.Woehle@arcor.net
To: linux-kernel@vger.kernel.org
Subject: sundance.o only two ports working
Date: Wed, 14 Aug 2002 18:37:31 +0100 [thread overview]
Message-ID: <41256C15.00613A82.00@ffm-hq-gtw01.Arcor.net> (raw)
Hello,
i have a strange problem with two of my machines:
They are identical P4 systems with Intel Chipset with two epro100 adapters
onboard and a d-link dfe-580TX quad ethernet card.
I am using Kernel 2.4.18 and sundance.o v1.07a 7/9/2002.
The problem is, that i only can use the two first ports of the d-link card.
I can set up all four with no problems according to mii-diag and alta-diag.
Each port recognises link up/down and negotiates to the right speed and
flowcontrol.
But when i send traffic over the ports 4&5, at first nothing happens and of
course i can't see any interrupts in /proc/interrupts eth4 eth5 and after a
while i get
the console message:
eth4: Transmit timed out, status c0, resetting...
Having a look at alta-diag i noticed, that the column
" Interrupt status is..." differs between Index#1 / #2 and Index#3 / #4
Index#1 and #2 tells: Interrupt status is 0000: No interrupts pending.
Index#3 and #4 tells: Interrupt status is 0101: Interrupt summary Link status
changed
and after genrating some traffic that line changes at Index#3 & #4 to:
Interrupt status is 0301: Interrupt summary Link status changed Tx DMA done.
The beehavier is identical on both machines.
For better analysing i can send a file including cat /proc/pic, pci-config,
alta-diag -e and alta-diag -m bevor and after sending some pings.
This file is a some more pages long so i don't know if it is ok to send it to
the mailing list.
with regards
Holger
next reply other threads:[~2002-08-14 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-14 17:37 Holger.Woehle [this message]
2002-08-14 17:05 ` Matthew Hall
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=41256C15.00613A82.00@ffm-hq-gtw01.Arcor.net \
--to=holger.woehle@arcor.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®