From: David Rees <dbr@greenhydrant.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.16 freezed up with eepro100 module
Date: Thu, 29 Nov 2001 21:57:46 -0800 [thread overview]
Message-ID: <20011129215746.A29355@greenhydrant.com> (raw)
In-Reply-To: <15366.21354.879039.718967@abasin.nj.nec.com> <20011129095107.A17457@conwaycorp.net> <3C070FEC.3602CB49@pobox.com> <20011130114506.A4789@bee.lk>
In-Reply-To: <20011130114506.A4789@bee.lk>; from anuradha@gnu.org on Fri, Nov 30, 2001 at 11:45:06AM +0600
On Fri, Nov 30, 2001 at 11:45:06AM +0600, Anuradha Ratnaweera wrote:
>
> Has anybody got the same issue with non Dell machines?
>
> I am running 2.4.16 on a Compaq proliant ML 370 without problems (machine has
> been up for 2+ days with the new kernels, though). Trafic is not very high.
I don't have any non-Dell machines with the eepro100, but I did put one of
our Dells on 2.2.16 35 hours ago with the eepro100 driver. I don't know the
exact model, but it's an older dual 500MHz PIII machine. Traffic is light,
with only appoximately 100MB being transfered over the network so far.
Is there a workload that can reproduce the hang? If so, I might be able to
do a bit of testing...
I've also got a couple Dell 2400s, but those are still running 2.4.9.
Unfortunately those are production machines, so I don't want to mess with
them right now.
-Dave
next prev parent reply other threads:[~2001-11-30 5:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-29 15:25 2.4.16 freezed up with eepro100 module Sven Heinicke
2001-11-29 15:51 ` Nathan Poznick
2001-11-29 16:14 ` Sven Heinicke
2001-11-30 4:49 ` J Sloan
2001-11-30 5:45 ` Anuradha Ratnaweera
2001-11-30 5:57 ` David Rees [this message]
2001-11-30 6:07 ` SBP2 Support for multiple LUNs - Changers ?? Ramaraj Pandian
2001-11-30 14:23 ` 2.4.16 freezed up with eepro100 module Nathan Poznick
2001-11-30 16:04 ` Sven Heinicke
2001-11-30 22:31 ` Nathan Poznick
2001-12-01 0:17 ` Mike Fedyk
2001-12-01 10:17 ` Andrey Savochkin
2001-12-03 15:37 ` Nathan Poznick
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=20011129215746.A29355@greenhydrant.com \
--to=dbr@greenhydrant.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.