From: Andrey Nekrasov <andy@spylog.ru>
To: linux-kernel@vger.kernel.org, linux.nics@intel.com
Subject: NIC on Intel STL2 - bad work with eepro100 & e100
Date: Fri, 4 Oct 2002 15:31:28 +0400 [thread overview]
Message-ID: <20021004113128.GA31145@an.local> (raw)
Hello.
1. Hardware:
Intel Server Board STL2.
Network: onboard NIC "Intel(R) 82559 single chip PCI LAN controller"
Software:
Linux kernel up-to version 2.4.20pre9 + arp hidden patch.
2. dmesg:
...
Intel(R) PRO/100 Network Driver - version 2.1.15-k1
Copyright (c) 2002 Intel Corporation
e100: hw init failed
e100: Failed to initialize, instance #0
...
3. cat /proc/pci
...
Bus 0, device 3, function 0:
Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 8).
IRQ 18.
Master Capable. Latency=66. Min Gnt=8.Max Lat=56.
Non-prefetchable 32 bit memory at 0xfb101000 [0xfb101fff].
I/O at 0x5400 [0x543f].
Non-prefetchable 32 bit memory at 0xfb000000 [0xfb0fffff].
...
ps. eepro100 driver work, but bad.
dmesg:
...
<4>eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html
<4>eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.s
<6>eth0: OEM i82557/i82558 10/100 Ethernet, 00:D0:B7:B6:B2:8B, IRQ 18.
<6> Board assembly 000000-000, Physical connectors present: RJ45
<6> Primary interface chip i82555 PHY #1.
<6> General self-test: passed.
<6> Serial sub-system self-test: passed.
<6> Internal registers self-test: passed.
<6> ROM checksum self-test: passed (0x04f4518b).
...
...
eepro100: wait_for_cmd_done timeout!
eepro100: wait_for_cmd_done timeout!
eepro100: wait_for_cmd_done timeout!
eepro100: wait_for_cmd_done timeout!
eepro100: wait_for_cmd_done timeout!
eepro100: wait_for_cmd_done timeout!
...
And periodically freeze.
--
bye.
Andrey Nekrasov, SpyLOG.
next reply other threads:[~2002-10-04 11:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 11:31 Andrey Nekrasov [this message]
2002-10-04 13:50 ` NIC on Intel STL2 - bad work with eepro100 & e100 Paul P Komkoff Jr
2002-10-04 17:03 ` Kallol Biswas
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=20021004113128.GA31145@an.local \
--to=andy@spylog.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.nics@intel.com \
/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