Bug 1379 - iwl4965: REPLY_ADD_STA failed
: iwl4965: REPLY_ADD_STA failed
Status: VERIFIED FIXED
: iwlwifi
WPA & WPA2
: 0.0.38
: IBM Debian
: P2 critical
Assigned To:
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2007-07-15 06:57 by
Modified: 2007-12-29 02:41 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2007-07-15 06:57:31
Linux 2.6.22, from kernel.org.

Lenovo 3000 V200.

Network running secured, PSK.

Jul 15 10:48:04 v200 -- MARK --
Jul 15 10:50:56 v200 kernel: wlan0: RX deauthentication from 00:11:6b:25:af:76
(reason=6)
Jul 15 10:50:56 v200 kernel: wlan0: deauthenticated
Jul 15 10:50:56 v200 kernel: wlan0: RX deauthentication from 00:11:6b:25:af:76
(reason=6)
Jul 15 10:50:57 v200 kernel: wlan0: authenticate with AP 00:11:6b:25:af:76
Jul 15 10:50:58 v200 last message repeated 2 times
Jul 15 10:50:58 v200 kernel: wlan0: authentication with AP 00:11:6b:25:af:76
timed out
Jul 15 10:51:00 v200 kernel: iwl4965: REPLY_ADD_STA failed
Jul 15 10:51:30 v200 last message repeated 4 times
Jul 15 10:52:29 v200 last message repeated 8 times
Jul 15 10:53:28 v200 last message repeated 8 times

And then many many more, and no connectivity.
------- Comment #1 From 2007-07-20 20:18:13 -------
Sam, I seem to have same problem. Could you check at network frequency? Check if
the value is greater than 2.422 GHZ (or very close to this value) and if so,
check bug http://bughost.org/bugzilla/show_bug.cgi?id=1390 because I have no
network connectivity with any net on this freq and my messages are very similar
to yours.
------- Comment #2 From 2007-07-22 08:17:13 -------
I can confirm that the issues are related, or more precisely, that when I
switched from "channel 11" to "channel 4" (Level1 router) the problem seems to
go away, at least for 30 hrs.
------- Comment #3 From 2007-07-22 08:17:54 -------
*** Bug 1390 has been marked as a duplicate of this bug. ***
------- Comment #4 From 2007-07-22 11:07:31 -------
So it is definitely related to certain high frequencies, but as it is not 100%
reproducible (for example I am working right now at channel11 wich before I
couldn't connect with same config), how could we deal with this, any temporal
workarround?
------- Comment #5 From 2007-07-22 19:47:48 -------
I'm not quite understood. 

Channel 03 : 2.422 GHz
Channel 04 : 2.427 GHz
Channel 11 : 2.462 GHz

You said you had problems with frequencies more than 2.422. But you also said it
works if you switched from channel 11 to channel 4?
------- Comment #6 From 2007-07-24 18:53:22 -------
(In reply to comment #5)
> I'm not quite understood. 
> 
> Channel 03 : 2.422 GHz
> Channel 04 : 2.427 GHz
> Channel 11 : 2.462 GHz
> 
> You said you had problems with frequencies more than 2.422. But you also said it
> works if you switched from channel 11 to channel 4?

I don't understand it either besides the fact that I am also affected.
Sometimes, I can think that it is frequency related and sometimes it works
again. I am 3 days now in channel 11 in my house (2.464GHZ) without any issue
where I had issues before (??!!), but it only works in my house with a signal
quality of >50% (according to NetworkManager), anyway I have a lot of troubles
if I have a signal below 30% (isn't 30% enough?) and depending of frequency.

But in any case, I always have those iwl4965: REPLY_ADD_STA failed all the time
(in a successful connection and in a unsuccessful connection).

Tell me what to do, what to try.. and I'll try it because I can't give credit to
this estrange behavior.
------- Comment #7 From 2007-08-08 16:59:16 -------
I have other comment:

Today I saw something really strange! And it is according to the behavior I've
seen in my own machine.

I saw it in a friend's laptop with a iwl3945 and windows XP, so I think the
problem is not only in Linux' driver.

It connects to an unprotected wireless (almost 100% of power, because we were
close enough from AP) and it connects. For a while, you can use the internet,
but after certain amount of time, it gets stucked, it remains connected, but
cannot ping anymore, cannot send/receive data, etc.

A disconnect and reconnect does not solve this problem, because even if it
reconnects again, it can't send/receive any data.

So this is another hardware (I think 3945 is related to 4965 as they share
almost same code when possible), and this is a windows driver, so, if the
behaviour is almost identical, ¿maybe problem is in firmware?

On the other hand, I red that there are some restrictions in frequency in order
to not to interfere radars, etc. Wich restrictions are applied to Spain for
example? Maybe those restrictions are too restrictive and thus, make very
difficult to connect in certain situations?

There are many reports of this weird behavior.. any possible cause?
------- Comment #8 From 2007-08-13 01:04:30 -------
because we didn't meet the same problem, could you please try 0.1.8?
------- Comment #9 From 2007-08-17 00:12:36 -------
fixed in 0.1.8
------- Comment #10 From 2007-12-28 23:12:09 -------
we didn't meet with such problem with iwlwifi-1.2.23 and Linux 2.6.23,u may 
try this version, if it's fixed, then verify it.
------- Comment #11 From 2007-12-29 02:41:16 -------
This thing has been gone for a while. I am using the latest+latest kernel, but
its been from at least 2.6.22 that it's gone.