Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#14248 - [kernel26] iwl3945 firmware bug in linux-2.6.29 X86_64
Attached to Project:
Arch Linux
Opened by Luka Napotnik (napsy) - Wednesday, 15 April 2009, 07:52 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 26 July 2009, 17:31 GMT
Opened by Luka Napotnik (napsy) - Wednesday, 15 April 2009, 07:52 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 26 July 2009, 17:31 GMT
|
DetailsDescription:
My wireless worked well until recently when the system blocks and the intel iwl3945 wireless module begins to take about 50% of my CPU. I guess there's a bug in the module that causes some inner loop. Sometimes I get wireless to work but that's for a short while and suddenly wireless turns off and again the iwl3945 mudule gets 50% of CPU. After the loop begins, the system is still responsible but I can't run any new processes. My kernel is: uname -sr Linux 2.6.29-ARCH I downgraded to kernel 2.6.28 and wireless now works. More reports can be traced in BBS at http://bbs.archlinux.org/viewtopic.php?id=69598 |
This task depends upon
Closed by Roman Kyrylych (Romashka)
Sunday, 26 July 2009, 17:31 GMT
Reason for closing: No response
Additional comments about closing: No responses in +3 months. Please report to upstream if the problem persist with the latest 2.6.30.
Sunday, 26 July 2009, 17:31 GMT
Reason for closing: No response
Additional comments about closing: No responses in +3 months. Please report to upstream if the problem persist with the latest 2.6.30.
I won't request closure on this because I don't know if I would have had problems if I'd upgraded sooner.