Debian Bug report logs - #461924
firmware-iwlwifi: WLAN connection dies due to "Microcode SW error"

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Andres Järv <andresjarv@gmail.com>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: firmware-iwlwifi: WLAN connection dies due to "Microcode SW error"

Date: Mon, 21 Jan 2008 16:23:40 +0200

Package: firmware-iwlwifi
Version: 0.9
Severity: grave
Justification: renders package unusable

I managed to connect to a WiFi network but after about a minute of surfing the 
internet connection died. While searching for the cause I stumbled upon such 
errors in 'dmesg':

--start dmesg snippet--
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:18:39:a5:79:fc
wlan0: RX authentication from 00:18:39:a5:79:fc (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:18:39:a5:79:fc
wlan0: RX ReassocResp from 00:18:39:a5:79:fc (capab=0x411 status=0 aid=3)
wlan0: associated
iwl3945: Microcode SW error detected.  Restarting 0x82000008.
iwl3945: Error Reply type 0x00000000 cmd REPLY_SCAN_CMD (0x80) seq 0x442F ser
0x00000000
iwl3945: Can't stop Rx DMA.
wlan0: failed to restore operationalchannel after scan
iwl3945: No space for Tx
iwl3945: Error sending REPLY_ADD_STA: iwl_enqueue_hcmd failed: -28
iwl3945: No space for Tx
iwl3945: Error sending REPLY_TX_PWR_TABLE_CMD: iwl_enqueue_hcmd failed: -28
--end dmesg snippet--

I have no idea what the problem might be but "microcode SW error" gave me a hint 
towards the firmware.

My laptop has an Intel 3945 chip.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.23-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=et_EE.UTF-8, LC_CTYPE=et_EE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

-- no debconf information

Message #12 received at 461924@bugs.debian.org (full text, mbox, reply):

From: Didier Raboud <didier@raboud.com>

To: 461924@bugs.debian.org

Date: Wed, 30 Jan 2008 11:17:54 +0100

[Message part 1 (text/plain, inline)]

Hi, 

I confirm this behaviour with latest 2.6.24 kernel. It happens once in a 
while, but still happens.

Regards, 

Didier

[signature.asc (application/pgp-signature, inline)]

Message #17 received at 461924@bugs.debian.org (full text, mbox, reply):

From: Ross Boylan <RossBoylan@stanfordalumni.org>

To: Debian Bug Tracking System <461924@bugs.debian.org>

Subject: firmware-iwlwifi: Microcode SW error with 4965

Date: Wed, 06 Feb 2008 16:27:32 -0500

Package: firmware-iwlwifi
Version: 0.10
Followup-For: Bug #461924

I am seeing the same message, and experiencing intermittent connection
failures, with a 4965 wireless card.  Not all failures are associated
with the message, and I think I sometimes get the Microcode SW
error on start up, but it does not seem to interefere with the card's
operation initially.  I can't immediately find examples of the SW
error message on startup, so I might be mistaken on that last point.

The problem seems to have become more frequent since I went from a
2.6.22 to a 2.6.23 kernel.  The latter, but not the former, supports
Intel's ICH8 audio (which shouldn't be relevant, but who knows?).  I
have bluetooth and wired ethernet, though the latter is not
connected.  Dell Latitude D630.

The failure is sometimes preceded by a period of apparently weakening
signal strength.  Since rebooting, and sometimes simply reloading the
drivers, fixes it, the problem is likely on my machine rather than the
access point.

Upgrading to 0.10 from 0.9 doesn't seem to have helped.

Here's a bit of kern.log.  In this case there's only one Microcode SW
error message.  lspci output appears at the very bottom

Of course, this might be a different  problem from that originally
reported; it might even be a couple of different problems in itself
(e.g., the Microcode SW error and the dropped connections).

