From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: John Jasen <jjasen@datafoundation.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: a couple of NICs that don't NIC
Date: Fri, 29 Jun 2001 14:55:04 -0400 [thread overview]
Message-ID: <3B3CCF08.3E2E6AA8@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0106291223560.9716-100000@flash.datafoundation.com>
John Jasen wrote:
> kernels: 2.4.4
>
> drivers used: kernel 8139too
>
> symptoms: the system would hang under heavy network traffic, and need to
> be powercycled backed to life.
fixed in 2.4.6-pre6
--
Jeff Garzik | Andre the Giant has a posse.
Building 1024 |
MandrakeSoft |
prev parent reply other threads:[~2001-06-29 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 16:32 a couple of NICs that don't NIC John Jasen
2001-06-29 18:55 ` Jeff Garzik [this message]
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=3B3CCF08.3E2E6AA8@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=jjasen@datafoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox