From: Sven Heinicke <sven@research.nj.nec.com>
To: Anuradha Ratnaweera <anuradha@gnu.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.16 freezed up with eepro100 module
Date: Fri, 30 Nov 2001 11:04:29 -0500 (EST) [thread overview]
Message-ID: <15367.44557.930845.66428@abasin.nj.nec.com> (raw)
In-Reply-To: <20011130114506.A4789@bee.lk>
In-Reply-To: <15366.21354.879039.718967@abasin.nj.nec.com> <20011129095107.A17457@conwaycorp.net> <3C070FEC.3602CB49@pobox.com> <20011130114506.A4789@bee.lk>
I have eepro100's on other systems and never had a problem. They
never have been made to work as hard as the DELLs though. I am
trying the same DELL with a 3C996-T 1000Bt card using the driver from
3COM (we plan on moving that system to a 1000Bt system but the switch
hasn't arrived yet) and it is running at 100Bt with the same
software. If you don't hear form me assume it surrived. Been up a
day so far, took the DELL like 3 days of heavy use to crash before.
Sven
> 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.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-11-30 16:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-29 15:25 Sven Heinicke
2001-11-29 15:51 ` Nathan Poznick
2001-11-30 4:49 ` J Sloan
2001-11-30 5:45 ` Anuradha Ratnaweera
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 [this message]
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
2001-11-29 16:14 ` Sven Heinicke
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=15367.44557.930845.66428@abasin.nj.nec.com \
--to=sven@research.nj.nec.com \
--cc=anuradha@gnu.org \
--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
all inboxes | Powered by JetHome®