#initial boot
Feb  5 08:13:49 cotton kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb  5 08:13:49 cotton kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb  5 08:13:51 cotton kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Feb  5 08:13:51 cotton kernel: hda: drive_cmd: error=0x04 { AbortedCommand }
Feb  5 08:13:51 cotton kernel: ide: failed opcode was: 0xef
Feb  5 08:14:33 cotton kernel: input: Logitech         (3) Button Mouse as /class/input/input10
Feb  5 08:15:18 cotton kernel: wlan0: Initial auth_alg=0
Feb  5 08:15:18 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Feb  5 08:15:18 cotton kernel: wlan0: RX authentication from 00:18:4d:80:b6:24 (alg=0 transaction=2 status=0)
Feb  5 08:15:18 cotton kernel: wlan0: authenticated
Feb  5 08:15:18 cotton kernel: wlan0: associate with AP 00:18:4d:80:b6:24
Feb  5 08:15:18 cotton kernel: wlan0: RX AssocResp from 00:18:4d:80:b6:24 (capab=0x411 status=0 aid=1)
Feb  5 08:15:18 cotton kernel: wlan0: associated
Feb  5 08:15:18 cotton kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Feb  5 08:15:35 cotton kernel: wlan0: no IPv6 routers present

# Since the network is password protected, NetworkManager can not 
# connect to it on initial boot.  It does when I log in and provide
# a passphrase.

# here's one of the failures; I think I had to unload and load the
# drivers twice to get it working

Feb  5 16:39:34 cotton kernel: wlan0: No ProbeResp from current AP 00:18:4d:80:b6:24 - assume out of range
Feb  5 16:39:36 cotton kernel: wlan0: No STA entry for own AP 00:18:4d:80:b6:24
Feb  5 16:39:44 cotton kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Feb  5 16:39:55 cotton kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb  5 16:44:50 cotton kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb  5 16:48:27 cotton kernel: ACPI: PCI interrupt for device 0000:03:00.0 disabled
Feb  5 16:48:50 cotton kernel: iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 0.1.15ks
Feb  5 16:48:50 cotton kernel: iwl4965: Copyright(c) 2003-2007 Intel Corporation
Feb  5 16:48:50 cotton kernel: ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
Feb  5 16:48:50 cotton kernel: PCI: Setting latency timer of device 0000:03:00.0 to 64
Feb  5 16:48:50 cotton kernel: iwl4965: Detected Intel Wireless WiFi Link 4965AGN
Feb  5 16:48:51 cotton kernel: iwl4965: Tunable channels: 11 802.11bg, 13 802.11a channels
Feb  5 16:48:51 cotton kernel: wmaster0: Selected rate control algorithm 'iwl-4965-rs'
Feb  5 16:48:51 cotton kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb  5 16:52:31 cotton kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb  5 16:56:30 cotton kernel: wlan0: Initial auth_alg=0
Feb  5 16:56:30 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Feb  5 16:56:30 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Feb  5 16:56:30 cotton kernel: wlan0: RX authentication from 00:18:4d:80:b6:24 (alg=0 transaction=2 status=0)
Feb  5 16:56:30 cotton kernel: wlan0: authenticated
Feb  5 16:56:30 cotton kernel: wlan0: associate with AP 00:18:4d:80:b6:24
Feb  5 16:56:30 cotton kernel: wlan0: RX AssocResp from 00:18:4d:80:b6:24 (capab=0x411 status=0 aid=1)
Feb  5 16:56:30 cotton kernel: wlan0: associated
Feb  5 16:56:30 cotton kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Feb  5 16:56:47 cotton kernel: wlan0: no IPv6 routers present

Feb  5 19:32:49 cotton kernel: wlan0: RX deauthentication from 00:18:4d:80:b6:24 (reason=7)
Feb  5 19:32:49 cotton kernel: wlan0: deauthenticated
Feb  5 19:32:50 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Feb  5 19:32:50 cotton kernel: wlan0: RX authentication from 00:18:4d:80:b6:24 (alg=0 transaction=2 status=0)
Feb  5 19:32:50 cotton kernel: wlan0: authenticated
Feb  5 19:32:50 cotton kernel: wlan0: associate with AP 00:18:4d:80:b6:24
Feb  5 19:32:50 cotton kernel: wlan0: RX ReassocResp from 00:18:4d:80:b6:24 (capab=0x411 status=0 aid=1)
Feb  5 19:32:50 cotton kernel: wlan0: associated
Feb  5 19:32:50 cotton kernel: iwl4965: TX Power requested while scanning!
Feb  5 19:32:50 cotton kernel: iwl4965: Error setting Tx power (-11).
Feb  5 19:32:50 cotton kernel: iwl4965: TX Power requested while scanning!
Feb  5 19:32:50 cotton kernel: iwl4965: Error setting Tx power (-11).
Feb  5 19:32:54 cotton kernel: wlan0: RX deauthentication from 00:18:4d:80:b6:24 (reason=15)
Feb  5 19:32:54 cotton kernel: wlan0: deauthenticated
Feb  5 19:32:55 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Feb  5 19:32:55 cotton last message repeated 2 times
Feb  5 19:32:55 cotton kernel: wlan0: authentication with AP 00:18:4d:80:b6:24 timed out
Feb  5 19:32:55 cotton kernel: iwl4965: Microcode SW error detected.  Restarting 0x82000000.
Feb  5 19:32:55 cotton kernel: wlan0: failed to restore operationalchannel after scan
Feb  5 19:32:55 cotton kernel: iwl4965: TX Power requested while scanning!
Feb  5 19:33:15 cotton kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb  5 19:33:40 cotton kernel: ACPI: PCI interrupt for device 0000:03:00.0 disabled
Feb  5 19:33:49 cotton kernel: iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 0.1.15ks
Feb  5 19:33:49 cotton kernel: iwl4965: Copyright(c) 2003-2007 Intel Corporation
Feb  5 19:33:49 cotton kernel: ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
Feb  5 19:33:49 cotton kernel: PCI: Setting latency timer of device 0000:03:00.0 to 64
Feb  5 19:33:49 cotton kernel: iwl4965: Detected Intel Wireless WiFi Link 4965AGN
Feb  5 19:33:49 cotton kernel: iwl4965: Tunable channels: 11 802.11bg, 13 802.11a channels
Feb  5 19:33:49 cotton kernel: wmaster0: Selected rate control algorithm 'iwl-4965-rs'
Feb  5 19:33:49 cotton kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb  5 19:35:23 cotton kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb  5 19:35:34 cotton kernel: wlan0: Initial auth_alg=0
Feb  5 19:35:34 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Feb  5 19:35:34 cotton kernel: wlan0: RX authentication from 00:18:4d:80:b6:24 (alg=0 transaction=2 status=0)
Feb  5 19:35:34 cotton kernel: wlan0: authenticated
Feb  5 19:35:34 cotton kernel: wlan0: associate with AP 00:18:4d:80:b6:24
Feb  5 19:35:34 cotton kernel: wlan0: RX AssocResp from 00:18:4d:80:b6:24 (capab=0x411 status=0 aid=1)
Feb  5 19:35:34 cotton kernel: wlan0: associated
Feb  5 19:35:34 cotton kernel: wlan0: association frame received from 00:18:4d:80:b6:24, but not in associate state - ignored
Feb  5 19:35:34 cotton kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Feb  5 19:35:38 cotton kernel: wlan0: RX deauthentication from 00:18:4d:80:b6:24 (reason=15)
Feb  5 19:35:38 cotton kernel: wlan0: deauthenticated
Feb  5 19:35:39 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Feb  5 19:35:39 cotton kernel: wlan0: RX authentication from 00:18:4d:80:b6:24 (alg=0 transaction=2 status=0)
Feb  5 19:35:39 cotton kernel: wlan0: authenticated
Feb  5 19:35:39 cotton kernel: wlan0: associate with AP 00:18:4d:80:b6:24
Feb  5 19:35:39 cotton kernel: wlan0: RX ReassocResp from 00:18:4d:80:b6:24 (capab=0x411 status=0 aid=1)
Feb  5 19:35:39 cotton kernel: wlan0: associated
Feb  5 19:35:39 cotton kernel: iwl4965: TX Power requested while scanning!
Feb  5 19:35:39 cotton kernel: iwl4965: Error setting Tx power (-11).
Feb  5 19:35:39 cotton kernel: iwl4965: TX Power requested while scanning!
Feb  5 19:35:39 cotton kernel: iwl4965: Error setting Tx power (-11).
Feb  5 19:35:43 cotton kernel: wlan0: RX deauthentication from 00:18:4d:80:b6:24 (reason=15)
Feb  5 19:35:43 cotton kernel: wlan0: deauthenticated
Feb  5 19:35:44 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Feb  5 19:35:44 cotton kernel: wlan0: no IPv6 routers present
Feb  5 19:35:44 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Feb  5 19:35:45 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Feb  5 19:35:45 cotton kernel: wlan0: authentication with AP 00:18:4d:80:b6:24 timed out
Feb  5 19:35:45 cotton kernel: iwl4965: Microcode SW error detected.  Restarting 0x82000000.
Feb  5 19:35:47 cotton kernel: wlan0: failed to restore operationalchannel after scan
Feb  5 19:35:47 cotton kernel: iwl4965: No space for Tx
Feb  5 19:35:47 cotton kernel: iwl4965: Error sending REPLY_ADD_STA: iwl_enqueue_hcmd failed: -28
Feb  5 19:35:47 cotton kernel: iwl4965: No space for Tx
Feb  5 19:35:47 cotton kernel: iwl4965: Error sending REPLY_TX_LINK_QUALITY_CMD: iwl_enqueue_hcmd failed: -28
Feb  5 19:35:47 cotton kernel: iwl4965: No space for Tx
Feb  5 19:35:47 cotton kernel: iwl4965: Error sending REPLY_TX_PWR_TABLE_CMD: iwl_enqueue_hcmd failed: -28
Feb  5 19:35:52 cotton kernel: iwl4965: REPLY_ADD_STA failed
Feb  5 19:35:52 cotton kernel: wlan0: Initial auth_alg=0
Feb  5 19:35:52 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Feb  5 19:35:52 cotton kernel: wlan0: Initial auth_alg=0
Feb  5 19:35:52 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Feb  5 19:35:52 cotton kernel: wlan0: RX authentication from 00:18:4d:80:b6:24 (alg=0 transaction=2 status=0)
Feb  5 19:35:52 cotton kernel: wlan0: authenticated
Feb  5 19:35:52 cotton kernel: wlan0: associate with AP 00:18:4d:80:b6:24
Feb  5 19:35:52 cotton kernel: wlan0: authentication frame received from 00:18:4d:80:b6:24, but not in authenticate state - ignored
Feb  5 19:35:52 cotton kernel: wlan0: authentication frame received from 00:18:4d:80:b6:24, but not in authenticate state - ignored
Feb  5 19:35:52 cotton kernel: wlan0: RX ReassocResp from 00:18:4d:80:b6:24 (capab=0x411 status=0 aid=1)
Feb  5 19:35:52 cotton kernel: wlan0: associated
Feb  5 19:35:52 cotton kernel: wlan0: deauthenticate(reason=3)
Feb  5 19:36:12 cotton kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb  5 19:36:26 cotton kernel: wlan0: Initial auth_alg=0
Feb  5 19:36:26 cotton kernel: wlan0: authenticate with AP 00:18:4d:80:b6:24
Feb  5 19:36:26 cotton kernel: wlan0: RX authentication from 00:18:4d:80:b6:24 (alg=0 transaction=2 status=0)
Feb  5 19:36:26 cotton kernel: wlan0: authenticated
Feb  5 19:36:26 cotton kernel: wlan0: associate with AP 00:18:4d:80:b6:24
Feb  5 19:36:26 cotton kernel: wlan0: RX AssocResp from 00:18:4d:80:b6:24 (capab=0x411 status=0 aid=1)
Feb  5 19:36:26 cotton kernel: wlan0: associated
Feb  5 19:36:26 cotton kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Feb  5 19:36:43 cotton kernel: wlan0: no IPv6 routers present

# lspci
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 0c)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Contoller #4 (rev 02)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 02)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 02)
00:1c.5 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 6 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f2)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 135M (rev a1)
03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)
04:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5755M Gigabit Ethernet PCI Express (rev 02)
05:01.0 CardBus bridge: O2 Micro, Inc. Cardbus bridge (rev 21)
05:01.4 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02)

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (800, 'stable'), (700, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.23-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

-- no debconf information

Message #22 received at 461924@bugs.debian.org (full text, mbox, reply):

From: Tim Richardson <tim@tim-richardson.net>

To: 461924@bugs.debian.org

Subject: adapter fails after suspend/resume

Date: Fri, 22 Feb 2008 11:04:02 +0100

I get this firmware error after resuming from a suspend if I have my
Dell D420 in the docking station on wired connection, suspend, undock
and resume. 
Have to reboot, I haven't found an alternative,

I have sid's 2.6.24 and firmware v 0.10
-- 
Tim Richardson tim@tim-richardson.net
+31 610 899 815
The Netherlands

Message #29 received at 461924@bugs.debian.org (full text, mbox, reply):

From: Ross Boylan <RossBoylan@stanfordalumni.org>

To: 461924@bugs.debian.org

Cc: RossBoylan@stanfordalumni.org

Subject: 461924: iwlwifi fixed upstream

Date: Sat, 05 Apr 2008 20:54:04 -0700

Or so they say.  Is just following the upstream instructions at
linuxwireless.org likely to work?  Will it mess up things done "the
debian way"?

The other complication is that it sounds as if the fix is to the driver,
not the firmware.  The tarball doesn't appear to have any firmware in
it.  They say the 2.6.25 kerrnel will include the fixes, with
linuxwireless.org having stuff for earlier versions.

Ross

Message #34 received at 461924@bugs.debian.org (full text, mbox, reply):

From: maximilian attems <max@stro.at>

To: Ross Boylan <RossBoylan@stanfordalumni.org>

Cc: 461924@bugs.debian.org

Subject: Re: Bug#461924: 461924: iwlwifi fixed upstream

Date: Sun, 6 Apr 2008 14:12:11 +0200

On Sat, Apr 05, 2008 at 08:54:04PM -0700, Ross Boylan wrote:
> Or so they say.  Is just following the upstream instructions at
> linuxwireless.org likely to work?  Will it mess up things done "the
> debian way"?
> 
> The other complication is that it sounds as if the fix is to the driver,
> not the firmware.  The tarball doesn't appear to have any firmware in
> it.  They say the 2.6.25 kerrnel will include the fixes, with
> linuxwireless.org having stuff for earlier versions.

we provide since long 2.6.25 images just read the DebianKernel
debian wiki page for trunk apt line.

Message #39 received at 461924@bugs.debian.org (full text, mbox, reply):

From: Ross Boylan <RossBoylan@stanfordalumni.org>

To: maximilian attems <max@stro.at>

Cc: RossBoylan@stanfordalumni.org, 461924@bugs.debian.org

Subject: Re: Bug#461924: 461924: iwlwifi fixed upstream

Date: Sun, 06 Apr 2008 10:25:37 -0700

On Sun, 2008-04-06 at 14:12 +0200, maximilian attems wrote:
> On Sat, Apr 05, 2008 at 08:54:04PM -0700, Ross Boylan wrote:
> > Or so they say.  Is just following the upstream instructions at
> > linuxwireless.org likely to work?  Will it mess up things done "the
> > debian way"?
> > 
> > The other complication is that it sounds as if the fix is to the driver,
> > not the firmware.  The tarball doesn't appear to have any firmware in
> > it.  They say the 2.6.25 kerrnel will include the fixes, with
> > linuxwireless.org having stuff for earlier versions.
> 
> we provide since long 2.6.25 images just read the DebianKernel
> debian wiki page for trunk apt line.
Thanks for the tip.  For those following, it's
http://wiki.debian.org/DebianKernel.

According to the upstream (intel wifi) bug, 2.6.25 rc5 has the fix; rc3
didn't.  rc5 is what's current from DebianKernel.

I have mixed feelings about using the bleeding edge; I notice some
kernels have been held out of testing for quite awhile, apparently
because of significant problems.

I don't quite know how the packaging works, but I assume
http://kernel-handbook.alioth.debian.org/ and other docs referenced on
the wiki page explain it.

Message #44 received at 461924@bugs.debian.org (full text, mbox, reply):

From: maximilian attems <max@stro.at>

To: Ross Boylan <RossBoylan@stanfordalumni.org>

Cc: 461924@bugs.debian.org

Subject: Re: Bug#461924: 461924: iwlwifi fixed upstream

Date: Sun, 6 Apr 2008 20:33:50 +0200

On Sun, Apr 06, 2008 at 10:25:37AM -0700, Ross Boylan wrote:
> 
> On Sun, 2008-04-06 at 14:12 +0200, maximilian attems wrote:
> Thanks for the tip.  For those following, it's
> http://wiki.debian.org/DebianKernel.
> 
> According to the upstream (intel wifi) bug, 2.6.25 rc5 has the fix; rc3
> didn't.  rc5 is what's current from DebianKernel.

no we have newer, running on
Linux dual 2.6.25-rc8-amd64 #1 SMP Sat Apr 5 05:22:14 UTC 2008 x86_64
GNU/Linux
 
> I have mixed feelings about using the bleeding edge; I notice some
> kernels have been held out of testing for quite awhile, apparently
> because of significant problems.

no held out of testings because of politics 
aka d-i release freezes
 
> I don't quite know how the packaging works, but I assume
> http://kernel-handbook.alioth.debian.org/ and other docs referenced on
> the wiki page explain it.

the etch state, newer no.

Message #49 received at 461924@bugs.debian.org (full text, mbox, reply):

From: Sam Morris <sam@robots.org.uk>

To: 461924@bugs.debian.org

Subject: Re: firmware-iwlwifi: WLAN connection dies due to "Microcode SW error"

Date: Fri, 11 Apr 2008 02:11:14 +0100

[Message part 1 (text/plain, inline)]

I am seeing this with a Samsung Q45 laptop:

        02:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 3945ABG Network Connection [8086:4222] (rev 02)

with both linux-image-2.6.24-1-amd64 version 2.6.24-5 and
linux-image-2.6.25-rc8-amd64 version
2.6.25~rc8-1~experimental.1~snapshot.11063.

-- 
Sam Morris
http://robots.org.uk/

PGP key id 1024D/5EA01078
3412 EA18 1277 354B 991B  C869 B219 7FDB 5EA0 1078

[signature.asc (application/pgp-signature, inline)]

Message #54 received at 461924@bugs.debian.org (full text, mbox, reply):

From: Peter Lewis <prlewis@letterboxes.org>

To: 461924@bugs.debian.org

Subject: Using drivers from linuxwireless.org works for me in Lenny.

Date: Sun, 20 Apr 2008 15:41:47 +0100

Just thought I'd report that I had this problem using a fresh install of Lenny 
on a Samsung Q35 laptop with an intel 3945 wireless NIC.

Installing the latest drivers from linuxwireless.org fixed the problem for me 
using the standard Lenny kernel.

Pete.

Message #59 received at 461924@bugs.debian.org (full text, mbox, reply):

From: maximilian attems <max@stro.at>

To: Peter Lewis <prlewis@letterboxes.org>, 461924@bugs.debian.org

Subject: Re: Bug#461924: Using drivers from linuxwireless.org works for me in Lenny.

Date: Sun, 20 Apr 2008 19:28:39 +0200

On Sun, Apr 20, 2008 at 03:41:47PM +0100, Peter Lewis wrote:
> Just thought I'd report that I had this problem using a fresh install of Lenny 
> on a Samsung Q35 laptop with an intel 3945 wireless NIC.
> 
> Installing the latest drivers from linuxwireless.org fixed the problem for me 
> using the standard Lenny kernel.

they are quite outdate use trunk 2.6.25 snapshot.
wiki.debian.org/DebianKernel

Message #64 received at 461924@bugs.debian.org (full text, mbox, reply):

From: Peter Lewis <prlewis@letterboxes.org>

To: maximilian attems <max@stro.at>

Cc: 461924@bugs.debian.org

Subject: Re: Bug#461924: Using drivers from linuxwireless.org works for me in Lenny.

Date: Mon, 21 Apr 2008 11:29:29 +0100

On Sunday 20 April 2008 at 18:28:39 maximilian attems wrote:
> On Sun, Apr 20, 2008 at 03:41:47PM +0100, Peter Lewis wrote:
> > Just thought I'd report that I had this problem using a fresh install of
> > Lenny on a Samsung Q35 laptop with an intel 3945 wireless NIC.
> >
> > Installing the latest drivers from linuxwireless.org fixed the problem
> > for me using the standard Lenny kernel.
>
> they are quite outdate use trunk 2.6.25 snapshot.
> wiki.debian.org/DebianKernel

Thanks, have just tried this, and though the bug which disconnects the 
connection periodically is not present, I do get this during scanning:

iwl3945: Microcode SW error detected.  Restarting 0x82000008.
iwl3945: Error Reply type 0x00000005 cmd REPLY_TX (0x1C) seq 0x000B ser 
0x0000004B
iwl3945: Error setting new configuration (-5).
iwl3945: Can't stop Rx DMA.

... repeated three or four times. The system temporarily freezes whilst doing 
so. Once the connection is up, it's fine.

This behaviour was not present with the linuxwireless.org latest drivers, 
which worked perfectly with 2.6.24.

Thanks.

Message #69 received at 461924@bugs.debian.org (full text, mbox, reply):

From: Craig Walsh <craig@craignet.co.uk>

To: 461924@bugs.debian.org

Date: Thu, 24 Jul 2008 15:34:44 +0100

I have this problem on a Dell XPS M1330. For some strange reason it is
interfering with my trackpad, it freezes at regular intervals. When i
try and connect to the network it just asks me for the key over and over
again but never connects. Here is a snippet from dmesg:

[  227.206190] iwl3945: Microcode SW error detected.  Restarting
0x82000008. 
[  227.206190] iwl3945: Error Reply type 0x00000005 cmd REPLY_TX (0x1C)
seq 0x0000 ser 0x0000004B 
[  227.206190] iwl3945: Error setting new configuration (-5). 
[  227.210190] iwl3945: Can't stop Rx DMA. 
[  227.210286] psmouse.c: TouchPad at isa0060/serio1/input0 lost
synchronization, throwing 5 bytes away. 
[  218.448330] psmouse.c: resync failed, issuing reconnect request 
[  218.758833] iwl3945: Microcode SW error detected.  Restarting
0x82000008. 
[  218.758833] iwl3945: Error Reply type 0x00000005 cmd REPLY_TX (0x1C)
seq 0x0000 ser 0x0000004B 
[  218.758833] iwl3945: Error setting new configuration (-5). 
[  218.758833] iwl3945: Can't stop Rx DMA. 
[  219.174950] iwl3945: Microcode SW error detected.  Restarting
0x82000008. 
[  219.174950] iwl3945: Error Reply type 0x00000005 cmd REPLY_TX (0x1C)
seq 0x0000 ser 0x0000004B 
[  219.174950] iwl3945: Error setting new configuration (-5). 
[  219.174950] iwl3945: Can't stop Rx DMA. 
[  219.175048] psmouse.c: TouchPad at isa0060/serio1/input0 lost
synchronization, throwing 1 bytes away. 
[  230.154740] psmouse.c: resync failed, issuing reconnect request

Hope this helps.

Kind Regards,
Craig Walsh

Message #76 received at 461924-done@bugs.debian.org (full text, mbox, reply):

From: maximilian attems <max@stro.at>

To: 461924-done@bugs.debian.org

Subject: Re: firmware-iwlwifi: WLAN connection dies due to "Microcode SW error"

Date: Sun, 29 Mar 2009 19:26:28 +0200

Version: 0.15

latest firmware package has newer microcode 
that together with newer driver no longer give those errors.
thus closing.

-- 
maks

Send a report that this bug log contains spam.