From owner-freebsd-stable@FreeBSD.ORG Mon Jan 18 07:33:27 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE2C6106568B for ; Mon, 18 Jan 2010 07:33:27 +0000 (UTC) (envelope-from graham@menhennitt.com.au) Received: from mail01.syd.optusnet.com.au (mail01.syd.optusnet.com.au [211.29.132.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4C3578FC20 for ; Mon, 18 Jan 2010 07:33:26 +0000 (UTC) Received: from maxwell.mencon.com.au (c122-107-224-152.eburwd5.vic.optusnet.com.au [122.107.224.152]) by mail01.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id o0I7XIH3001723; Mon, 18 Jan 2010 18:33:20 +1100 Received: from [203.2.73.73] (chief.mencon.com.au [203.2.73.73]) by maxwell.mencon.com.au (Postfix) with ESMTP id AE20E5D4E; Mon, 18 Jan 2010 18:33:09 +1100 (EST) Message-ID: <4B540EC3.7040506@menhennitt.com.au> Date: Mon, 18 Jan 2010 18:33:23 +1100 From: Graham Menhennitt User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Sam Leffler , FreeBSD stable References: <0122e9480533dc61e94ec7d00678aeaf.squirrel@lamneth> <0c682ad7769fbd678a6835f041d0c791.squirrel@lamneth> <4B522102.1050805@errno.com> In-Reply-To: <4B522102.1050805@errno.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: ath hostap problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jan 2010 07:33:27 -0000 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