Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#15631 - [iwlwifi-4965-ucode] iwl4965 - Microcode SW error detected. - 228.61.2.24-1

Attached to Project: Arch Linux
Opened by Léo Scharf (K-Rembar) - Wednesday, 22 July 2009, 03:33 GMT
Last edited by Roman Kyrylych (Romashka) - Friday, 07 August 2009, 08:43 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Thomas Bächler (brain0)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

Wifi keeps going down whenever you start sending a lot of packets (torrent for example).

iwlagn 0000:0b:00.0: Microcode SW error detected. Restarting 0x82000000.
Registered led device: iwl-phy0::radio
Registered led device: iwl-phy0::assoc
Registered led device: iwl-phy0::RX
Registered led device: iwl-phy0::TX

With the iwlwifi-4965-ucode 228.61.2.24-1 firmware. Had to downgrade to iwlwifi-4965-ucode-228.57.2.23-1-x86_64 in order to have a stable wifi again.

http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=2052
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Friday, 07 August 2009, 08:43 GMT
Reason for closing:  Upstream
Comment by Thomas Bächler (brain0) - Wednesday, 22 July 2009, 07:58 GMT
I don't think there is a point in opening the bug report here, as with every single version of the 4965 ucode, someone's wireless breaks, there's at least three of these reports open and I cannot do the slightest thing about any of them.
Comment by Gerardo Exequiel Pozzi (djgera) - Wednesday, 22 July 2009, 18:29 GMT
@Thomas: These three bugs can be closed as "upstream"?, can do nothing with a blob driver. These bugs are already reported to upstream.
Comment by Thomas Bächler (brain0) - Wednesday, 22 July 2009, 20:53 GMT
I am unsure what to do with them. No matter what we do, with the next ucode release more bugs will be opened, Intel can't seem to get 4965 right (the 3965 and 5xxx work better). I think we should close them, provided there is not a thing we can do.

EDIT: Some correction on your terminology: It is not a binary blob driver, the ucode is executed inside the wireless chip, not the host CPU. All code executed on the CPU is GPL.

Loading...