Description of problem: About 70% of the time, the iwlagn driver fails to notice nearby networks when it scans. In these situations, it finds exactly one network (always the same one), and then never sees any of the other 12+ networks in range, including my own. How reproducible: This problem occurs 70% of the time. It doesn't seem to matter whether I've done a cold boot or a suspend/resume cycle. Usually, after six to ten driver rmmod/modprobe cycles, the driver will notice the nearby networks properly, and I can then associate to my AP successfully. However, there's about a 1/3 likelihood that the rmmod/modprobe cycles will cause the kernel to hang and require a hard (hold down the power button) reboot. I *suspect* that the AP that always gets detected when this problem occurs has had its transmit power boosted by its owner, but I've no idea how to verify that. Regardless, the fact that sometimes all other networks are seen and sometimes none are seen points to a driver bug. The end result of this is that because of the driver flakiness, constant fiddling, and forced reboots, it's more trouble than it's worth to me to ever suspend my laptop, which is both a shame and a waste of electricity. Steps to Reproduce: 1. Boot. 2. Log into Gnome. 3. Notice just one wireless network in the network picklist.
I've got a similar problem except that I see no wireless network at all. So I generally remove/reload iwlagn once and then it's ok untill next reboot.
I definitely see the "no networks" problem pretty often, but it's about as common for me to see just one of the dozen around me.
This problem also occurs on RawHide, except that we can see networks but can't authenticate... wlan0 direct probe responded wlan0: authenticate with AP 00:17:33:b0:3b:80 wlan0: authenticated wlan0: associate with AP 00:17:33:b0:3b:80 wlan0: RX AssocResp from 00:17:33:b0:3b:80 (capab=0x401 status=0 aid=1) wlan0: associated wlan0: disassociating by local choice (reason=3)
What are the kernel versions in use?
2.6.29.1-111.fc11.x86_64 for me.
after a couple of hours, nm-applet crash, and the errors below appeared in dmesg: E: hpet increasing min_delta_ns to 33750 nsec CE: hpet increasing min_delta_ns to 50624 nsec iwlagn: Read index for DMA queue txq_id (2) index 234 is out of range [0-256] 238 237 iwlagn: Read index for DMA queue txq_id (2) index 231 is out of range [0-256] 238 237 iwlagn: Read index for DMA queue txq_id (2) index 233 is out of range [0-256] 238 237 iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms. wlan0: No ProbeResp from current AP a6:b5:fa:f7:ac:c8 - assume out of range iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms. iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms. iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms. iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms. iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms. iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms. iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms. iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms. iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms. iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms. iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms. iwlagn: No space for Tx iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28 iwlagn: No space for Tx iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28 iwlagn: No space for Tx iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28 iwlagn: No space for Tx iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28 iwlagn: No space for Tx iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28 iwlagn: No space for Tx iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28 iwlagn: No space for Tx iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28 iwlagn: No space for Tx iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28 iwlagn: No space for Tx iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28 iwlagn: No space for Tx iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28 iwlagn: No space for Tx iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28 iwlagn: No space for Tx iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28 iwlagn: No space for Tx
For me, it's happened with every F-10 kernel. I'm currently running kernel-2.6.27.21-170.2.56.fc10.x86_64.
still having the "disassociating by local choice (reason=3)" problem on kernel 2.6.29.2-126.fc11.x86_64.
Please attach the output of 'lspci -n'. Also, the output of 'rpm -q iwl4965-firmware' and rpm -q iwl5000-firmware'...thanks!
Created attachment 343703 [details] output of "lspci -n" I've attached the lspci output. Firmware versions: iwl4965-firmware-228.57.2.23-2.noarch iwl5000-firmware-5.4.A.11-3.noarch
FWIW, this driver defaults to letting the device firmware handle scanning. There is an option to switch it back to doing scanning at the CPU (like most other mac80211-based drivers). Please drop a file into /etc/modprobe.d (e.g. /etc/modprobe.d/iwlagn.options) with a line in it like this: options iwlagn disable_hw_scan=1 After that, either execute 'modprobe -r iwlagn ; modprobe iwlagn' or simply reboot. Does this change/improve scanning behavior?
I now have "wlan0: deauthenticated (Reason: 6)" in dmesg with newly updated kernel 2.6.29.3-140.fc11.x86_64. I'm trying with /etc/modprobe.d/iwlagn.conf disabling the hw scan, it seems a little bit better. Hope it will also be more stable. Here is my pci/vendor id: 03:00.0 0280: 8086:4236 Firmware versions: iwl5000-firmware-5.4.A.11-4.noarch iwl4965-firmware-228.57.2.23-5.fc11.noarch
I've successfully associated three times in a row with hw scanning disabled, in the environment that's normally so problematic, and both scanning and associating seem to be much faster now too.
Firmware updates are available: yum --enablerepo=updates-testing update iwl4965-firmware iwl5000-firmware Do these updates improve the situation?
just had the same problem on F11 kernel-2.6.29.6-213. Do I have to try with updates-testing?
It doesn't seems to happen every time I boot on fedora. It was working with a fresh F11 install, but after updating and rebooting a few times NetworkManager failed to connect. After a modprobe -r iwlagn && modprobe iwlagn, I'm able to connect wireless networks.
Honestly, that sounds like a different issue...
I had the fails to scan networks problem before, now I always can scan the networks. So for this part of the problem (scanning networks) it seems to be OK for me. I should open a new bug for the iwlagn failing to associate networks.
John, I'll take a look at the updates tonight.
I've got the updated firmware running, but no news to report yet. (i.e. no discernible difference, due to insufficient thrashing around)
It's worked reliably for a few days in my environment where it usually has problems. I wouldn't exactly call this "data" yet, but it's something.
for me too, I can now transfer big files, which was impossible a few days ago. But this morning, it failed to associate again, had to reload iwlagn driver :(
Edouard: I think you and I have different problems. I never lose associations once they're made. I just wasn't able to see any more than 1 AP (always the same one) about 80% of the time.
Bryan, Is scanning ok with with recent F11 kernels/firmware? I would like to close this bug. Edouard, This bug: iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28 iwlagn: No space for Tx is not solved yet, even upstream. Fedora bug report is here: https://bugzilla.redhat.com/show_bug.cgi?id=493018 and Intel bugzilla entry here: http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2037 Please CC yourself and comment to help solve this problem.
Ok, according to previous comment this bug is fixed, closing it.