From: "Miles Lane" <miles.lane@gmail.com>
To: "Andrew Morton" <akpm@osdl.org>
Cc: netdev@vger.kernel.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 17:53:10 -0700 [thread overview]
Message-ID: <a44ae5cd0609261753t311a7952w2a98434c093ef1c@mail.gmail.com> (raw)
In-Reply-To: <20060926124310.17797fe5.akpm@osdl.org>
On 9/26/06, Andrew Morton <akpm@osdl.org> wrote:
>
> [added netdev]
>
> On Tue, 26 Sep 2006 12:04:40 -0700
> "Miles Lane" <miles.lane@gmail.com> wrote:
>
> > 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.
> >
> > >From dmesg output:
> > ieee80211: 802.11 data/management/control stack, git-1.1.13
> > ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
> > ieee80211_crypt: registered algorithm 'NULL'
> > ieee80211_crypt: registered algorithm 'WEP'
> > ieee80211_crypt: registered algorithm 'CCMP'
> > ieee80211_crypt: registered algorithm 'TKIP'
>
> I suspect that whatever caused this is now in mainline. Are you able to
> test Linus's current git tree?
Sorry, I don't have oodles of disk space free to hold all the git
historical information (iirc, it's huge). I could conceivably put it
together, but I'd been some help and time. I am currently travelling,
but I do have my kernel test laptop with me. Also, I am currently
staying in a building running off of solar power, so I need to be a
bit careful with power consumption. I'll be in a place with AC power
in five days. Lastly, I don't know how I triggered the problem. I am
happy to try to reproduce it for you, though.
Miles
next prev parent reply other threads:[~2006-09-27 0:53 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 [this message]
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
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=a44ae5cd0609261753t311a7952w2a98434c093ef1c@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 \
--cc=netdev@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®