[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#550534: marked as done (IWL4965 firmware 228.61.2.24 crash when using 802.11n and hw crypto)

Your message dated Sat, 19 Nov 2022 09:43:53 +0100
with message-id <Y3iXSbwZdE/D8PKw@eldamar.lan>
and subject line Re: Bug#550534: firmware-iwlwifi: iwlagn 0000:03:00.0: Microcode SW error detected. Restarting 0x82000000.
has caused the Debian Bug report #550534,
regarding IWL4965 firmware 228.61.2.24 crash when using 802.11n and hw crypto
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
550534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550534
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: firmware-iwlwifi
Version: 0.18
Severity: grave
Justification: renders package unusable


Firmware iwlwifi-4965-2.ucode version 228.61.2.24 in firmware-iwlwifi 0.18
renders the wlan interface unusable. After a couple of minutes, the
following message appears in syslog:

 iwlagn 0000:03:00.0: Microcode SW error detected.  Restarting 0x82000000.

.... after which no packets can be sent, though the interface appears up.
Simply restarting the interface brings it up again.

Downgrading to 0.17 with firmware 228.57.2.23 solves the problem for me.
However, since 0.18 is already in squeeze, that version was hard to track
down. I found it in lenny-backports ultimately:

 http://www.backports.org/debian/pool/non-free/f/firmware-nonfree/firmware-iwlwifi_0.17~bpo50+1_all.deb

Googling this problem turns up hits in every distribution imaginable.
Other Debian bugs that are possibly related are 546213 and 548749.
Allegedly Ubunty Karmic Koala fixes the problem, however, package
linux-firmware_1.21_all.deb also contains 228.61.2.24. A combination of
kernel driver and firmware version perhaps?

Intel seems unaware of the problem. 228.61.2.24 is still the latest version
on:
 http://intellinuxwireless.org/?p=iwlwifi&n=downloads

This is very serious. Please revert to the older microcode version.

More information about my environment:
Intel Wireless WiFi 4965AGN. (ThinkPad R61, 802.11n draft WPA2 AP).
>From lspci:
03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)

wlan0     IEEE 802.11abgn  ESSID:"<censored>"  
          Mode:Managed  Frequency:2.437 GHz  Access Point: <censored>
          Bit Rate=54 Mb/s   Tx-Power=15 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=48/70  Signal level=-62 dBm  Noise level=-91 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-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

firmware-iwlwifi depends on no packages.

firmware-iwlwifi recommends no packages.

Versions of packages firmware-iwlwifi suggests:
ii  initramfs-tools               0.93.4     tools for generating an initramfs
di  linux-image-2.6.30-1-686 [lin 2.6.30-6   Linux 2.6.30 image on PPro/Celeron
ii  linux-image-2.6.30-2-686 [lin 2.6.30-8   Linux 2.6.30 image on PPro/Celeron

-- no debconf information

--- End Message ---
--- Begin Message --- 
Hi

Closing now this bugreport as later revisions of kernel with the same
firmware version seems to have solved or made the connections stable
again for reporting people. In aiming of housekeeping old bugs,
closing the report.

If proplem still persists with a recent Kernel, feel free to reopen.

Regards,
Salvatore

--- End Message ---
Reply to: