From: "D.J. Barrow" <barrow_dj@yahoo.com>
To: Chris Leishman <masklin@debian.org>,
Rod Stewart <stewart@lab43.org>,
linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Cc: Chris Leishman <masklin@debian.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Airport debug (was Re: airport woes?)
Date: Mon, 6 Nov 2000 07:37:22 -0800 (PST) [thread overview]
Message-ID: <20001106153722.12662.qmail@web219.mail.yahoo.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1410 bytes --]
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.
--- Chris Leishman <masklin@debian.org> wrote:
>
> On Thu, Nov 02, 2000 at 03:15:58PM -0500, Rod
> Stewart wrote:
> <snip>
> >
> > Anyone know if this is fixed, or a work around?
> I've got the same setup,
> > with the same problem. My ssh connections over
> airport freeze.
> >
> > Thanks,
> > -Rms
>
> No idea yet - but I'm not all the familiar with
> device drivers, etc, yet.
>
> I do know that the airport_tx method stops getting
> called when the lock-up
> occurs. Why it doesn't get called I don't know.
>
> Regards,
>
> Chris
>
>
> --
>
----------------------------------------------------------------------
> Knuth: premature optimization is the root of
> all evil.
>
----------------------------------------------------------------------
> Reply with subject 'request key' for GPG public key.
> KeyID 0xB4E24219
>
>
=====
D.J. Barrow Linux for S/390 kernel developer
eMail: djbarrow@de.ibm.com,barrow_dj@yahoo.com
Phone: +49-(0)7031-16-2583
IBM Germany Lab, Schönaicherstr. 220, 71032 Böblingen
Thousands of Stores. Millions of Products. All in one Place.
http://shopping.yahoo.com/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-11-06 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-06 15:37 D.J. Barrow [this message]
2000-11-08 12:02 ` Airport debug (was Re: airport woes?) Chris Leishman
-- 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=20001106153722.12662.qmail@web219.mail.yahoo.com \
--to=barrow_dj@yahoo.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=masklin@debian.org \
--cc=stewart@lab43.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).