From: Andrew Lutomirski <luto@mit.edu>
To: linux-wireless@vger.kernel.org, ilw@linux.intel.com
Subject: iwlwifi connection troubles, maybe aggregation related
Date: Tue, 3 Nov 2009 18:38:57 -0500 [thread overview]
Message-ID: <cb0375e10911031538n62fe7473x4dd41329b9264b5c@mail.gmail.com> (raw)
Hi all-
My laptop (Intel 5350) has trouble using the wireless networks here.
I'm at MIT, which has a bunch of Cisco 1250 AP's (dual-band, MIMO,
etc). Running Windows, everything works perfectly. On Linux
(2.6.31-rc5, but I've seen problems with other, older kernels as
well), it sometimes works, but I frequently find the network almost
completely unusable. I can associate and ping just fine, but, as soon
as I try to send any significant amount of data, I can no longer
transmit. I can still receive both broadcast and unicast frames, but
the network doesn't see anything I send. An older laptop (presumably
with 4965,
This seems to be correlated with a line like:
iwlagn 0000:03:00.0: iwl_tx_agg_start on ra = 00:21:d8:49:4a:52 tid = 0
appearing in dmesg.
Running "iw dev wlan0 disconnect" will make the connection start
working until I try to send data again (presumably because either NM
or wpa_supplicant will reassociate).
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
The driver doesn't recover until I do "echo 1 >
/sys/kernel/debug/ieee80211/phy0/reset" Oddly enough, after resetting
just now, I couldn't trigger the failure again, even though it was
100% reproducible before resetting.
Thanks,
Andy
next reply other threads:[~2009-11-03 23:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 23:38 Andrew Lutomirski [this message]
2009-11-04 1:47 ` iwlwifi connection troubles, maybe aggregation related Greg Oliver
2009-11-04 9:30 ` Johannes Berg
2009-11-04 10:59 ` Greg Oliver
2009-11-04 11:32 ` Greg Oliver
2009-11-06 19:45 ` Andrew Lutomirski
2009-11-17 22:03 ` Andrew Lutomirski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cb0375e10911031538n62fe7473x4dd41329b9264b5c@mail.gmail.com \
--to=luto@mit.edu \
--cc=ilw@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox