linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Joseph Garcia <jpgarcia@execpc.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Problems with Ethernet on PowerBook Wallstreet G3
Date: Wed, 12 Apr 2000 13:10:02 -0500	[thread overview]
Message-ID: <38F4BBFA.B3CE8273@execpc.com> (raw)
In-Reply-To: Pine.LNX.3.96.1000412105423.25261A-100000@deepspace.mklinux.org


Here's my observations on whats happening with my system (PDQ/300):

Any out-going FTP transfer maxes around 100K/s, and has potential to corrupt.
NFS, atalk, etc seem to be ok.  Incoming transfers also seem to be ok.  By
outgoing, I do mean out going.  Whether its with a server (wu or pro), or a
client, if the file originates from my powerbook, it has this common problem.

During the time of transfer, the collision light on the hub blares.  I have
tried this with a normal hub and a switch.  As far as I can tell, this would
mean it is colliding with itself.  How else could a switched hub get collisions
this prevalent?

Initially, I was thinking that this is a bug brought on by the BMAC+, a
sibling/upgrade to the BMAC that can do 100BT and full duplex.  I looked at the
driver, and one wait value was changed from a few hundred ms (early 2.2.x) to 10
ms.  I tried switching it back, but there was no change.  so its not that.
Anything else that could be causing it?  I don't remember this problem with
earlier 2.2 kernels.  Anyone confirm this?  2.1.x maybe?

I severly doubt it is a pure TCP problem, because ftp using the lo device
regards high return.  The only possible cause is the BMAC driver IMO.  But how
would it only effect FTP outgoing?  I've heard that FTP uses raw bandwidth, so
does that mean it uses some low level handshaking that nothing else uses, and
depends on the file's host?   So where do FTP-out and BMAC collide in such a way
that it doesnt affect lo, nor incoming files?

Sorry if I'm ranting.

Is this info any help?

--
Joseph P. Garcia      jpgarcia@execpc.com      jpgarcia@lidar.ssec.wisc.edu
CS Undergraduate                      Student Employee - Systems Programmer
University of Wisconsin - Madison                            UW Lidar Group

"Did you ever notice how the Chinese Abacus, with 2 '5' beads and 5 '1'
beads, is perfect for hexidecimal math?"

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

       reply	other threads:[~2000-04-12 18:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.3.96.1000412105423.25261A-100000@deepspace.mklinux.org>
2000-04-12 18:10 ` Joseph Garcia [this message]
2000-04-12 18:55   ` Problems with Ethernet on PowerBook Wallstreet G3 David A. Gatwood
2000-04-12 22:18   ` Wolfgang Denk
2000-04-12 18:25 ` Benjamin Herrenschmidt
2000-04-12 20:06   ` Michael Schmitz
     [not found] <38F5A91D.1212ECEC@drea.dnd.ca>
2000-04-13 12:23 ` Wolfgang Denk
     [not found] <Pine.LNX.4.10.10004130948140.10131-100000@opal.biophys.uni-duesseldorf.de>
2000-04-13  9:39 ` Wolfgang Denk
     [not found]   ` <38F5B1C0.FC8863EB@drea.dnd.ca>
2000-04-13 12:57     ` Joseph Garcia
2000-04-13 13:59       ` Benjamin Herrenschmidt
2000-04-13 16:47       ` David A. Gatwood
2000-04-12 22:45 Wolfgang Denk
     [not found] <Pine.LNX.3.96.1000411215343.219D-100000@deepspace.mklinux.org>
2000-04-12 12:44 ` Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2000-04-11 18:22 Wolfgang Denk

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=38F4BBFA.B3CE8273@execpc.com \
    --to=jpgarcia@execpc.com \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).