Bug 148322 - [ath] Triggering atheros wifi beacon misses in hostap mode under no radio traffic load
Summary: [ath] Triggering atheros wifi beacon misses in hostap mode under no radio tra...
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: 9.0-CURRENT
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-wireless (Nobody)
Depends on:
Reported: 2010-07-02 17:40 UTC by Adrian Chadd
Modified: 2018-05-28 19:46 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Adrian Chadd freebsd_committer 2010-07-02 17:40:04 UTC
Reproducing "missed x consecutive beacon" debug messages by doing SPI flash IO.

This isn't -necessarily- a radio stability/signal strength issue (but I'll
re-test that comment when I acquire something spectrum analyzer-y) but it
could indicate some other problem. The flash IO is through the AR71XX SPI bus.
It shouldn't interfere with the beacon transmission, right?


Weirdly enough, tweaking the HAL DMA/software beacon timings quieten those messages:

# sysctl hw.ath.hal.dma_brt=1000
# sysctl hw.ath.hal.sw_brt=3000
# ifconfig wlan0 down
#ifconfig wlan0 up
# dd if=/dev/redboot/kernel of=/dev/null bs=64k

I haven't tried passing any traffic through the AP yet with these HAL settings.

100/300 also works. Dropping it back to the default of 2/10 sees the missed beacon messages.
* setup interface in hostap mode:

create_args_wlan0="wlanmode hostap mode 11g country AU txpower 2 bgscan"
ifconfig_wlan0="ssid cacheboy_test_1 mode 11g channel 6 txpower 2 up"

* create hostapd config to make sure neighbors don't steal wifi:

wpa_pairwise=CCMP TKIP

* create bridge group just for testing normal traffic:

ifconfig_bridge0="addm wlan0 stp wlan0 addm wlan1 stp wlan1 addm arge0 stp arge0 up"

* enable beacon debug messages (assuming the kernel has been compiled with atheros debugging):

# sysctl dev.ath.0.debug=0x80

* dd from flash:
wap1# dd if=/dev/redboot/kernel of=/dev/null bs=64k
ath0: ath_beacon_proc: missed 1 consecutive beacons
ath0: ath_beacon_proc: resume beacon xmit after 1 misses
ath0: ath_beacon_proc: missed 1 consecutive beacons
ath0: ath_beacon_proc: resume beacon xmit after 1 misses
<etc, etc>
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2010-07-03 12:16:04 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-net

Over to maintainer(s).
Comment 2 dfilter service freebsd_committer 2010-09-09 23:28:07 UTC
pgollucci    2010-09-09 22:28:03 UTC

  FreeBSD ports repository

  Modified files:
    devel                Makefile 
  Added files:
    devel/pecl-xhprof    Makefile distinfo pkg-descr 
  XHProf is a function-level hierarchical profiler for PHP and has a simple HTML
  based navigational interface. The raw data collection component is implemented
  in C (as a PHP extension). The reporting/UI layer is all in PHP. It is capable
  of reporting function-level inclusive and exclusive wall times, memory usage,
  CPU times and number of calls for each function. Additionally, it supports
  ability to compare two runs (hierarchical DIFF reports), or aggregate results
  from multiple runs.
  WWW: http://pecl.php.net/package/xhprof/
  PR:             ports/148322
  Submitted by:   Conor McDermottroe <ports at mcdermottroe.com>
  Revision  Changes    Path
  1.4037    +1 -0      ports/devel/Makefile
  1.1       +24 -0     ports/devel/pecl-xhprof/Makefile (new)
  1.1       +3 -0      ports/devel/pecl-xhprof/distinfo (new)
  1.1       +9 -0      ports/devel/pecl-xhprof/pkg-descr (new)
cvs-all@freebsd.org mailing list
To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
Comment 3 Adrian Chadd freebsd_committer 2011-04-11 12:41:05 UTC
Responsible Changed
From-To: freebsd-net->freebsd-wireless

punt to mailing list
Comment 4 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:46:46 UTC
batch change:

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


Reset to open status.

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.