On Wed, Nov 4, 2009 at 4:30 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Tue, 2009-11-03 at 18:38 -0500, Andrew Lutomirski wrote: > >> iwlagn 0000:03:00.0: iwl_tx_agg_start on ra = 00:21:d8:49:4a:52 tid = 0 > >> Turning on or off power management and fiddling with >> no_sleep_autoadjust makes no difference. Setting tx_agg_tid_enable to >> zero in debugfs while the connection was working seemed to make it a >> little more reliable (it lasted long enough to do "git pull" but not >> much longer). >> >> After running "iw dev wlan0 disconnect" a few times, I start to get >> errors like this: >> >> [18078.209635] iwlagn 0000:03:00.0: SENSITIVITY_CMD failed >> [18078.313461] iwlagn 0000:03:00.0: No space for Tx >> [18078.313467] iwlagn 0000:03:00.0: Error sending SENSITIVITY_CMD: >> enqueue_hcmd failed: -28 >> [18078.313470] iwlagn 0000:03:00.0: SENSITIVITY_CMD failed >> [18078.522409] iwlagn 0000:03:00.0: No space for Tx >> [18078.522414] iwlagn 0000:03:00.0: Error sending SENSITIVITY_CMD: >> enqueue_hcmd failed: -28 > > Sounds like the firmware messes up ... > > Maybe as a first workaround you could modprobe iwlagn with > 11n_disable=1. But I don't know at this point what the problem could be. 11n_disable50=1 seems to work. I'll reply again if it stops working. Do the Intel folks have any ideas? Thanks, Andy -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
