Date: Tue, 27 Dec 2011 18:49:45 +0100 From: Martin Lesser <ml-freebsd-wireless@bettercom.de> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-wireless@freebsd.org Subject: Re: ath updates - please test Message-ID: <4EFA0539.2020508@bettercom.de> In-Reply-To: <CAJ-Vmok3ShR78uhjvK93msMmDgBHQv6WKc4sL0wGv=6zE3jRmg@mail.gmail.com> References: <CAJ-VmokdHhhUcyZ_2uDtZH233F9vRYJ0m2OrXaLdh662ghxgtg@mail.gmail.com> <4EF50AF4.3030105@bettercom.de> <CAJ-Vmok3ShR78uhjvK93msMmDgBHQv6WKc4sL0wGv=6zE3jRmg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi all, hi Adrian, on 24.12.2011 00:45 Adrian Chadd wrote: > Thanks for testing out -HEAD! Unfortunately the "stuck beacons" appeared again - not as much as in STABLE in the past but probably too much to ignore: Dec 25 10:20:18 fs kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 25 10:20:27 fs last message repeated 29 times Dec 25 10:20:27 fs kernel: ath0: ath_raw_xmit: sc_inreset_cnt > 0; bailing Dec 25 10:20:40 fs kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 25 10:20:51 fs last message repeated 36 times Dec 25 10:20:51 fs kernel: ath0: ath_raw_xmit: sc_inreset_cnt > 0; bailing I've set hw.ath.debug=2147483647 but I'm not sure whether that makes sense. Which debug-infos can I provide to help to get this bug out of the way? Are there plans to backport the actual /ath back to CURRENT? Additionally I ordered a D-Link DWA-547 [1] and hope not only to get rid of these stuck beacons but also to test 11n a little bit more. Cheers - Martin [1] http://www.wikidevi.com/wiki/D-Link_DWA-547
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EFA0539.2020508>