public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Joe Rice <jrice@bigidea.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Still having problems with eepro100
Date: Fri, 30 Nov 2001 17:07:15 -0800	[thread overview]
Message-ID: <20011130170715.K504@mikef-linux.matchmail.com> (raw)
In-Reply-To: <20011130180827.E2265@bigidea.com> <20011130163721.J504@mikef-linux.matchmail.com> <20011130184916.A13868@bigidea.com>
In-Reply-To: <20011130184916.A13868@bigidea.com>

On Fri, Nov 30, 2001 at 06:49:16PM -0600, Joe Rice wrote:
> i guess that explains why i haven't seen the problem again
> on the bed of machines with 2.4.16.  
> Could please explain how you came to your answer?
> maybe this is to obvious to be addressed on the list, but
> please give me a clue.
> 

IIRC the triggers are:
older kernel ( <= 2.4.9)
nfs w/ 1024 byte packets (default) better usually is 8192
lots of network traffic

  reply	other threads:[~2001-12-01  1:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-01  0:08 Still having problems with eepro100 Joe Rice
2001-12-01  0:37 ` Mike Fedyk
2001-12-01  0:49   ` Joe Rice
2001-12-01  1:07     ` Mike Fedyk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-30 11:39 Johan
2001-10-30 11:57 ` Thomas Langås
2001-10-30 12:05   ` Johan
2001-10-30 12:58     ` Kirill Ratkin
2001-10-30 20:19   ` Kurt Roeckx
2001-10-30 12:09 ` Alan Cox
2001-10-30 12:20   ` Rafael Martinez
2001-10-30 16:23 ` Lee Packham
2001-10-30 16:51   ` Kirill Ratkin
2001-10-30 17:07 ` Alex Bligh - linux-kernel
2001-10-31 14:40   ` Alex Bligh - linux-kernel
2001-11-01 11:15 ` Andrey Savochkin
2001-11-01 11:33   ` Jeff Garzik

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=20011130170715.K504@mikef-linux.matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=jrice@bigidea.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