Re: 2.6.18-mm1 -- ieee80211: Info elem: parse failed: info_element->len + 2 > left : info_element->len+2=28 left=9, id=221.

[Miles Lane]

On 9/26/06, Andrew Morton <akpm@xxxxxxxx> wrote:
> [added netdev]
>
> On Tue, 26 Sep 2006 12:04:40 -0700
> "Miles Lane" <miles.lane@xxxxxxxxx> 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@xxxxxxxxxxxxxxx>
> > 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/