Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 261248 - net-wireless/iwl4965-ucode microcode error with 2.6.28-tuxonice-r3
Summary: net-wireless/iwl4965-ucode microcode error with 2.6.28-tuxonice-r3
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: AMD64 Linux
: High major (vote)
Assignee: Peter Volkov (RETIRED)
Depends on:
Reported: 2009-03-05 03:34 UTC by Julian Heckbert
Modified: 2010-12-23 14:35 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---

emerge --info (einfo,3.48 KB, text/plain)
2009-03-05 03:35 UTC, Julian Heckbert

Note You need to log in before you can comment on or make changes to this bug.
Description Julian Heckbert 2009-03-05 03:34:06 UTC
I get the following error in dmesg when I try to use my Intel iwl4965 card with the 2.6.28 kernel
  [ 2663.532142] iwlagn: Microcode SW error detected.  Restarting 0x2000000.
  [ 2665.745793] iwlagn: No space for Tx
  [ 2665.745798] iwlagn: Error sending SENSITIVITY_CMD: enqueue_hcmd failed: -28
  [ 2665.745800] iwlagn: SENSITIVITY_CMD failed 
I'm using the microcode on an amd64 machine, I get the same error with the microcode

Reproducible: Always

Steps to Reproduce:
1. bring up the wireless interface and connect to a wireless network
2. wait
Actual Results:  
the wireless card appears to still be connected to the wireless network but any connection attempts across the interface will time out

Expected Results:  
connections across the interface should have gone through

The card works fine with the 2.6.27-gentoo and 2.6.26-tuxonice kernels
the wicd daemon is normally used to connect to wireless networks, but without it, the same problem occurs
Comment 1 Julian Heckbert 2009-03-05 03:35:55 UTC
Created attachment 183962 [details]
emerge --info
Comment 2 Peter Volkov (RETIRED) gentoo-dev 2009-03-06 08:56:10 UTC
Thank you for report Julian. Please enable CONFIG_IWLWIFI_DEBUG in your kernel and load module with modprobe iwl4965 debug=0x43fff, reproduce bug and show us output.

This issue was discussed for a very long time at ubuntu (with no resolution):
and probably similar issue was reported upstream by redhat user:
but no much progress done there, so, could you report your issue upstream:
and tell us URL so we could track the progress there?
Comment 3 Julian Heckbert 2009-03-06 14:44:14 UTC
bug reported upstream here:
Comment 4 Peter Volkov (RETIRED) gentoo-dev 2010-12-23 14:35:26 UTC
Upstream bug was assigned as duplicate of and duplicate is marked as needinfo. Unfortunately without upstream we can do nothing here, so I'll set status of this bug to be the same as upstream.