Date: Mon, 18 Jan 2010 18:33:23 +1100 From: Graham Menhennitt <graham@menhennitt.com.au> To: Sam Leffler <sam@errno.com>, FreeBSD stable <freebsd-stable@freebsd.org> Subject: Re: ath hostap problems Message-ID: <4B540EC3.7040506@menhennitt.com.au> In-Reply-To: <4B522102.1050805@errno.com> References: <0122e9480533dc61e94ec7d00678aeaf.squirrel@lamneth> <0c682ad7769fbd678a6835f041d0c791.squirrel@lamneth> <4B522102.1050805@errno.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sam Leffler wrote: > Are both machines SMP? Stuck beacons typically arise for two reasons: > the channel is busy and the ap can't get on the air to send the frame, > or the host/bus is overloaded and cannot meet the realtime > requirements of posting the beacon frame in time to hit the beacon > transmit schedule. I can't tell from the above info whether either > might be possible. Sam, I'm having a similar problem with the "stuck beacon" message (see my request at http://www.mail-archive.com/freebsd-stable@freebsd.org/msg107619.html). What info do you need to be able to diagnose it? Thanks for any help, Graham Menhennitt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B540EC3.7040506>