From: Marc Duponcheel <mduponch@cisco.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4.19rc2 -> 2.4.19rc3 : no more eth
Date: Tue, 23 Jul 2002 15:02:21 +0200 [thread overview]
Message-ID: <20020723130221.GF29367@cisco.com> (raw)
Dear kernel crew.
I follow the stable kernel and run 2.4.18 just fine on 3 machines.
Recently I thought about trying 2.4.19rc kernels. That went fine as
well with one exception.
One machine (with 2 ethernet controllers)
Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 0c)
3Com Corporation 3c900B-TPO [Etherlink XL TPO] (rev 04)
will no longer recognise -any- of those.
Note that this 'artifact' only happens with 2.4.19rc3. The .config
between 2.4.19rc2 did not change 2.4.19rc3
During boot I see OOPses (which for some reason, my syslog does not
see).
Because this is a rather severe change [:-)] I wonder if I this rings
a bell.
Thanks for your valuable time
--
Greetings,
Marc Duponcheel Multicast Development Engineer Cisco Systems
email: mduponch@cisco.com tel: +32 2 704 52 40 cell: +32 478 68 10 91
next reply other threads:[~2002-07-23 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 13:02 Marc Duponcheel [this message]
2002-07-23 23:55 ` 2.4.19rc2 -> 2.4.19rc3 : no more eth Marc Duponcheel
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=20020723130221.GF29367@cisco.com \
--to=mduponch@cisco.com \
--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