iwl3945: no space for tx, Error sending REPLY_LEDS_CMD: iwl3945_enqueue_hcmd failed: -28

[DaveAbrahams]

Binary package hint: udev

This is in intrepid (8.10). My version of udev is 124-9 but I have no idea if that's the right package.

I get loads of these in my syslog, even when my primary network connection is wired. Simply plugging in an external USB keyboard causes a flood of them (why I tagged udev), but they will continue to appear on their own.

Jan 15 20:44:42 mcbain kernel: [61540.684694] iwl3945: No space for Tx
Jan 15 20:44:42 mcbain kernel: [61540.684707] iwl3945: Error sending REPLY_LEDS_CMD: iwl3945_enqueue_hcmd failed: -28

Disabling wireless networking in Network Manager seems to make it stop.

syslog attached.

[Chris Coulson (chrisccoulson)]

This looks like a kernel issue rather than a udev issue, so I'm re-assigning. Please include the following additional information, if you have not already done so (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" after a fresh boot 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.
4. Please attach your /var/log/kern.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!

[Chris Coulson (chrisccoulson)]

Doesn't look like a Network Manager bug either. Closing the Network Manager task. Also, you added an upstream Intel Linux Wireless task. I'm going to close that for now, but will reopen it if it looks like a driver problem and we send the bug upstream.

[DaveAbrahams (boostpro)]

on Fri Jan 16 2009, Chris Coulson <chrisccoulson-AT-googlemail.com> wrote:

