iwl4965 driver hiccuping on Dell XPS M1330

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include as attachments the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

Hi,

$ uname -a
Linux mybox 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 GNU/Linux

Attached 2 files

Thanks,
Julio

Same laptop, same wireless card, different problems:

-works fine one g AP, despite some disconnections sometimes
-with another AP, it's getting associated, but after a few packets uploaded, it's dead. I have to modprobe -r the module and modprobe it again. Then it goes for a few kb, and dead again.

I can provide logs as well if that seems necessary. If you think it's another bug, I can open one.

I have added another bug about our wireless-card on ubuntu here:

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/133397

have you same problem?

I'm using Network Manager, and it's connecting fine at boot, so I don't think I have this problem. I have an up-to-date Gutsy.

Yes, I'm using Network Manager too, but I have this problem at boot and I have no idea about cause of problem.

Actually I cannot use wireless anymore!

No manual restarting, no network-manager, nothing works

I re-post my dmesg and post /var/log/syslog

$ uname -a
Linux mybox 2.6.22-10-generic #1 SMP Wed Aug 22 08:11:52 GMT 2007 i686 GNU/Linux

I have a problem that sound like this one. The connection work for 5 seconds and than stops for 3 seconds.

I'm running Kubuntu Gutsy tribe 5 on an ASUS G1S.

The problem seems to be "caused" by wpa_supplicant asking for a SCAN of the wireless every 5 seconds. If you kill wpa_supplicant the connection no longer drops out. If you run WAP it work fine.

Every time it drops out there is the following message in kern.log

Sep 2 11:54:16 asus kernel: [ 2788.376000] iwl4965: REPLY_ADD_STA failed
Sep 2 11:54:23 asus kernel: [ 2795.756000] iwl4965: REPLY_ADD_STA failed
Sep 2 11:54:31 asus kernel: [ 2803.136000] iwl4965: REPLY_ADD_STA failed
Sep 2 11:54:38 asus kernel: [ 2810.516000] iwl4965: REPLY_ADD_STA failed

Yes :) maybe it's cause. My 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.

Do I start a new bug report for 'wpa_supplicant'?

Started new bug-report for wpa_supplicant here:

https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/136725

I suspect that wpa_suplicant is doing what it always does and it's some problem in the wireless driver that means that the scan is causing the link to drop out.

ok, I let wpa_supplicant bug-report open again a bit, and eventually I close it if iwl4965-driver is confirmed like main problem

wpa_supplicant bug-report is considered invalid and so the problem is relative to iwl4965 driver.

Gutsy l-u-m commit e11a59413f44fe0d8594f630483f73d10cbeb9b6. This updates iwlwifi to 0.1.15 from http://intellinuxwireless.org. My scp bulk transfer testing now shows consistent throughput.

In http://intellinuxwireless.org is out version 0.1.16. It seems re-fix changes in 0.1.15 (in the file CHANGES)

The latest gutsy kernel 2.6.22-12 solved these problems for me. I now see consistent throughput.

Situation seems worsened:

wpa_supplicant crashes and connection goes down (I need to restart it)

Updated to iwlwifi release 1.1.0

just upgraded my gutsy...

I confirm: situation is worsened...

If I try to download a big file (for example feisty ubuntu iso) after downloaded 5.8 MB everytime connection goes down and wpa_supplicant dies...

probably I need to change title of this bug report from hiccuping to dying...

I am seeing some strange problems with wpa_supplicant from time to time, and happen to be using iwl4965 as well. I can't say whether the driver is at fault or not.

I tried using knetworkmanger with the latest driver and I wasn't able to connect at all.

I didn't investigate too closely since the wireless works fine with a static config in /etc/network/interfaces.

iwl4965 is in Gusty l-u-m

Still there with iwl4965 1.1.17

driver loaded with debug=0x41002:

/var/log/syslog shows:

Sep 28 22:45:47 boris-laptop kernel: [10215.132000] iwl4965: I iwl_mac_tx enter
Sep 28 22:45:47 boris-laptop kernel: [10215.132000] iwl4965: I iwl_mac_tx leave
Sep 28 22:45:47 boris-laptop kernel: [10215.132000] iwl4965: I iwl_mac_tx enter
Sep 28 22:45:47 boris-laptop kernel: [10215.132000] iwl4965: I iwl_mac_tx leave
Sep 28 22:45:52 boris-laptop kernel: [10220.136000] iwl4965: U iwl_mac_hw_scan enter
Sep 28 22:45:52 boris-laptop kernel: [10220.136000] iwl4965: U iwl_mac_hw_scan leave
Sep 28 22:45:54 boris-laptop kernel: [10222.504000] iwl4965: U iwl_mac_config enter to channel 9
Sep 28 22:45:54 boris-laptop kernel: [10222.504000] iwl4965: U iwl_mac_config leave
Sep 28 22:45:54 boris-laptop kernel: [10222.504000] iwl4965: U iwl_mac_config_interface enter: interface id 6
Sep 28 22:45:54 boris-laptop kernel: [10222.504000] iwl4965: U iwl_mac_config_interface bssid: 00:04:0e:d8:04:ec
Sep 28 22:45:54 boris-laptop kernel: [10222.504000] iwl4965: U iwl_mac_config_interface leave
Sep 28 22:45:54 boris-laptop kernel: [10222.504000] iwl4965: I iwl_mac_tx enter
Sep 28 22:45:54 boris-laptop kernel: [10222.504000] iwl4965: I iwl_mac_tx leave
Sep 28 22:45:54 boris-laptop kernel: [10222.504000] iwl4965: I iwl_mac_tx enter
Sep 28 22:45:54 boris-laptop kernel: [10222.504000] iwl4965: I iwl_mac_tx leave
Sep 28 22:45:59 boris-laptop kernel: [10227.508000] iwl4965: U iwl_mac_hw_scan enter
Sep 28 22:45:59 boris-laptop kernel: [10227.508000] iwl4965: U iwl_mac_hw_scan leave
Sep 28 22:46:02 boris-laptop kernel: [10229.880000] iwl4965: U iwl_mac_config enter to channel 9
Sep 28 22:46:02 boris-laptop kernel: [10229.880000] iwl4965: U iwl_mac_config leave
Sep 28 22:46:02 boris-laptop kernel: [10229.880000] iwl4965: U iwl_mac_config_interface enter: interface id 6
Sep 28 22:46:02 boris-laptop kernel: [10229.880000] iwl4965: U iwl_mac_config_interface bssid: 00:04:0e:d8:04:ec
Sep 28 22:46:02 boris-laptop kernel: [10229.880000] iwl4965: U iwl_mac_config_interface leave

repeating in a 5 seconds' loop

http://intellinuxwireless.org/mac80211/downloads/mac80211-10.0.0.tgz
against kernel 2.6.22 is reported so solve the problem. current ubuntus mac80211 is still vanillas 8.0.2.tgz I believe...

Don't know if it is possible to deliver ubuntu linux-image/source/modules with the latest mac subsystem, since ubuntu is in beta now.

please see https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/144520/comments/8

I managed to get iwl stable by applying mac80211-10.0.0.
If someone could tell how to stop the resulting syslog / dmesg spam...

OK,

I changed mac80211-10.0.0.tgz's
pending/0025-mac80211-HT-use-KERN_DEBUG-for-HT-debugging-messa.patch
to look like this:

[snip]
From f597c02bc8814aa0ba5b3b9fd1aa14d521b284b8 Mon Sep 17 00:00:00 2001
From: Zhu Yi <email address hidden>
Date: Mon, 9 Jul 2007 14:13:02 +0800
Subject: [PATCH] mac80211: [HT] use KERN_DEBUG for HT debugging message

Signed-off-by: Zhu Yi <email address hidden>
---
 net/mac80211/wme.c | 2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/net/mac80211/wme.c b/net/mac80211/wme.c
index 96e9969..beb729d 100644
--- a/net/mac80211/wme.c
+++ b/net/mac80211/wme.c
@@ -283,7 +283,7 @@ static int wme_qdiscop_enqueue(struct sk_buff *skb, struct Qdisc* qd)
                                queue = ht_queue;
                                pkt_data->ht_queue = 1;
                        }
- printk(KERN_ERR "wme:%s ht_queue=%d,queue=%d pool=0x%lX qdisc=%p\n",
- __func__,ht_queue,queue,q->qdisc_pool,q);

                        sta_info_put(sta);
--
1.5.2

[snap]

I know, it's dirty, but I need a working solution...

please see my comments

Sigh,

here is what I *really* did to "pending/0025-mac80211-HT-use-KERN_DEBUG-for-HT-debugging-messa.patch" (see attachment)

Has anyone seen the problem in this somewhat related bug?
https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/144621

If so, and if someone's available, can they load the driver with debug=0x41002 and attach the log to bug144621 after the problem happens?

thanks for your help

with last upgrade to:

$ uname -r
2.6.22-14-generic

hiccuping problem seems fixed... :)

I wait a bit of time again and if there are not problems I close this bug report (finally)

great! bug fixed! I close this bug report - thanks!