Bug 146425 - [mwl] mwl dropping all packets during and after high usage on 802.11n
Summary: [mwl] mwl dropping all packets during and after high usage on 802.11n
Status: Closed Feedback Timeout
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-wireless (Nobody)
URL:
Keywords:
Depends on:
Blocks: 277512
  Show dependency treegraph
 
Reported: 2010-05-09 07:10 UTC by Erik Fonnesbeck
Modified: 2024-06-08 01:26 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Fonnesbeck 2010-05-09 07:10:02 UTC
When using the card in 802.11n in access point mode, testing with file copying to or from a Windows system with an 802.11n card (specifically an Atheros 5416-based card in this card) with the other endpoint being accessed over 100 Mbps ethernet, after a short time it started to drop all packets, even after the transfer was stopped.  Before the packet loss, the transfer is typically far below 802.11g's fastest rate.

Fix: 

If ampdu is disabled, the packet loss does not occur.  After that it can also at least reach, but not exceed, 802.11g rates.
How-To-Repeat: Use mwl as 802.11n access point and copy a file over the network without a speed cap set.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2010-05-10 05:17:06 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-net

Over to maintainer(s).
Comment 2 Adrian Chadd freebsd_committer freebsd_triage 2012-04-30 07:02:18 UTC
Responsible Changed
From-To: freebsd-net->freebsd-wireless

Switch over
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:47:33 UTC
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.
Comment 4 Bjoern A. Zeeb freebsd_committer freebsd_triage 2024-03-05 21:26:30 UTC
Is this still a setup you are running and did one and a half decades ago anyone think this mwl or our 11n implementation?
Comment 5 Bjoern A. Zeeb freebsd_committer freebsd_triage 2024-06-08 01:26:16 UTC
I am really sorry no one looked into this back then.
I'll close it as I can no longer track all the 11n changes which may or may not have affected this.

In the unlikely case you still have this setup and can still reproduce it, please re-open the PR.