lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 20 Oct 2006 10:57:21 +0800 From: Zhu Yi <yi.zhu@...el.com> To: Andrew Morton <akpm@...l.org> Cc: Jiri Slaby <jirislaby@...il.com>, Linux kernel mailing list <linux-kernel@...r.kernel.org>, ipw2100-admin@...ux.intel.com, "John W. Linville" <linville@...driver.com> Subject: Re: ipw2200: "ieee80211: Info elem: parse failed" On Thu, 2006-10-19 at 19:23 -0700, Andrew Morton wrote: > On Thu, 19 Oct 2006 11:17:34 +0200 > Jiri Slaby <jirislaby@...il.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 - 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