> This looks like a kernel issue rather than a udev issue, so I'm re-
> assigning. Please include the following additional information, if you
> have not already done so (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.

Linux mcbain 2.6.27-10-generic #1 SMP Fri Nov 21 12:00:22 UTC 2008 i686 GNU/Linux

> 2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the
> resulting file "dmesg.log" to this bug report.

Done

> 3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting
> file "lspci-vvnn.log" to this bug report.

Done.

> 4. Please attach your /var/log/kern.log to this bug report.

Done.

--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com

[Finlay Thompson (finlay-nz)]

Just wanted to confirm that I had this problem for the first time this morning.

I'm running Intrepid, totally up to date. It started swapping on my computer, making it completely unusable.

Note that I have an encrypted disk, so when things start going wrong, they go really slow!

Anyway, attached the output from
$ grep iwl3945 /var/log/syslog > iwl3945.log

[zorblek (zorblek)]

I am getting this same error in a different context. When I attempt to boot in Intrepid, Gnome fails to load properly and I get this exact error repeatedly. This is on a Dell XPS M1210 with no external hardware attached. I would post error logs but I am currently only able to get online from a wifi-enabled media player...

[Jeffrey Baker (jwbaker)]

There's a lot of noise on this bug, but it's definitely a kernel issue. I see this quite frequently on Jaunty (amd64) with kernel 2.6.28-8.24. For instance:

[19298.596118] iwl3945: Error sending REPLY_SCAN_CMD: time out after 500ms.
[19298.596145] iwl3945: No space for Tx
[19298.596150] iwl3945: Error sending REPLY_RXON: iwl3945_enqueue_hcmd failed: -28
[19298.596155] iwl3945: Error setting new configuration (-28).
[19298.596163] iwl3945: No space for Tx
[19298.596167] iwl3945: Error sending REPLY_TX_PWR_TABLE_CMD: iwl3945_enqueue_hcmd failed: -28
[19303.597739] iwl3945: No space for Tx
[19303.597748] iwl3945: Error sending REPLY_SCAN_CMD: iwl3945_enqueue_hcmd failed: -28
[19303.597770] iwl3945: No space for Tx
[19303.597774] iwl3945: Error sending REPLY_RXON: iwl3945_enqueue_hcmd failed: -28
[19303.597779] iwl3945: Error setting new configuration (-28).
[19303.597786] iwl3945: No space for Tx

Etc etc etc. It goes on like that forever if you don't remove the kernel module. Removing and reinserting the kernel module makes it stop. Needless to say, the network doesn't work during these episodes.

[Jeffrey Baker (jwbaker)]

Attaching my dmesg, since the previous reporter had both a tainted kernel, and a dmesg that didn't show the problem.

[Chris Coulson (chrisccoulson)]

Jeffrey - would you mind testing this on Jaunty using a vanilla 2.6.29-rc5 kernel, available from here:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.29-rc5/

Thanks

[zorblek (zorblek)]

My problem turned out to be unrelated to this bug. I am, however, still
getting that error message. Here's the output of dmesg.

On Sun, Feb 22, 2009 at 8:44 AM, Chris Coulson <<email address hidden>
> wrote:

> Jeffrey - would you mind testing this on Jaunty using a vanilla
> 2.6.29-rc5 kernel, available from here:
>
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.29-rc5/
>
> Thanks
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
> Status: Confirmed => Incomplete
>
> --
> iwl3945: no space for tx, Error sending REPLY_LEDS_CMD:
> iwl3945_enqueue_hcmd failed: -28
> https://bugs.launchpad.net/bugs/317728
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Intel Linux Wireless project upstream project presentation in
> launchpad.: Invalid
> Status in The Linux Kernel: In Progress
> Status in NetworkManager: Invalid
> Status in "linux" source package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: udev
>
> This is in intrepid (8.10). My version of udev is 124-9 but I have no idea
> if that's the right package.
>
> I get loads of these in my syslog, even when my primary network connection
> is wired. Simply plugging in an external USB keyboard causes a flood of
> them (why I tagged udev), but they will continue to appear on their own.
>
> Jan 15 20:44:42 mcbain kernel: [61540.684694] iwl3945: No space for Tx
> Jan 15 20:44:42 mcbain kernel: [61540.684707] iwl3945: Error sending
> REPLY_LEDS_CMD: iwl3945_enqueue_hcmd failed: -28
>
> Disabling wireless networking in Network Manager seems to make it stop.
>
> syslog attached.
>

[Jeffrey Baker (jwbaker)]

I ran with the 2.6.29-rc5 kernel two days straight and have not seen the problem. Usually I would see this problem once or more times every day. I'll keep watching to see if it recurs.

[Jeffrey Baker (jwbaker)]

Scratch my last. I just saw the very same error with the 2.6.29-rc5 kernel.

[snowch (snowch)]

My laptop has just started hanging (in the last couple of days) with this problem on Ubuntu 8.10 with 2.6.27-11-generic i386

[Marios Karaoulis (marios-hellas-23)]

Same error using kubuntu 9.04 with linux-backports-modules

[Lubosz Sarnecki (lubosz)]

Same issue here. But it's the routers fault. Never had problems with WPA before. I get disconnects and have to reset my wifi.

?field.comment=Same issue here. But it's the routers fault. Never had problems with WPA before. I get disconnects and have to reset my wifi.

$ uname -a
Linux bBook 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009 x86_64 GNU/Linux

Jan 12 20:04:13 bBook kernel: [142108.360072] iwlagn 0000:03:00.0: Error sending REPLY_SCAN_CMD: time out after 500ms.
Jan 12 20:04:14 bBook kernel: [142108.860261] iwlagn 0000:03:00.0: Error sending REPLY_RXON: time out after 500ms.
Jan 12 20:04:14 bBook kernel: [142108.860274] iwlagn 0000:03:00.0: Error setting new RXON (-110)
Jan 12 20:04:14 bBook kernel: [142109.360229] iwlagn 0000:03:00.0: Error sending REPLY_RXON: time out after 500ms.
Jan 12 20:04:14 bBook kernel: [142109.360241] iwlagn 0000:03:00.0: Error setting new RXON (-110)
Jan 12 20:04:19 bBook kernel: [142113.860261] iwlagn 0000:03:00.0: Error sending REPLY_RXON: time out after 500ms.
Jan 12 20:04:19 bBook kernel: [142113.860273] iwlagn 0000:03:00.0: Error setting new RXON (-110)
Jan 12 20:04:19 bBook kernel: [142114.360107] iwlagn 0000:03:00.0: Error sending REPLY_SCAN_CMD: time out after 500ms.
Jan 12 20:04:20 bBook kernel: [142114.861438] iwlagn 0000:03:00.0: Error sending REPLY_RXON: time out after 500ms.
Jan 12 20:04:20 bBook kernel: [142114.861450] iwlagn 0000:03:00.0: Error setting new RXON (-110)

[hexa- (mweinelt-deactivatedaccount)]

Having this issue in University when transfering larger parts of data via the wlan network (i.e. upgrading, downloads).

It feels like an internal buffer in the adapter is filling up and when it disconnects the timespans it stays stable are getting shorter with each reconnect.

rmmod iwl3945 && modprobe iwl3945 helps but only very shortly.

$ uname -a
Linux mweinelt-laptop 2.6.32-21-generic #32-Ubuntu SMP Fri Apr 16 08:09:38 UTC 2010 x86_64 GNU/Linux

$ lspci | grep Net
0b:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)

This bug has not been existent for me in earlier versions of Ubuntu, currently using 9.04 Beta.

[hexa- (mweinelt-deactivatedaccount)]

10.04 Beta was what i meant. Please, anyone?

[Stefan Flanderijn (ca-launchpad)]

I'm having exactly those issues with the iwl3945 adapter on ubuntu 10.04 LTS on a Dynamic WEP, TTLS, PEAP network at my university.

[hexa- (mweinelt-deactivatedaccount)]

Can confirm for WPA2 Enterprise as well.

[Stavros Filargyropoulos (stafil)]

Hitting this bug as well. Running 10.04. Would be nice if the patch for this is included in the next compiled kernel.

[cne007 (cne007)]

Just switch to plain Debian 5.04 to Kubuntu to give it a try. Never had this problem before. Now I am getting disconnected all the time when I DL files.
When I connect through VPNC to my work network, I can only surf the work network, always time out when I tried to surf the web. Was working before.

wil switch back to Debian.

[ikke (ikke-iki)]

I just started experiencing this after upgrading from 9.04 to 10.04. My HW is IBM T60 with:

03:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection [8086:4227] (rev 02)
 Subsystem: Intel Corporation Device [8086:1011]
 Flags: bus master, fast devsel, latency 0, IRQ 32
 Memory at edf00000 (32-bit, non-prefetchable) [size=4K]
 Capabilities: <access denied>
 Kernel driver in use: iwl3945
 Kernel modules: iwl3945

$ uname -r
2.6.32-22-generic

$ modinfo iwl3945
filename: /lib/modules/2.6.32-22-generic/kernel/drivers/net/wireless/iwlwifi/iwl3945.ko
firmware: iwlwifi-3945-2.ucode
license: GPL
author: Copyright(c) 2003-2009 Intel Corporation <email address hidden>
version: 1.2.26ks
description: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux
srcversion: 02CBE7C0CB9F55C123EC213
alias: pci:v00008086d00004227sv*sd*bc*sc*i*
alias: pci:v00008086d00004222sv*sd*bc*sc*i*
alias: pci:v00008086d00004227sv*sd00001014bc*sc*i*
alias: pci:v00008086d00004222sv*sd00001044bc*sc*i*
alias: pci:v00008086d00004222sv*sd00001034bc*sc*i*
alias: pci:v00008086d00004222sv*sd00001005bc*sc*i*
depends: mac80211,iwlcore,led-class,cfg80211
vermagic: 2.6.32-22-generic SMP mod_unload modversions 586
parm: antenna:select antenna (1=Main, 2=Aux, default 0 [both]) (int)
parm: swcrypto:using software crypto (default 1 [software])
 (int)
parm: disable_hw_scan:disable hardware scanning (default 0) (int)
parm: fw_restart3945:restart firmware in case of error (int)

I didn't ever notice it before, but now it's bothersome.

[ikke (ikke-iki)]

forgot to mention, I have WPA in use.

[Per Baekgaard (baekgaard)]

Same problem here with 10.04 LTS on an IBM T60 (using WPA/WPA2 authentication).

[Onaka (brollejunior)]

Same with 10.04 LTS on Dell Inspiron 6400

[Yorirou (yorirou)]

Same problem on 10.04 LTS. My network is a 5 GHz 802.11a/n wifi network with WPA 2 personal ecryption.

[Yorirou (yorirou)]

New observation: high speed HTTP traffic (watching youtube videos) triggers this error, while torrent doesn't.

[Tom Morton (tomm)]

This may be fixed in linux kernel 2.6.35-rc3. This commit and other bits it depend on may be the thing:

http://git.kernel.org/?p=linux/kernel/git/iwlwifi/iwlwifi-2.6.git;a=commit;h=a6866ac93e6cb68091326e80b4fa4619a5957644

[zob (zob)]

Affects me to on Lenovo T60 with a Intel 3945ABG wifi card.
lars@T60-laptop:~$ lsb_release -a && uname -a && lshw -C network
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 10.04 LTS
Release: 10.04
Codename: lucid
Linux T60-laptop 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 22:02:19 UTC 2010 i686 GNU/Linux
WARNING: you should run this program as super-user.
  *-network
       description: Ethernet interface
       product: 82573L Gigabit Ethernet Controller
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: eth0
       version: 00
       serial: 00:16:41:e2:6b:75
       width: 32 bits
       clock: 33MHz
       capabilities: bus_master cap_list ethernet physical
       configuration: broadcast=yes driver=e1000e driverversion=1.0.2-k2 firmware=0.5-1 ip=10.0.0.5 latency=0 multicast=yes
       resources: irq:29 memory:ee000000-ee01ffff ioport:3000(size=32)
  *-network
       description: Wireless interface
       product: PRO/Wireless 3945ABG [Golan] Network Connection
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: wlan0
       version: 02
       serial: 00:19:d2:06:25:41
       width: 32 bits
       clock: 33MHz
       capabilities: bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=iwl3945 latency=0 multicast=yes wireless=IEEE 802.11abg
       resources: irq:31 memory:edf00000-edf00fff

[zob (zob)]

Is this bug valid at all???

I mean: Bug Watch Updater on 2009-05-29
Changed in linux:
status: In Progress → Invalid

[zob (zob)]

Maybe worth watching:
https://bugzilla.redhat.com/show_bug.cgi?id=589777

[satyr (t-bicer)]

I have the same problem on my IBM T60. I was using ubuntu 8.04 and never had this problem. Recently, I switched to 10.04 and these things started to happen.

[Woo (w-digmia)]

I can also confirm this bug. It's affecting me on my IBM/Lenovo ThinkPad T60 since I upgraded to ubuntu 10.04 Lucid. It was ok on 9.10.ok.

[zob (zob)]

I think I'm seeing this on windows 7 on the same machine (Thinkpad T60). And then I found this:
http://www.intel.com/support/wireless/wlan/pro3945abg/sb/CS-031631.htm

Maybe a workaround could be to turn off power-saving on the card:
sudo iwconfig wlan0 power off

iwconfig wlan0 power off can be added to /etc/rc.local if it seems to be working I guess.

I havn't tested this yet.

[Woo (w-digmia)]

sudo iwconfig wlan0 power off
Error for wireless request "Set Power Management" (8B2C) :
    SET failed on device wlan0 ; Operation not supported.

I am almost sure it is driver problem. I never had this problem on ubuntu 9.10 nor 9.04.

[zob (zob)]

Look at this one then. That must be our friends on another "invalid" bug.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/348204?comments=all

[zob (zob)]

This workaround seems to be working. I have no clue why.

gksu gedit /etc/default/grub

Change the CMD_LINUX_DEFAULT line to:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.modeset=0 noplymouth"

sudo update-grub

(If you're using burg instead of grub, which I am, just enter burg insted in /etc/default/burg and in update-burg).

[zob (zob)]

Sorry forgot to credit this guy for the workaround: http://forum.ubuntuusers.de/topic/intel-3945-wlan-bricht-ab-und-verbindet-sich-/?highlight=intel+corporation+pro+wireless+3945abg#post-2427198

I help this will be helpful to someone here to.

[zob (zob)]

help=hope

[Truls Skare (truls-skare)]

I can confirm that the GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.modeset=0 noplymouth" workaround works on my thinkpad t60. No dropouts anymore!

[zob (zob)]

I can still make it drop out even with the workaround, but I have to really make an effort. But then it drops in windows as well. To much travelling/zooming in google maps makes it drop out for example (ubuntu & win7).
But it is more or less stable with the workaround.

[pamindic (pam-indicia)]

 Iwl3945 on Thinkpad Z61m and same wireless dropout problem. The "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.modeset=0 noplymouth" workaround has now sorted it.

[effell (effell)]

FYI, on a Thinkpad X60, I have this problem (with Miro) on kernel 2.6.32-25, but not (so far) on 2.6.32-24.
I don't have a Radeon card, so no surprise the above workaround didn't fix it for me.

[Wizgoblar (wizgoblar)]

I have the same problem with my Toshiba Tecra M7 on which I just installed lucid with kernel 2.6.32-24-generic.
I have installed the package linux-backports-modules-wireless-lucid-generic, but I still get disconnects, even while browsing.

Here's lshw -C network:
*-network
       description: Wireless interface
       product: PRO/Wireless 3945ABG [Golan] Network Connection
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: wlan0
       version: 02
       serial: 00:18:de:4e:e5:2f
       width: 32 bits
       clock: 33MHz
       capabilities: bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=iwl3945 driverversion=2.6.32-24-generic firmware=15.32.2.9 ip=192.168.100.8 latency=0 multicast=yes wireless=IEEE 802.11abg
       resources: irq:28 memory:ffcff000-ffcfffff

Here from kern.log:
Sep 22 00:11:59 dknux kernel: [18696.790462] iwl3945 0000:03:00.0: Microcode SW error detected. Restarting 0x82000008.
Sep 22 00:11:59 dknux kernel: [18696.790500] iwl3945 0000:03:00.0: Start IWL Error Log Dump:
Sep 22 00:11:59 dknux kernel: [18696.790506] iwl3945 0000:03:00.0: Status: 0x000202E4, count: 1
Sep 22 00:11:59 dknux kernel: [18696.790511] iwl3945 0000:03:00.0: Desc Time asrtPC blink2 ilink1 nmiPC Line
Sep 22 00:11:59 dknux kernel: [18696.790738] iwl3945 0000:03:00.0: SYSASSERT (#5) 1615053811 0x008B6 0x00274 0x00320 0x01472 116
Sep 22 00:11:59 dknux kernel: [18696.790741]
Sep 22 00:11:59 dknux kernel: [18696.790871] iwl3945 0000:03:00.0: Start IWL Event Log Dump: display last 20 count
Sep 22 00:11:59 dknux kernel: [18696.790914] iwl3945 0000:03:00.0: 1614987569 0x00000080 0313
Sep 22 00:11:59 dknux kernel: [18696.790938] iwl3945 0000:03:00.0: 1614987571 0x000001fe 0501
Sep 22 00:11:59 dknux kernel: [18696.790963] iwl3945 0000:03:00.0: 1614988327 0x00000000 0502
Sep 22 00:11:59 dknux kernel: [18696.790988] iwl3945 0000:03:00.0: 1614989119 0x000000c3 0310
Sep 22 00:11:59 dknux kernel: [18696.791012] iwl3945 0000:03:00.0: 1614989120 0x00000000 0314
Sep 22 00:11:59 dknux kernel: [18696.791037] iwl3945 0000:03:00.0: 1614989121 0x0000031a 0501
Sep 22 00:11:59 dknux kernel: [18696.791061] iwl3945 0000:03:00.0: 1614989126 0x000003fc 0504
Sep 22 00:11:59 dknux kernel: [18696.791086] iwl3945 0000:03:00.0: 1614989127 0x6042c744 0503
Sep 22 00:11:59 dknux kernel: [18696.791111] iwl3945 0000:03:00.0: 1614989127 0x00000010 0503
Sep 22 00:11:59 dknux kernel: [18696.791136] iwl3945 0000:03:00.0: 1614989128 0x0b0188bc 0503
Sep 22 00:11:59 dknux kernel: [18696.791161] iwl3945 0000:03:00.0: 1614989129 0x6042c744 0503
Sep 22 00:11:59 dknux kernel: [18696.791185] iwl3945 0000:03:00.0: 1614989129 0x00000010 0503
Sep 22 00:11:59 dknux kernel: [18696.791210] iwl3945 0000:03:00.0: 1614989130 0x0b0188bc 0503
Sep 22 00:11:59 dknux kernel: [18696.791235] iwl3945 0000:03:00.0: 1614989132 0x0b0188b4 0500
Sep 22 00:11:59 dknux kernel: [18696.791259] iwl3945 0000:03:00.0: 1614989134 0x0b0188b4 0600
Sep 22 00:11:59 dknux kernel: [18696.791284] iwl3945 0000:03:00.0:...

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.