[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a44ae5cd0609262305p1d0b9aaai9db324aff0b3ba0c@mail.gmail.com>
Date: Tue, 26 Sep 2006 23:05:44 -0700
From: "Miles Lane" <miles.lane@...il.com>
To: "Andrew Morton" <akpm@...l.org>,
LKML <linux-kernel@...r.kernel.org>,
"Jouni Malinen" <jkmaline@...hut.fi>,
"James P. Ketrenos" <ipw2100-admin@...ux.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.
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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists