From: Zhu Yi <yi.zhu@intel.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Jiri Slaby <jirislaby@gmail.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
ipw2100-admin@linux.intel.com,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: ipw2200: "ieee80211: Info elem: parse failed"
Date: Fri, 20 Oct 2006 10:57:21 +0800 [thread overview]
Message-ID: <1161313041.19188.23.camel@debian.sh.intel.com> (raw)
In-Reply-To: <20061019192350.13209920.akpm@osdl.org>
On Thu, 2006-10-19 at 19:23 -0700, Andrew Morton wrote:
> On Thu, 19 Oct 2006 11:17:34 +0200
> Jiri Slaby <jirislaby@gmail.com> wrote:
>
> > Hi,
> >
> > since 2.6.19-rc1 I'm getting these messages from ipw2200 driver:
> > ieee80211: Info elem: parse failed: info_element->len + 2 > left :
> > info_element->len+2=8 left=2, id=128.
> >
> > The driver says:
> > ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.1.4km
> > ipw2200: Copyright(c) 2003-2006 Intel Corporation
> > ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 3
> > PCI: setting IRQ 3 as level-triggered
> > ACPI: PCI Interrupt 0000:02:07.0[A] -> Link [LNKC] -> GSI 3 (level, low) -> IRQ 3
> > ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
> > ACPI: PCI Interrupt 0000:00:13.2[A] -> Link [LNKD] -> GSI 10 (level, low) -> IRQ 10
> >
> > and works, but the message is annoying, since the driver prints it again and
> > again. What could be wrong?
> >
>
> I suspect it was always failing. But the failure message has been changed
> so that it actually comes out.
This was already addressed by
http://marc.theaimsgroup.com/?l=linux-netdev&m=116119388014674&w=2
Thanks,
-yi
prev parent reply other threads:[~2006-10-20 2:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 9:17 ipw2200: "ieee80211: Info elem: parse failed" Jiri Slaby
2006-10-20 2:23 ` Andrew Morton
2006-10-20 2:57 ` Zhu Yi [this message]
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=1161313041.19188.23.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=akpm@osdl.org \
--cc=ipw2100-admin@linux.intel.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.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