From: Davide Libenzi <davidel@xmail.virusscreen.com>
To: "Micah Gorrell" <angelcode@myrealbox.com>,
"Andrey Savochkin" <saw@saw.sw.com.sg>
Cc: "Romain Kang" <romain@kzsu.stanford.edu>,
<linux-kernel@vger.kernel.org>, <root@chaos.analogic.com>,
"Craig I. Hagan" <hagan@cih.com>
Subject: Re: eepro100 - Linux vs. FreeBSD
Date: Tue, 30 Jan 2001 08:15:39 -0800 [thread overview]
Message-ID: <01013008153900.01000@ewok.dev.mycio.com> (raw)
In-Reply-To: <003001c08acf$7ae475f0$9b2f4189@angelw2k>
In-Reply-To: <003001c08acf$7ae475f0$9b2f4189@angelw2k>
On Tuesday 30 January 2001 08:14, Micah Gorrell wrote:
> I have been running 2.2 on many machines since its release and have updated
> to the latest version of 2.2 many times. All of these machines have an
> eepro100 and I never saw a single problem with any of them. I updated most
> of my machines to 2.4 over the course of a week and within a day of
> updating each of them showed the problem. This may be pure chance but it
> sounds to me as if it is a difference with the 2.4 kernel.
I had the same problem on my dual PIII with a dual eepro100 NIC.
2.4.1-pre12 solved the problem ( don't ask me why :) ).
- Davide
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-30 16:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 15:15 Micah Gorrell
2001-01-30 16:15 ` Davide Libenzi [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-30 17:35 Micah Gorrell
2001-01-29 18:06 Micah Gorrell
2001-01-30 7:34 ` Andrey Savochkin
2001-01-29 16:24 Romain Kang
2001-01-29 17:32 ` Craig I. Hagan
2001-01-29 17:48 ` Richard B. Johnson
2001-01-29 18:02 ` Sergey Kubushin
2001-01-29 18:15 ` Udo A. Steinberg
2001-01-29 18:16 ` Richard B. Johnson
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=01013008153900.01000@ewok.dev.mycio.com \
--to=davidel@xmail.virusscreen.com \
--cc=angelcode@myrealbox.com \
--cc=hagan@cih.com \
--cc=linux-kernel@vger.kernel.org \
--cc=romain@kzsu.stanford.edu \
--cc=root@chaos.analogic.com \
--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
all inboxes | Powered by JetHome®