Ubuntu 8.10 Intel Corporation PRO/Wireless 5300 AGN [Shiloh] Network Connection When sending a large amount of data, sometimes the kernel starts reporting the errors below. This is running with debug50=0xffffffff when loading the module. The reason I noticed this was because the card seems to stop working every once in a while unless you unload and reload the module and I was hoping for more information as to what might be happening. I'm not sure if the errors below are the source of my problem or just harmless messages. I can definitely reproduce the problem with a ping flood, but this is a somewhat contrived case, but the same message will also occur during upload heavy traffic. modprobe -rv iwlagn modprobe -v iwlagn debug50=0xffffffff ping -f -s 60000 <ip> [ 3220.481562] cfg80211: Using static regulatory domain info [ 3220.481566] cfg80211: Regulatory domain: US [ 3220.481568] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 3220.481571] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm) [ 3220.481574] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) [ 3220.481576] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) [ 3220.481579] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) [ 3220.481581] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) [ 3220.481584] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm) [ 3220.481586] cfg80211: Calling CRDA for country: US [ 3220.542969] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks [ 3220.542975] iwlagn: Copyright(c) 2003-2008 Intel Corporation [ 3220.543232] iwlagn 0000:0b:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 [ 3220.543247] iwlagn 0000:0b:00.0: setting latency timer to 64 [ 3220.543545] iwlagn: Detected Intel Wireless WiFi Link 5300AGN REV=0x24 [ 3220.564493] iwlagn: Tunable channels: 13 802.11bg, 24 802.11a channels [ 3220.564993] wmaster0 (iwlagn): not using net_device_ops yet [ 3220.566090] phy0: Selected rate control algorithm 'iwl-agn-rs' [ 3220.566174] wlan0 (iwlagn): not using net_device_ops yet [ 3224.591408] iwlagn 0000:0b:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 [ 3224.591552] iwlagn 0000:0b:00.0: irq 34 for MSI/MSI-X [ 3224.591605] iwlagn 0000:0b:00.0: firmware: requesting iwlwifi-5000-1.ucode [ 3224.598844] iwlagn loaded firmware version 5.4.1.16 [ 3224.777679] Registered led device: iwl-phy0:radio [ 3224.777706] Registered led device: iwl-phy0:assoc [ 3224.777727] Registered led device: iwl-phy0:RX [ 3224.777746] Registered led device: iwl-phy0:TX [ 3224.806663] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 3226.576539] wlan0: authenticate with AP 00:0a:79:5c:cf:a8 [ 3226.579414] wlan0: authenticated [ 3226.579420] wlan0: associate with AP 00:0a:79:5c:cf:a8 [ 3226.581588] wlan0: RX AssocResp from 00:0a:79:5c:cf:a8 (capab=0x421 status=0 aid=1) [ 3226.581596] wlan0: associated [ 3226.599592] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 3226.599692] wlan0: disassociating by local choice (reason=3) [ 3231.667639] wlan0: authenticate with AP 00:16:01:e6:81:74 [ 3231.669572] wlan0: authenticate with AP 00:16:01:e6:81:74 [ 3231.670414] wlan0: authenticated [ 3231.670419] wlan0: associate with AP 00:16:01:e6:81:74 [ 3231.681024] wlan0: RX AssocResp from 00:16:01:e6:81:74 (capab=0x431 status=0 aid=1) [ 3231.681028] wlan0: associated [ 3237.256049] wlan0: no IPv6 routers present [ 3243.343560] iwlagn: No space for Tx [ 3243.343566] iwlagn: Error sending REPLY_TX_LINK_QUALITY_CMD: enqueue_hcmd failed: -28 [ 3243.343570] iwlagn: No space for Tx [ 3243.343572] iwlagn: Error sending REPLY_TX_LINK_QUALITY_CMD: enqueue_hcmd failed: -28 [ 3243.343575] iwlagn: No space for Tx [ 3243.343577] iwlagn: Error sending REPLY_TX_LINK_QUALITY_CMD: enqueue_hcmd failed: -28 [ 3243.343580] iwlagn: No space for Tx etc...
I'm having almost the same problem with a PRO/Wireless 4965AGN and Linux 2.6.28.7 After a while, the interface stops working and iwlagn complains (with debug=0x43fff): [79762.810351] iwlagn: No space for Tx [79762.810361] iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28 [79762.810383] iwlagn: No space for Tx [79762.810389] iwlagn: Error sending REPLY_RXON: enqueue_hcmd failed: -28 [79762.810394] iwlagn: Error setting new RXON (-28) [79762.810408] iwlagn: No space for Tx [79762.810412] iwlagn: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed: -28 Output at module load time: [79799.033252] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks [79799.033261] iwlagn: Copyright(c) 2003-2008 Intel Corporation [79799.033441] iwlagn 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [79799.033493] iwlagn 0000:03:00.0: setting latency timer to 64 [79799.033613] iwlagn: Detected Intel Wireless WiFi Link 4965AGN REV=0x4 [79799.083052] iwlagn: Tunable channels: 13 802.11bg, 19 802.11a channels [79799.085060] phy1: Selected rate control algorithm 'iwl-agn-rs' [79799.086556] iwlagn 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [79799.086869] iwlagn 0000:03:00.0: irq 314 for MSI/MSI-X [79799.086974] iwlagn 0000:03:00.0: firmware: requesting iwlwifi-4965-2.ucode [79799.348763] Registered led device: iwl-phy1:radio [79799.348815] Registered led device: iwl-phy1:assoc [79799.348862] Registered led device: iwl-phy1:RX [79799.348909] Registered led device: iwl-phy1:TX [79799.406798] ADDRCONF(NETDEV_UP): wlan0: link is not ready ~$ cat /proc/sys/kernel/tainted 0
I just noticed that the first messages after it starts failing are different: [37879.516371] wlan0: No ProbeResp from current AP 00:1c:4a:a0:ee:57 - assume out of range [37881.545841] iwlagn 0000:03:00.0: PCI INT A disabled [37881.606096] iwlagn 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [37881.606237] iwlagn 0000:03:00.0: restoring config space at offset 0x1 (was 0x100102, writing 0x100106) [37881.606416] iwlagn 0000:03:00.0: irq 314 for MSI/MSI-X [37881.810481] Registered led device: iwl-phy0:radio [37881.811119] Registered led device: iwl-phy0:assoc [37881.813091] Registered led device: iwl-phy0:RX [37881.813146] Registered led device: iwl-phy0:TX [37882.312994] iwlagn: Error sending REPLY_ADD_STA: time out after 500ms. [37882.813003] iwlagn: Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms. [37882.813011] iwlagn: Error sending TX power (-110) [37883.313018] iwlagn: Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms. [37883.813016] iwlagn: Error sending REPLY_RXON: time out after 500ms. [37883.813023] iwlagn: Error setting new RXON (-110) [37884.353016] iwlagn: Error sending REPLY_RXON: time out after 500ms. [37884.353023] iwlagn: Error setting new RXON (-110) [37884.852951] iwlagn: Error sending REPLY_RXON: time out after 500ms. [37884.852960] iwlagn: Error setting new RXON (-110) [37884.855431] ADDRCONF(NETDEV_UP): wlan0: link is not ready [37915.116325] iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms. [37915.616342] iwlagn: Error sending REPLY_RXON: time out after 500ms. [37915.616349] iwlagn: Error setting new RXON (-110) [37916.116335] iwlagn: Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms. [37920.616400] iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms. [37921.116338] iwlagn: Error sending REPLY_RXON: time out after 500ms. [37921.116347] iwlagn: Error setting new RXON (-110) [37921.616392] iwlagn: Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms. [37926.116335] iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms. [37926.617219] iwlagn: Error sending REPLY_RXON: time out after 500ms. [37926.617227] iwlagn: Error setting new RXON (-110) [37927.116340] iwlagn: Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms. [37931.617155] iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms. [37932.116335] iwlagn: Error sending REPLY_RXON: time out after 500ms. [37932.116343] iwlagn: Error setting new RXON (-110) [37932.617142] iwlagn: Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms. [37937.117217] iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms. [37937.617139] iwlagn: Error sending REPLY_RXON: time out after 500ms. [37937.617147] iwlagn: Error setting new RXON (-110) [37938.117155] iwlagn: Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms. [37942.617143] iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms. [37943.117149] iwlagn: Error sending REPLY_RXON: time out after 500ms. [37943.117156] iwlagn: Error setting new RXON (-110) [37943.617217] iwlagn: Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms. [37948.117153] iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms. [37948.117183] iwlagn: No space for Tx [37948.117188] iwlagn: Error sending REPLY_RXON: enqueue_hcmd failed: -28 [37948.117194] iwlagn: Error setting new RXON (-28) [37948.117208] iwlagn: No space for Tx [37948.117213] iwlagn: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed: -28 [37953.118618] iwlagn: No space for Tx [37953.118628] iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28 [37953.118647] iwlagn: No space for Tx [37953.118652] iwlagn: Error sending REPLY_RXON: enqueue_hcmd failed: -28 [37953.118657] iwlagn: Error setting new RXON (-28) [37953.118671] iwlagn: No space for Tx [37953.118676] iwlagn: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed: -28
Got same on kernels from .27.x to .29-pre8 [ 6828.900445] iwlagn: Microcode SW error detected. Restarting 0x2000000. [ 6829.142626] Registered led device: iwl-phy0:radio [ 6829.142669] Registered led device: iwl-phy0:assoc [ 6829.142709] Registered led device: iwl-phy0:RX [ 6829.142744] Registered led device: iwl-phy0:TX The network hangs up, the only way is to ifdown and ifup wlan0. Tested on pae and non-pae kernels, iwlwifi-4965-ucode-228.57.2.23-1.noarch
*** Bug 12982 has been marked as a duplicate of this bug. ***
Same problem with 2.6.30-rc5: May 10 12:11:08 jtb [ 9170.456847] iwlagn 0000:0c:00.0: Microcode SW error detected. Restarting 0x2000000. May 10 12:11:08 jtb [ 9170.510810] Registered led device: iwl-phy0::radio May 10 12:11:08 jtb [ 9170.510829] Registered led device: iwl-phy0::assoc May 10 12:11:08 jtb [ 9170.510846] Registered led device: iwl-phy0::RX May 10 12:11:08 jtb [ 9170.510863] Registered led device: iwl-phy0::TX May 10 12:11:54 jtb [ 9215.989961] wlan0: no probe response from AP 00:1e:c1:ae:32:d2 - disassociating May 10 12:11:54 jtb [ 9215.989974] iwlagn 0000:0c:00.0: Invalid station for AGG tid 0 May 10 12:11:54 jtb [ 9215.989982] ------------[ cut here ]------------ May 10 12:11:54 jtb [ 9215.989986] WARNING: at net/mac80211/agg-tx.c:141 warn_slowpath_null+0x23/0x39() May 10 12:11:54 jtb [ 9215.989989] Hardware name: Latitude E6500 May 10 12:11:54 jtb [ 9215.989991] Modules linked in: uvcvideo e1000e uhci_hcd ehci_hcd snd_hda_codec_intelhdmi snd_hda_codec_idt snd_hda_ intel snd_hda_codec snd_pcm snd_page_alloc iwlagn iwlcore mac80211 cfg80211 btusb May 10 12:11:54 jtb [ 9215.990014] Pid: 1103, comm: phy0 Not tainted 2.6.30-rc5 #2 May 10 12:11:54 jtb [ 9215.990016] Call Trace: May 10 12:11:54 jtb [ 9215.990023] [<ffffffff8105f053>] warn_slowpath_fmt+0xe6/0x131 May 10 12:11:54 jtb [ 9215.990028] [<ffffffff81058215>] ? try_to_wake_up+0x1d1/0x1f6 May 10 12:11:54 jtb [ 9215.990034] [<ffffffff8146b1a3>] ? printk+0x79/0x92 May 10 12:11:54 jtb [ 9215.990054] [<ffffffffa004c46e>] ? iwl_tx_agg_stop+0xda/0x212 [iwlcore] May 10 12:11:54 jtb [ 9215.990059] [<ffffffff8105f0c1>] warn_slowpath_null+0x23/0x39 May 10 12:11:54 jtb [ 9215.990077] [<ffffffffa0022763>] ___ieee80211_stop_tx_ba_session+0x69/0x94 [mac80211] May 10 12:11:54 jtb [ 9215.990082] [<ffffffff8146de8b>] ? _spin_lock_bh+0x20/0x4f May 10 12:11:54 jtb [ 9215.990097] [<ffffffffa00228e0>] __ieee80211_stop_tx_ba_session+0x58/0x89 [mac80211] May 10 12:11:54 jtb [ 9215.990112] [<ffffffffa00223ad>] ieee80211_sta_tear_down_BA_sessions+0x2e/0x61 [mac80211] May 10 12:11:54 jtb [ 9215.990128] [<ffffffffa0025785>] ieee80211_set_disassoc+0xcb/0x236 [mac80211] May 10 12:11:54 jtb [ 9215.990143] [<ffffffffa00266cd>] ieee80211_associated+0x126/0x161 [mac80211] May 10 12:11:54 jtb [ 9215.990159] [<ffffffffa002789f>] ? ieee80211_sta_work+0x0/0x902 [mac80211] May 10 12:11:54 jtb [ 9215.990174] [<ffffffffa0028132>] ieee80211_sta_work+0x893/0x902 [mac80211] May 10 12:11:54 jtb [ 9215.990189] [<ffffffffa002789f>] ? ieee80211_sta_work+0x0/0x902 [mac80211] May 10 12:11:54 jtb [ 9215.990204] [<ffffffffa002789f>] ? ieee80211_sta_work+0x0/0x902 [mac80211] May 10 12:11:54 jtb [ 9215.990209] [<ffffffff81072086>] worker_thread+0x132/0x1d9 May 10 12:11:54 jtb [ 9215.990215] [<ffffffff81076ebe>] ? autoremove_wake_function+0x0/0x5e May 10 12:11:54 jtb [ 9215.990219] [<ffffffff81071f54>] ? worker_thread+0x0/0x1d9 May 10 12:11:54 jtb [ 9215.990224] [<ffffffff81076a03>] kthread+0x69/0xac May 10 12:11:54 jtb [ 9215.990228] [<ffffffff8105c29f>] ? schedule_tail+0x36/0x90 May 10 12:11:54 jtb [ 9215.990233] [<ffffffff8102bdfa>] child_rip+0xa/0x20 May 10 12:11:54 jtb [ 9215.990238] [<ffffffff8107699a>] ? kthread+0x0/0xac May 10 12:11:54 jtb [ 9215.990241] [<ffffffff8102bdf0>] ? child_rip+0x0/0x20 May 10 12:11:54 jtb [ 9215.990244] ---[ end trace eb62aacad5d2d074 ]--- May 10 12:11:54 jtb [ 9215.990248] iwlagn 0000:0c:00.0: Invalid station for AGG tid 0 May 10 12:11:54 jtb [ 9215.990251] HW problem - can not stop rx aggregation for tid 0 May 10 12:11:54 jtb [ 9215.990305] iwlagn 0000:0c:00.0: Invalid station for AGG tid 1 May 10 12:11:54 jtb [ 9215.990308] HW problem - can not stop rx aggregation for tid 1 May 10 12:11:54 jtb [ 9215.990344] iwlagn 0000:0c:00.0: Invalid station for AGG tid 6 May 10 12:11:54 jtb [ 9215.990346] HW problem - can not stop rx aggregation for tid 6 May 10 12:11:54 jtb [ 9215.999113] mac80211-phy0: failed to remove key (0, 00:1e:c1:ae:32:d2) from hardware (-22) May 10 12:11:57 jtb [ 9219.344882] wlan0: authenticate with AP 00:1e:c1:ae:32:d2 May 10 12:11:57 jtb [ 9219.378490] wlan0: authenticate with AP 00:1e:c1:ae:32:d2 May 10 12:11:57 jtb [ 9219.387796] wlan0: authenticate with AP 00:1e:c1:ae:32:d2 May 10 12:11:57 jtb [ 9219.391711] wlan0: authenticated May 10 12:11:57 jtb [ 9219.391716] wlan0: associate with AP 00:1e:c1:ae:32:d2 May 10 12:11:57 jtb [ 9219.396222] wlan0: RX ReassocResp from 00:1e:c1:ae:32:d2 (capab=0x431 status=0 aid=1) May 10 12:11:57 jtb [ 9219.396227] wlan0: associated May 10 12:12:17 jtb [ 9239.662035] iwlagn 0000:0c:00.0: iwl_tx_agg_start on ra = 00:1e:c1:ae:32:d2 tid = 0 May 10 12:12:17 jtb [ 9239.662118] iwlagn 0000:0c:00.0: HW queue is empty May 10 12:12:35 jtb [ 9257.416310] iwlagn 0000:0c:00.0: Microcode SW error detected. Restarting 0x2000000. May 10 12:12:35 jtb [ 9257.473089] Registered led device: iwl-phy0::radio May 10 12:12:35 jtb [ 9257.473118] Registered led device: iwl-phy0::assoc May 10 12:12:35 jtb [ 9257.473143] Registered led device: iwl-phy0::RX May 10 12:12:35 jtb [ 9257.473166] Registered led device: iwl-phy0::TX May 10 12:13:09 jtb [ 9291.256589] wlan0: no probe response from AP 00:1e:c1:ae:32:d2 - disassociating
Just FYI...the Intel team will need to comment specifically, but those look like 3+ different problems to me. Adding comments like "same problem" and then a trace that doesn't match only confuses things. Please be reasonably sure that you actually do have the same problem before adding a "me too" comment. In many cases it is better to open a new bug. If it really is the same problem, it is easy to mark a new bug as a duplicate. But once a bug gets used for more than one actual problem it can be very difficult to sort things out.
Yes - the issues in #3 (from Piotr) and #5 (from Jens) do not seem to belong here. Please open a separate bug for them. Although, I do think #5 has already been reported and resolved in intellinuxwireless.org/bugzilla. As far as the other issue goes, we just submitted patches that should resolve the issues. Is it possible to test with the latest wireless-testing kernel?
This tree? git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git
That should be a good place to start, yes. :-)
I'm not sure the fix was already backported by a Fedora maintainer, but I can no longer reproduce this bug on 2.6.29.4-162.fc11.x86_64.
(In reply to comment #10) > I'm not sure the fix was already backported by a Fedora maintainer, but I can > no longer reproduce this bug on 2.6.29.4-162.fc11.x86_64. I doubt so because those patches were only merged into wireless-testing a few days ago. If you want to use a stable kernel for testing then you will have to use compat-wireless to get these recent changes.
Possibly unrelated, from 2.6.29.4-162.fc11.x86_64 I get: May 31 21:45:39 localhost kernel: iwlagn: Read index for DMA queue txq_id (2) index 22 is out of range [0-256] 28 26 May 31 21:45:40 localhost kernel: iwlagn: Microcode SW error detected. Restarting 0x2000000. May 31 21:45:40 localhost kernel: Registered led device: iwl-phy0:radio May 31 21:45:40 localhost kernel: Registered led device: iwl-phy0:assoc May 31 21:45:40 localhost kernel: Registered led device: iwl-phy0:RX May 31 21:45:40 localhost kernel: Registered led device: iwl-phy0:TX May 31 21:48:56 localhost kernel: mac80211-phy0: failed to remove key (0, 00:18:4d:35:b2:1b) from hardware (-22)
What particular changeset in wireless-testing is supposed to fix this bug?
(In reply to comment #12) > Possibly unrelated, from 2.6.29.4-162.fc11.x86_64 I get: > > May 31 21:45:39 localhost kernel: iwlagn: Read index for DMA queue txq_id (2) > index 22 is out of range [0-256] 28 26 > May 31 21:45:40 localhost kernel: iwlagn: Microcode SW error detected. > Restarting 0x2000000. > May 31 21:45:40 localhost kernel: Registered led device: iwl-phy0:radio > May 31 21:45:40 localhost kernel: Registered led device: iwl-phy0:assoc > May 31 21:45:40 localhost kernel: Registered led device: iwl-phy0:RX > May 31 21:45:40 localhost kernel: Registered led device: iwl-phy0:TX > May 31 21:48:56 localhost kernel: mac80211-phy0: failed to remove key (0, > 00:18:4d:35:b2:1b) from hardware (-22) This is unrelated ... but could be resolved if you use the ucode we released recently (v 8.24.2.12) available from http://intellinuxwireless.org/?n=Downloads
(In reply to comment #13) > What particular changeset in wireless-testing is supposed to fix this bug? A few changesets targeted this instability: commit 00cb0e6e5f6a125c4362cb08510bd26cd2285d32 Author: Mohamed Abbas <mohamed.abbas@intel.com> Date: Fri May 22 11:01:53 2009 -0700 iwlcore: Set rb_timeout to 0x10 for devices with ICT commit dd588a32df697923a53b46ac48b58a4d1696fabe Author: Mohamed Abbas <mohamed.abbas@intel.com> Date: Fri May 22 11:01:52 2009 -0700 iwlcore: Add support for periodic RX interrupt commit bb8d9dc232984652cf648dd7e34df5dc4aa2582f Author: Mohamed Abbas <mohamed.abbas@intel.com> Date: Fri May 22 11:01:51 2009 -0700 iwlcore: Allow skb allocation from tasklet. commit 617547266c17feeec5b24738fd7ed0b340f94998 Author: Mohamed Abbas <mohamed.abbas@intel.com> Date: Fri May 22 11:01:50 2009 -0700 iwlcore: support ICT interrupt commit 78b4233a8565302422c8070a9d7b593ca8f5ad2a Author: Mohamed Abbas <mohamed.abbas@intel.com> Date: Fri May 22 11:01:47 2009 -0700 iwlcore: register locks
(In reply to comment #14) > (In reply to comment #12) > > Possibly unrelated, from 2.6.29.4-162.fc11.x86_64 I get: > > > > May 31 21:45:39 localhost kernel: iwlagn: Read index for DMA queue txq_id > (2) > > index 22 is out of range [0-256] 28 26 > > May 31 21:45:40 localhost kernel: iwlagn: Microcode SW error detected. > > Restarting 0x2000000. > > May 31 21:45:40 localhost kernel: Registered led device: iwl-phy0:radio > > May 31 21:45:40 localhost kernel: Registered led device: iwl-phy0:assoc > > May 31 21:45:40 localhost kernel: Registered led device: iwl-phy0:RX > > May 31 21:45:40 localhost kernel: Registered led device: iwl-phy0:TX > > May 31 21:48:56 localhost kernel: mac80211-phy0: failed to remove key (0, > > 00:18:4d:35:b2:1b) from hardware (-22) > > This is unrelated ... but could be resolved if you use the ucode we released > recently (v 8.24.2.12) available from > http://intellinuxwireless.org/?n=Downloads I've actually already been using it since May 22: iwl5000-firmware-8.24.2.12-1.fc11.noarch -rw-r--r-- 1 root root 345008 Jun 2 2008 /lib/firmware/iwlwifi-5000-1.ucode -rw-r--r-- 1 root root 353240 Apr 23 21:28 /lib/firmware/iwlwifi-5000-2.ucode iwlagn 0000:03:00.0: firmware: requesting iwlwifi-5000-1.ucode iwlagn loaded firmware version 5.4.1.16 Should I file a new bug report?
(In reply to comment #16) > iwlagn 0000:03:00.0: firmware: requesting iwlwifi-5000-1.ucode > iwlagn loaded firmware version 5.4.1.16 Oh, wait: my kernel is still requestiong the old firmware. I guess I should upgrade my kernel too? To what version? (sorry for the confusion)
(In reply to comment #17) > (In reply to comment #16) > > iwlagn 0000:03:00.0: firmware: requesting iwlwifi-5000-1.ucode > > iwlagn loaded firmware version 5.4.1.16 > > Oh, wait: my kernel is still requestiong the old firmware. I guess I should > upgrade my kernel too? To what version? > > (sorry for the confusion) Yes - the new firmware contains an API change, so a newer version of the driver is required. The change is in Linus's repo, but not in 2.6.30-rc7. You can thus grab Linus's repo or wait for his next release.
Running with Linus's tree from commit 3218911f839b6c85acbf872ad264ea69aa4d89ad + the version 2 firmware (reports 8.24.2.12 on startup), I am no longer able to reproduce the original "No space for TX" problem and the link seems to survive through all of the high bandwidth tests that I have tried so far on both the 2.4GHz and the 5GHz channels.