From: "Mark J. Steiglitz" <steig@DSG.Stanford.EDU>
To: ultralinux@vger.kernel.org
Subject: Linux de4x5 driver bug?
Date: Mon, 15 Jun 1998 22:44:32 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-90222357631021@msgid-missing> (raw)
I am running UltraLinux 1.0.9 with kernel version 2.1.105 on a Sun Ultra 5.
The system contains a Znyx ZX346 4-port 10/100 ethernet card, which is
recognized by the de4x5 driver.
The first port of the card operates properly, but the other three ports either
fail to receive any packets, or exhibit extremely poor performance, with delays
of approximately 2 seconds just to receive a packet from the same ethernet.
Other minor problems which may be related are that "ifconfig -a" shows
incorrect values for various packet counters for any interface corresponding to
any Znyx ZX346 port, and that "netstat -i" reports "unknown interface" for any
interface.
The following messages are displayed on the console when doing a
modprobe de4x5 :
kernel: loading device 'eth1'...
kernel: eth1: DC21140 at 0xfffff9fe02001000 (PCI bus 3, device 4), h/w address 00:c0:95:e0:2e:28,
kernel: eth1: Using generic MII device control. If the board doesn't operate,
kernel: please mail the following dump to the author:
kernel:
kernel: MII device address: 1
kernel: MII CR: 3000
kernel: MII SR: 7809
kernel: MII ID0: 15
kernel: MII ID1: f423
kernel: MII ANA: 1e1
kernel: MII ANC: 0
kernel: MII 16: 58
kernel: MII 17: 85e8
kernel: MII 18: 10
kernel:
kernel: and requires IRQ608060 (provided by PCI BIOS).
kernel: de4x5.c:V0.536 1998/3/5 davies@maniac.ultranet.com
kernel: loading device 'eth2'...
kernel: eth2: DC21140 at 0xfffff9fe02001080 (PCI bus 3, device 5), h/w address 00:c0:95:e0:2e:29,
kernel: eth2: Using generic MII device control. If the board doesn't operate,
kernel: please mail the following dump to the author:
kernel:
kernel: MII device address: 1
kernel: MII CR: 3000
kernel: MII SR: 7809
kernel: MII ID0: 15
kernel: MII ID1: f423
kernel: MII ANA: 1e1
kernel: MII ANC: 0
kernel: MII 16: 58
kernel: MII 17: 85e8
kernel: MII 18: 10
kernel:
kernel: and requires IRQ608070 (provided by PCI BIOS).
kernel: de4x5.c:V0.536 1998/3/5 davies@maniac.ultranet.com
kernel: loading device 'eth3'...
kernel: eth3: DC21140 at 0xfffff9fe02001400 (PCI bus 3, device 6), h/w address 00:c0:95:e0:2e:2a,
kernel: eth3: Using generic MII device control. If the board doesn't operate,
kernel: please mail the following dump to the author:
kernel:
kernel: MII device address: 1
kernel: MII CR: 3000
kernel: MII SR: 7809
kernel: MII ID0: 15
kernel: MII ID1: f423
kernel: MII ANA: 1e1
kernel: MII ANC: 0
kernel: MII 16: 58
kernel: MII 17: 85e8
kernel: MII 18: 10
kernel:
kernel: and requires IRQ608080 (provided by PCI BIOS).
kernel: de4x5.c:V0.536 1998/3/5 davies@maniac.ultranet.com
kernel: loading device 'eth4'...
kernel: eth4: DC21140 at 0xfffff9fe02001480 (PCI bus 3, device 7), h/w address 00:c0:95:e0:2e:2b,
kernel: eth4: Using generic MII device control. If the board doesn't operate,
kernel: please mail the following dump to the author:
kernel:
kernel: MII device address: 1
kernel: MII CR: 3000
kernel: MII SR: 7809
kernel: MII ID0: 15
kernel: MII ID1: f423
kernel: MII ANA: 1e1
kernel: MII ANC: 0
kernel: MII 16: 58
kernel: MII 17: 85e8
kernel: MII 18: 10
kernel:
kernel: and requires IRQ608090 (provided by PCI BIOS).
kernel: de4x5.c:V0.536 1998/3/5 davies@maniac.ultranet.com
--Mark
reply other threads:[~1998-06-15 22:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ultrasparc-90222357631021@msgid-missing \
--to=steig@dsg.stanford.edu \
--cc=ultralinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.