From owner-freebsd-mobile@FreeBSD.ORG  Thu Jul 22 16:00:15 2004
Return-Path: <owner-freebsd-mobile@FreeBSD.ORG>
Delivered-To: freebsd-mobile@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1E53E16A4CE
	for <freebsd-mobile@freebsd.org>;
	Thu, 22 Jul 2004 16:00:14 +0000 (GMT)
Received: from psg.com (psg.com [147.28.0.62])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D622743D45
	for <freebsd-mobile@freebsd.org>;
	Thu, 22 Jul 2004 16:00:14 +0000 (GMT)	(envelope-from randy@psg.com)
Received: from [127.0.0.1] (helo=roam.psg.com)
	by psg.com with esmtp (Exim 4.34 (FreeBSD))
	id 1BnfzO-000DXo-Ek
	for freebsd-mobile@freebsd.org; Thu, 22 Jul 2004 16:00:10 +0000
Received: from localhost ([127.0.0.1] helo=roam.psg.com.psg.com)
	by roam.psg.com with esmtp (Exim 4.40 (FreeBSD))
	id 1BnfzN-0002sx-OO
	for freebsd-mobile@freebsd.org; Thu, 22 Jul 2004 06:00:09 -1000
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16639.58504.930740.337742@roam.psg.com>
Date: Thu, 22 Jul 2004 06:00:08 -1000
To: FreeBSD Laptoppers <freebsd-mobile@freebsd.org>
Subject: ath0 associaiton failure
X-BeenThere: freebsd-mobile@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Mobile computing with FreeBSD <freebsd-mobile.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mobile>,
	<mailto:freebsd-mobile-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-mobile>
List-Post: <mailto:freebsd-mobile@freebsd.org>
List-Help: <mailto:freebsd-mobile-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mobile>,
	<mailto:freebsd-mobile-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jul 2004 16:00:15 -0000

on my freebsd very current, every few minutes the ath0 drops out
and then, after a few seconds, recovers.  the log message is

    ath0: association failed (reason 1) for 00:0f:66:04:c0:2f

my partner, running xp against the same base station, sees no 
symptoms.

clues and/or debugging hints sought

randy