From: Michael Buesch <mb@bu3sch.de>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Bob Copeland <me@bobcopeland.com>,
Jiri Slaby <jirislaby@gmail.com>,
Nick Kossifidis <mickflemm@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Ath5k on 2.6.32 suddenly fails
Date: Thu, 21 Jan 2010 13:05:28 +0100 [thread overview]
Message-ID: <201001211305.28456.mb@bu3sch.de> (raw)
In-Reply-To: <201001152350.06930.mb@bu3sch.de>
So so AP failed again.
This time with an older failure that I already reported in the past.
[92588.864887] ath5k phy0: unsupported jumbo
[92860.064977] ath5k phy0: unsupported jumbo
[93019.724035] ath5k phy0: unsupported jumbo
[93444.334305] ath5k phy0: unsupported jumbo
[161109.006052] ath5k phy0: unsupported jumbo
[186430.369739] ath5k phy0: unsupported jumbo
[210174.502973] ath5k phy0: no further txbuf available, dropping packet
[210175.527224] ath5k phy0: no further txbuf available, dropping packet
[210176.551473] ath5k phy0: no further txbuf available, dropping packet
...
Note that the "unsupported jumbo" messages seem to be harmless.
It fails, if these "dropping packet" messages appear.
Here's a wireshark log of the WM while I was trying to connect to
the AP with a device:
http://bu3sch.de/misc/quimbyfail
So it still beacons, but otherwise is completely dead.
--
Greetings, Michael.
next prev parent reply other threads:[~2010-01-21 12:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 10:52 Ath5k on 2.6.32 suddenly fails Michael Buesch
2010-01-11 16:11 ` Luis R. Rodriguez
2010-01-11 16:35 ` Larry Finger
2010-01-11 16:43 ` Luis R. Rodriguez
2010-01-11 22:36 ` Michael Buesch
2010-01-15 22:29 ` Michael Buesch
2010-01-15 22:40 ` Michael Buesch
2010-01-15 22:47 ` Luis R. Rodriguez
2010-01-15 22:50 ` Michael Buesch
2010-01-21 12:05 ` Michael Buesch [this message]
2010-01-21 15:57 ` Bob Copeland
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=201001211305.28456.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=me@bobcopeland.com \
--cc=mickflemm@gmail.com \
--cc=rjw@sisk.pl \
/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.