From: Nathan Poznick <poznick@conwaycorp.net>
To: Sven Heinicke <sven@research.nj.nec.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.16 freezed up with eepro100 module
Date: Thu, 29 Nov 2001 09:51:07 -0600 [thread overview]
Message-ID: <20011129095107.A17457@conwaycorp.net> (raw)
In-Reply-To: <15366.21354.879039.718967@abasin.nj.nec.com>
In-Reply-To: <15366.21354.879039.718967@abasin.nj.nec.com>
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
me it didn't lock up the entire machine however, it only seemed to
kill the network - I was able to reboot the machine cleanly once I got
to the console. (message from yesterday with the subject 'failed
assertion in tcp.c') I too, am open to suggestions :-)
--
Nathan Poznick <poznick@conwaycorp.net>
PGP Key: http://drunkmonkey.org/pgpkey.txt
Curiosity has its own reason for existing.
-- Albert Einstein
next prev parent reply other threads:[~2001-11-29 15:51 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 [this message]
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
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=20011129095107.A17457@conwaycorp.net \
--to=poznick@conwaycorp.net \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).