From owner-freebsd-current@FreeBSD.ORG Thu Dec 16 08:58:21 2004 Return-Path: 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 1D5CB16A4CE for ; Thu, 16 Dec 2004 08:58:21 +0000 (GMT) Received: from smtp814.mail.ukl.yahoo.com (smtp814.mail.ukl.yahoo.com [217.12.12.204]) by mx1.FreeBSD.org (Postfix) with SMTP id 4B67543D49 for ; Thu, 16 Dec 2004 08:58:20 +0000 (GMT) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: from unknown (HELO w2fzz0vc01.aah-go-on.com) (thomas.sparrevohn@hg1.btinternet.com@81.157.165.214 with plain) by smtp814.mail.ukl.yahoo.com with SMTP; 16 Dec 2004 08:58:19 -0000 From: Thomas Sparrevohn To: freebsd-current@freebsd.org Date: Thu, 16 Dec 2004 08:57:54 +0000 User-Agent: KMail/1.7.1 References: <41BBA812.2030006@errno.com> <1103166432.995.15.camel@RabbitsDen> <20041216082355.GA58798@webcom.it> In-Reply-To: <20041216082355.GA58798@webcom.it> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412160857.54669.Thomas.Sparrevohn@btinternet.com> Subject: Re: WEP and 802.11 drivers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Thomas.Sparrevohn@btinternet.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Dec 2004 08:58:21 -0000 On Thursday 16 December 2004 08:23, Andrea Campi wrote: > On Wed, Dec 15, 2004 at 10:07:12PM -0500, Alexandre Sunny Kovalenko wrote: > > Since adding wlan_wep to the kernel config, I do not have traps and > > double faults, but neither I have wireless connectivity -- card gets > > configured and claims to associate, occasionally I even get as far as > > obtaining address via DHCP, but that is all I can get. Intermittently I > > get 'host is down' from ping. At that point, ifconfig would show > > 'status' as 'no carrier'. > > Try playing with /usr/src/tools/tools/ath/80211debug and set different > flags until you get some more info. If you see it whining about invalid > transitions from INIT -> RUN, you are seeing the same issue I am. > Sam didn't reply to an email about this, so might be either too busy > or not interested on fixing wi (although at least a reply to that effect > would be nice). I'll probably start debugging this during the holidays, > or I'll have to go back to 5.STABLE, which I would hate. > > Bye, > Andrea When I don't get a double fault - I can get it up and running but see exactly that ieee80211_newstate: INIT -> INIT wi_newstate: INIT -> INIT ieee80211_newstate: INIT -> INIT wi_info_intr: LINK_STAT 0x1 wi_newstate: INIT -> RUN ieee80211_newstate: INIT -> RUN ieee80211_newstate: invalid transition I can reproduce it - However most of the time I still get a double fault in the arc4rand call to mtx_lock_flags - after looking at the wep_attach code which seems to be fine - I am beginning to think that it most be something else