From owner-freebsd-current@FreeBSD.ORG Sat Sep 3 04:01:22 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98F7E16A41F for ; Sat, 3 Sep 2005 04:01:22 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39E5E43D45 for ; Sat, 3 Sep 2005 04:01:22 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.89] ([66.127.85.89]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id j8341KBd094585 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Sep 2005 21:01:21 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <4319200A.2010702@errno.com> Date: Fri, 02 Sep 2005 21:01:14 -0700 From: Sam Leffler User-Agent: Mozilla Thunderbird 0.8 (X11/20041021) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vitaly References: <430060FB.1000405@tikhvin.info> <4314537C.5050808@tikhvin.info> <4314A32A.9050105@errno.com> <43183E7D.50802@tikhvin.info> In-Reply-To: <43183E7D.50802@tikhvin.info> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: ath bridge panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2005 04:01:22 -0000 Vitaly wrote: > >> >> Still exists with what version of the system? If you haven't tried >> BETA3 then do that first. >> >> To get something like this fixed you need to provide the steps needed >> to reproduce the problem. >> > I tried BETA3, while client authentification in progress i get error > messages but after all ok without panic Sorry but I do not understand "while cleint authentication in progress". Is this an ap? Where is the configuration? What client is this? > > ath0: device timeout > ath0: device timeout > ath0: device timeout > ath0: device timeout These should not happen. > couldn't m_pullup > couldn't m_pullup > couldn't m_pullup > couldn't m_pullup > couldn't m_pullup Haven't a clue where these msgs come from. > .... > > but i have another problem here - 80211b PDA client success communicates > with another 80211g client, but not with 80211b client > what debug modes i must set to athdebug to view activity with this problem > ath is the wrong level to look for problems; look at the net80211 level. I have a number of changes in current that have yet to be MFC'd to RELENG_6 for ap operation so they may help you. Also I'm aware that 11g ap operation is not right for a mixed-bss. The ap does not announce a revised ERP information element in the beacons when non-ERP stations join/leave the bss so a mixed station bss may not function correctly due to inconsistent setup of preamble and/or protection. No eta on when that'll be fixed; it's easy but my time is limited right now. Sam