Linux wireless drivers development
 help / color / mirror / Atom feed
From: "rossi.f@inwind.it" <rossi.f@inwind.it>
To: <yogeshp@marvell.com>,
	"johannes@sipsolutions.net" <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: WARNING: at net/mac80211/wep.c:101 ieee80211_wep_add_iv+0x52/0x150 [mac80211]()
Date: Tue, 3 May 2011 13:27:12 +0200 (CEST)	[thread overview]
Message-ID: <570950.1322951304422032629.JavaMail.defaultUser@defaultHost> (raw)

>Da: yogeshp@marvell.com
>Data: 03/05/2011 12.51
>A: "rossi.f@inwind.it"<rossi.f@inwind.it>, "johannes@sipsolutions.net"
<johannes@sipsolutions.net>
>Cc: "linux-wireless@vger.kernel.org"<linux-wireless@vger.kernel.org>
>Ogg: RE: WARNING: at net/mac80211/wep.c:101 ieee80211_wep_add_iv+0x52/0x150 
[mac80211]()
>
>>I get the warning every few seconds.
>>
>>Fabio
>I failed to regenerate the issue on my setup. I am using WEP40 on
>Ath5k as station on 32 bit machine. I even tried disabling hw encryption.
>
>Some more details would be helpful.
>
>Thanks
>Yogesh

I'm using WEP with 128bit key on a 64bit system using ath5k driver. The hw 
encryption is configured with the default value. I don't have access right now 
to the machine, I can provide more details tonight if needed. I can test 
patches to diagnose the problem.

Regards,
Fabio



             reply	other threads:[~2011-05-03 11:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-03 11:27 rossi.f [this message]
2011-05-03 11:44 ` WARNING: at net/mac80211/wep.c:101 ieee80211_wep_add_iv+0x52/0x150 [mac80211]() Mohammed Shafi
2011-05-03 14:25   ` Yogesh Powar
2011-05-03 14:28     ` Johannes Berg
2011-05-03 15:18       ` Mohammed Shafi
  -- strict thread matches above, loose matches on Subject: below --
2011-05-03 10:02 rossi.f
2011-05-03 10:51 ` Yogesh Powar
2011-05-02 20:57 Fabio Rossi
2011-05-03  8:31 ` Johannes Berg

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=570950.1322951304422032629.JavaMail.defaultUser@defaultHost \
    --to=rossi.f@inwind.it \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=yogeshp@marvell.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