From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>, Kacper <kacper@kacper.se>,
linux-wireless@vger.kernel.org
Subject: Re: ath5k phy0: unsupported jumbo
Date: Mon, 25 Jan 2010 10:25:09 -0800 [thread overview]
Message-ID: <43e72e891001251025s1e3fa358v31527d1b5f7e3436@mail.gmail.com> (raw)
In-Reply-To: <b6c5339f1001231032r155b380av93563a6febeeae2b@mail.gmail.com>
On Sat, Jan 23, 2010 at 10:32 AM, Bob Copeland <me@bobcopeland.com> wrote:
> On Sat, Jan 23, 2010 at 8:40 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>> So it looks like we receive some strange packets that haven’t been
>> explained yet. It might be worth looking at a few --- sounds kind of
>> interesting.
>>
>> Am I understanding correctly? This is a hardware bug or undocumented
>> hardware feature then, right?
>>
>> It might be nice to add some user-oriented explanation too, but for
>> now, how about this comment?
>>
>
> That's ok with me. I'd also be fine with removing the log spam. I think
> ultimately it represents some kind of driver issue, I'm just not sure what,
> exactly, yet. I recently added more debugging to a kernel on a system of
> mine that produces it more often -- I'll see what it turns up.
Jumbo frames are frames which the hardware receives for which it does
not have enough DMA leg room for, and so needs to split it out into
multiple descriptors. It should be OK to just drop them if ath5k is
setting the max RX dma size to the max 802.11 frame, as they could be
bogus frames or 11n AMSDU frames which ath5k obviously would not
support.
Luis
next prev parent reply other threads:[~2010-01-25 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 10:51 ath5k phy0: unsupported jumbo Jonathan Nieder
2010-01-23 12:18 ` Kacper
2010-01-23 13:40 ` Jonathan Nieder
2010-01-23 18:32 ` Bob Copeland
2010-01-25 18:25 ` Luis R. Rodriguez [this message]
2010-07-26 7:06 ` Vladimir Linevich
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=43e72e891001251025s1e3fa358v31527d1b5f7e3436@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=jrnieder@gmail.com \
--cc=kacper@kacper.se \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
/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).