From: "Micah Gorrell" <angelcode@myrealbox.com>
To: "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:21 -0700 [thread overview]
Message-ID: <003001c08acf$7ae475f0$9b2f4189@angelw2k> (raw)
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.
Micah
___
The irony is that Bill Gates claims to be making a stable operating system
and Linus Torvalds claims to be trying to take over the world
-----Original Message-----
From: "Andrey Savochkin" <saw@saw.sw.com.sg>
To: "Micah Gorrell" <angelcode@myrealbox.com>
Cc: "Romain Kang" <romain@kzsu.stanford.edu>;
<linux-kernel@vger.kernel.org>; <root@chaos.analogic.com>; "Craig I. Hagan"
<hagan@cih.com>
Date: Tuesday, January 30, 2001 12:35 AM
Subject: Re: eepro100 - Linux vs. FreeBSD
>On Mon, Jan 29, 2001 at 11:06:11AM -0700, Micah Gorrell wrote:
>> As stated in a number of previous messages to this list many people have
had
>> serious problems with the eepro100 driver in 2.4. These problems where
not
>> there in 2.2 and it is not a select few machines showing this so I very
much
>> doubt that it is a configuration problem. I assume that the intel driver
>> would prolly fix all of these issues but its not ready for 2.4 yet and
its
>[snip]
>
>In the first place, the "no resource" problem is a hardware one.
>As far as I understand, it's a buggy (or undocumented) timing requirement
>for some revisions.
>This problem showed with any kernel, 2.2 or 2.4, until a workaround was
>developed. On a single computer suffering from that problem it showed not
on
>every boot, but about in 30 percents. That's why the reports were
different.
>So, the kernel version is irrelevant to this problem.
>
>Best regards
> Andrey V.
> Savochkin
>
>
-
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 reply other threads:[~2001-01-30 15:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 15:15 Micah Gorrell [this message]
2001-01-30 16:15 ` Davide Libenzi
-- 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='003001c08acf$7ae475f0$9b2f4189@angelw2k' \
--to=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®