From: Mihai Moldovan <ionic@ionic.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Zhu Yi <yi.zhu@intel.com>,
James Ketrenos <jketreno@linux.intel.com>,
Reinette Chatre <reinette.chatre@intel.com>,
linux-wireless@vger.kernel.org
Subject: Firmware errors with ipw2200 when connected to an WPA-enabled AP
Date: Fri, 26 Dec 2008 03:39:34 +0100 [thread overview]
Message-ID: <495443E6.404@ionic.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2259 bytes --]
Hello,
I am seeing some really weird behavior with my IPW2200 card.
I am connected to an AP (multiple Atheros cards with hostapd) and
WPA-PSK with CCMP encryption.
When the connection is fully idle, I do see those messages coming up
pretty randomly:
[41715.420882] ipw2200: Firmware error detected. Restarting.
The card is then resetting itself, the connection is dropped for some
milliseconds, but all in all no harm is done.
Another situation happens when the card is on full load:
[38659.056980] __ratelimit: 21 callbacks suppressed
[38659.056985] CCMP: decrypt failed: STA=00:22:b0:bc:1e:2e
[38659.057638] CCMP: decrypt failed: STA=00:22:b0:bc:1e:2e
[38659.058005] CCMP: decrypt failed: STA=00:22:b0:bc:1e:2e
[38659.058356] CCMP: decrypt failed: STA=00:22:b0:bc:1e:2e
[38659.059127] CCMP: decrypt failed: STA=00:22:b0:bc:1e:2e
[38659.059637] CCMP: decrypt failed: STA=00:22:b0:bc:1e:2e
[38659.060123] CCMP: decrypt failed: STA=00:22:b0:bc:1e:2e
[38659.060671] CCMP: decrypt failed: STA=00:22:b0:bc:1e:2e
[38659.061046] CCMP: decrypt failed: STA=00:22:b0:bc:1e:2e
[38659.061641] CCMP: decrypt failed: STA=00:22:b0:bc:1e:2e
Those messages are repeated from time to time. The connection itself is
not being dropped, and netcat itself doesn't stop either, but for some
seconds, no packets are going through the WiFi link.
So, I am really curious about this, although not being fatal in itself,
the errors are pretty annoying.
I've added the respective Devs to the CC list, I hope this is OK.
One more sidenote though: I've been running IPW2200 for several years
with WEP and haven't experienced those errors yet, at least not in this
quantity. The card used to reset sometimes due to "firmware errors", but
please read "sometimes" as "every two weeks once."
Another little question: will the card be supported by the new
iwlwifi/iwlcore/iwlagn drivers anytime soon, or will the "old" ipw2200
driver be the only one for this card? Someone really should update the
documentation, at least in the kernel build system regarding this,
currently "There is no help available." :)
Please let me know if you need any more information, I will hand it to
you ASAP.
Best regards,
Mihai Moldovan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 898 bytes --]
next reply other threads:[~2008-12-26 2:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-26 2:39 Mihai Moldovan [this message]
2008-12-26 3:05 ` Firmware errors with ipw2200 when connected to an WPA-enabled AP Zhu Yi
2008-12-26 12:56 ` Mihai Moldovan
2008-12-29 1:33 ` Zhu Yi
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=495443E6.404@ionic.de \
--to=ionic@ionic.de \
--cc=jketreno@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=yi.zhu@intel.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;
as well as URLs for NNTP newsgroup(s).