[Gutsy] wpa_supplicant "freezes" few seconds connection on iwl4965

[slamdunk]

Binary package hint: wpasupplicant

Hardware: Dell XPS M1330
System: Gutsy Tribe 5

this bug-report is born from : https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/133395

My system has Intel-N wireless and module loaded is "iwl4965".

When I download a file via http or ftp or loading a page in internet, download hiccuping every 600/700Kb, it seems stopped and after 2/3 seconds it restarts.

From my kern.log:

Sep 2 10:20:36 mybox kernel: [ 158.316000] iwl4965: REPLY_ADD_STA failed
Sep 2 10:20:43 mybox kernel: [ 165.572000] iwl4965: REPLY_ADD_STA failed
Sep 2 10:20:50 mybox kernel: [ 172.728000] iwl4965: REPLY_ADD_STA failed
Sep 2 10:20:57 mybox kernel: [ 179.876000] iwl4965: REPLY_ADD_STA failed
Sep 2 10:21:05 mybox kernel: [ 187.032000] iwl4965: REPLY_ADD_STA failed
Sep 2 10:21:12 mybox kernel: [ 194.104000] iwl4965: REPLY_ADD_STA failed
Sep 2 10:21:19 mybox kernel: [ 201.252000] iwl4965: REPLY_ADD_STA failed
Sep 2 10:21:26 mybox kernel: [ 208.400000] iwl4965: REPLY_ADD_STA failed
Sep 2 10:23:18 mybox kernel: [ 320.376000] set_level status: 0
Sep 2 10:23:18 mybox kernel: [ 320.396000] set_level status: 0
Sep 2 10:23:18 mybox kernel: [ 320.416000] set_level status: 0
Sep 2 10:23:18 mybox kernel: [ 320.436000] set_level status: 0
Sep 2 10:23:18 mybox kernel: [ 320.456000] set_level status: 0
Sep 2 10:23:18 mybox kernel: [ 320.476000] set_level status: 0
Sep 2 10:23:18 mybox kernel: [ 320.496000] set_level status: 0

around 10:22 I have killed 'wpa_supplicant' and no more 'iwl4965: REPLY_ADD_STA failed' messages

I'm downloading ubuntu-iso to test and I don't see "hiccuping" and so 'wpa_supplicant' is the real problem.

Actually I'm testing my system on "Access Point" without encryption (no wpa/2 or wep)

[Rich Birch (ringo-albumsnaps)]

I'm experiencing exactly the same problem with a Lenovo laptop (N200) using the Intel 4965AGN wifi card.

I'm using ubuntu fiesty and have compiled the iwl4965 driver myself from http://intellinuxwireless.org/?p=iwlwifi since they're not yet available in stable kernels. Yours is the first report I've managed to find about this problem.

I was using wpa until yesterday when for other reasons I had to switch my router to wep, but I'm still experiencing the short lockups. I didn't realise wpa_supplicant was being used for wep connections but it appears to be, so I guess you could well be correct.

I'm going to keep investigating and I'll write back if I find a solution.

Thanks!

[Reinhard Tartler (siretart)]

if you don't want wpasupplicant to scan 'around', you can configure that with the ap-scan parameter. See the documentation of wpasupplicant. I'm therefore rejecting this bugtask.

If you are using network manager, I'd suggest opening a bugtask against that package. Honestly, I think iwl3945 and networkmanager need a lot more thought before being usable. Upstream seems to be aware of this.

[Rich Birch (ringo-albumsnaps)]

Thanks but it seems on fiesty at least that there is no wpa_supplicant.conf file when using network manager (which I guess is why you suggested filing a bug report against that)

Do you know of a way to get network manager to tell wpa to not scan?

[Reinhard Tartler (siretart)]

Rich Birch <email address hidden> writes:

> Thanks but it seems on fiesty at least that there is no
> wpa_supplicant.conf file when using network manager (which I guess is
> why you suggested filing a bug report against that)
>
> Do you know of a way to get network manager to tell wpa to not scan?

TTBOMK, this is not possible. Please contact the network manager
developers about that.

--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4