From: elf@florence.buici.com
To: saw@saw.sw.com.sg, linux-kernel@vger.kernel.org
Subject: eepro100 selftest failure in 2.4.11 (and .10)
Date: Wed, 10 Oct 2001 09:50:12 -0700 [thread overview]
Message-ID: <20011010095012.A29307@buici.com> (raw)
I checked the released 2.4.11 kernel and found the same driver
failure as was present in the 2.4.10 kernel.
I'm running Linux on a single-board computer that uses an Intel
ethernet chip, apparently i82557 compatible. The 2.2.17 kernel boots
OK. The 2.4.10 kernel fails to initialize the chip complaining
[thanks to kernel message scrollback]:
eth0: Intel Corporation 82557 [Ethernet Pro 100], 00:60:92:00:17:F4, IRQ 11
Board assembly 721383-006, Physical connectors present: RJ45
Primary interface chip 82555 PHY #1
Self test failed, status ffffffff:
Failure to initialize the i82557.
Verify that the card is in a bus-master capable slot.
When the 2.2.17 kernel boots, it reports that
The receiver lock-up bug exists -- enabling workaround.
and all of the tests succeed. The rest of the messages are the same
except for driver version information.
next reply other threads:[~2001-10-10 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 16:50 elf [this message]
2001-10-11 2:47 ` eepro100 selftest failure in 2.4.11 (and .10) Ion Badulescu
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=20011010095012.A29307@buici.com \
--to=elf@florence.buici.com \
--cc=linux-kernel@vger.kernel.org \
--cc=saw@saw.sw.com.sg \
/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