All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anuradha Ratnaweera <anuradha@gnu.org>
To: J Sloan <jjs@pobox.com>
Cc: Nathan Poznick <poznick@conwaycorp.net>,
	Sven Heinicke <sven@research.nj.nec.com>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.4.16 freezed up with eepro100 module
Date: Fri, 30 Nov 2001 11:45:06 +0600	[thread overview]
Message-ID: <20011130114506.A4789@bee.lk> (raw)
In-Reply-To: <15366.21354.879039.718967@abasin.nj.nec.com> <20011129095107.A17457@conwaycorp.net> <3C070FEC.3602CB49@pobox.com>
In-Reply-To: <3C070FEC.3602CB49@pobox.com>; from jjs@pobox.com on Thu, Nov 29, 2001 at 08:49:48PM -0800

On Thu, Nov 29, 2001 at 08:49:48PM -0800, J Sloan wrote:
> Nathan Poznick wrote:
> 
> > Thus spake Sven Heinicke:
> > >
> > > The 2.4.16 kernel finally makes my clients happy with memory
> > > management.  The systems that froz up is a Dell of some sort or other
> > > with two 1Ghz Pentium IIIs and 4G of memory.  But, now I seems to be
> > > having ethernet problems.  With and eepro100 card:
> >
> > I've encountered the same problem, with the same hardware setup (I
> > believe it's a Dell 2400, or something like that), on 2.4.14+xfs.  For
> >
> > [...]
> 
> Using the e100 driver instead seemed to solve the
> problem on the dell servers here.

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.

The driver is built into the kernel.

/proc/pci shows

  Bus  0, device   2, function  0:
    Ethernet controller: Intel Corp. 82557 [Ethernet Pro 100] (rev 8).
      IRQ 5.
      Master Capable.  Latency=64.  Min Gnt=8.Max Lat=56.
      Non-prefetchable 32 bit memory at 0xc4fff000 [0xc4ffffff].
      I/O at 0x2400 [0x243f].
      Non-prefetchable 32 bit memory at 0xc4e00000 [0xc4efffff].
  Bus  0, device   5, function  0:
    Ethernet controller: Intel Corp. 82557 [Ethernet Pro 100] (#2) (rev 8).
      IRQ 10.
      Master Capable.  Latency=64.  Min Gnt=8.Max Lat=56.
      Non-prefetchable 32 bit memory at 0xc4dfd000 [0xc4dfdfff].
      I/O at 0x2c00 [0x2c3f].
      Non-prefetchable 32 bit memory at 0xc4c00000 [0xc4cfffff].

Regards,

Anuradha

-- 

Debian GNU/Linux (kernel 2.4.16)

First Law of Bicycling:
	No matter which way you ride, it's uphill and against the wind.


  reply	other threads:[~2001-11-30  5:46 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 [this message]
2001-11-30  5:57       ` David Rees
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=20011130114506.A4789@bee.lk \
    --to=anuradha@gnu.org \
    --cc=jjs@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=poznick@conwaycorp.net \
    --cc=sven@research.nj.nec.com \
    /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.