public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Chris Leishman <masklin@debian•org>
To: "D.J. Barrow" <barrow_dj@yahoo•com>
Cc: Chris Leishman <masklin@debian•org>,
	Rod Stewart <stewart@lab43•org>,
	linuxppc-dev <linuxppc-dev@lists•linuxppc.org>
Subject: Re: Airport debug (was Re: airport woes?)
Date: Wed, 8 Nov 2000 23:02:30 +1100	[thread overview]
Message-ID: <20001108230230.A4113@nina.dev.fol> (raw)
In-Reply-To: <20001106153722.12662.qmail@web219.mail.yahoo.com>; from barrow_dj@yahoo.com on Mon, Nov 06, 2000 at 07:37:22AM -0800


On Mon, Nov 06, 2000 at 07:37:22AM -0800, D.J. Barrow wrote:
>
> Hi,
> I don't have an Airport but am familiar with
> programming linux network device drivers.
>
> This symtom sounds like a it could be a classic tbusy
> (transmit busy ) getting  stuck on in the driver in
> the network device structure.
>

Actually - I don't think this is the problem, since it only locks up the send
_for the single TCP connection_.  Other TCP connections, or new ones, work
fine.

It is interesting that I only ever get the problem when accessing distant
systems (where the link is slower and less reliable) - and then it happens
very consistantly.

Chris

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

  reply	other threads:[~2000-11-08 12:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-06 15:37 Airport debug (was Re: airport woes?) D.J. Barrow
2000-11-08 12:02 ` Chris Leishman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-11-06  7:38 Chris Leishman

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=20001108230230.A4113@nina.dev.fol \
    --to=masklin@debian$(echo .)org \
    --cc=barrow_dj@yahoo$(echo .)com \
    --cc=linuxppc-dev@lists$(echo .)linuxppc.org \
    --cc=stewart@lab43$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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