From: Stephan von Krawczynski <skraw@ithnet.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM REPORT 2.4.20-rc1: sundance.c
Date: Sat, 2 Nov 2002 15:54:31 +0100 [thread overview]
Message-ID: <20021102155431.7a01ed55.skraw@ithnet.com> (raw)
In-Reply-To: <3DC19ACA.9030906@pobox.com>
On Thu, 31 Oct 2002 16:04:10 -0500
Jeff Garzik <jgarzik@pobox.com> wrote:
> Stephan von Krawczynski wrote:
>
> >Hello all,
> >
> >I'd like to point out that (at least) the network driver sundance.c has
> >weird flaws when trying to use more than MAX_UNITS (8) cards at the same
> >time. Since
> >
>
> Smileys nonwithstanding, you need to include far more information
>
> Please define "weird flaws"... explicitly.
I am experiencing dropped packets as sundance RX side when simple nfs copying
takes places. These are at a rate of about 1-2% of RX packets. I call it
"weird" because I cannot see a definitive problem location in the driver
source. fact stays one simple copy drops packets, something I never saw in the
same setup (same cabling, same mainboard) with tulip cards.
I know that this is a hell of a "bug-report", but I really want to point out
only a strange difference between tulip-setup and sundance-setup.
--
Regards,
Stephan
prev parent reply other threads:[~2002-11-02 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 16:38 PROBLEM REPORT 2.4.20-rc1: sundance.c Stephan von Krawczynski
2002-10-31 17:30 ` PROBLEM REPORT 2.4.20-rc1: sundance.c (OT: userspace) Stephan von Krawczynski
2002-10-31 21:04 ` PROBLEM REPORT 2.4.20-rc1: sundance.c Jeff Garzik
2002-11-02 14:54 ` Stephan von Krawczynski [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=20021102155431.7a01ed55.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=jgarzik@pobox.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 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.