New hardware, old problem: stuck beacon when here is WiFi traffic

Lev Serebryakov lev at FreeBSD.org
Sun Apr 28 18:50:17 UTC 2013


Hello, Adrian.
You wrote 27 апреля 2013 г., 22:56:30:

AC> Anyway, leave it how it is for now. Just update to the latest -HEAD
AC> ath code and redo the testing. It will now log the whole TX queue
AC> contents, not just the completed frames. Hopefully it'll be more
AC> obvious.
  Ok, same test: UDP stream from AP to client (with iperf), limited to
 300M. Only 11-30M seen by client now, but no beacon stucks.
  After AP hangs several forced beacon stucks + hostaptd restart
 allow client to re-associate.

  Log with dev.ath.0.debug=0x900000020 attached ("sudo" messages are left as
 "time marks").

 --
// Black Lion AKA Lev Serebryakov <lev at FreeBSD.org>


More information about the freebsd-wireless mailing list