From: "Miles Lane" <miles.lane@gmail.com>
To: "Andrew Morton" <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
"Jouni Malinen" <jkmaline@cc.hut.fi>,
"James P. Ketrenos" <ipw2100-admin@linux.intel.com>
Subject: Re: 2.6.18-mm1 -- ieee80211: Info elem: parse failed: info_element->len + 2 > left : info_element->len+2=28 left=9, id=221.
Date: Tue, 26 Sep 2006 23:05:44 -0700 [thread overview]
Message-ID: <a44ae5cd0609262305p1d0b9aaai9db324aff0b3ba0c@mail.gmail.com> (raw)
In-Reply-To: <a44ae5cd0609261756w1e82087p60c18ef941657466@mail.gmail.com>
It occurs to me that these messages occured while I was connected to a
public WIFI AP at the airport in Phoenix. It may be that the network
configuration or my distance from the AP had a part to play in the
messages being triggered. If so, I may have trouble reproducing the
problem. I'll be interested to hear from some of the IEEE80211
developers on what these messages indicate.
ieee80211: Info elem: parse failed: info_element->len + 2 > left :
info_element->len+2=28 left=9, id=221.
ieee80211: Info elem: parse failed: info_element->len + 2 > left :
info_element->len+2=28 left=9, id=221.
ieee80211: Info elem: parse failed: info_element->len + 2 > left :
info_element->len+2=28 left=9, id=221.
next prev parent reply other threads:[~2006-09-27 6:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 19:04 Miles Lane
2006-09-26 19:43 ` Andrew Morton
2006-09-27 0:53 ` Miles Lane
2006-09-28 0:24 ` Jesper Juhl
2006-09-28 5:02 ` Miles Lane
2006-09-27 0:56 ` Miles Lane
2006-09-27 6:05 ` Miles Lane [this message]
2006-09-27 20:47 ` James Ketrenos
2006-09-27 20:18 ` Andrew Morton
2006-09-27 22:58 ` James Ketrenos
2006-09-27 23:02 ` Andrew Morton
2006-09-28 0:15 ` Denis Vlasenko
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=a44ae5cd0609262305p1d0b9aaai9db324aff0b3ba0c@mail.gmail.com \
--to=miles.lane@gmail.com \
--cc=akpm@osdl.org \
--cc=ipw2100-admin@linux.intel.com \
--cc=jkmaline@cc.hut.fi \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®