From owner-freebsd-net@FreeBSD.ORG Fri Mar 14 13:53:11 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24BCC106566B for ; Fri, 14 Mar 2008 13:53:11 +0000 (UTC) (envelope-from yousif@alumni.jmu.edu) Received: from coruscant.far-far-away.com (coruscant.far-far-away.us [70.91.196.65]) by mx1.freebsd.org (Postfix) with SMTP id C2F6F8FC26 for ; Fri, 14 Mar 2008 13:53:10 +0000 (UTC) (envelope-from yousif@alumni.jmu.edu) Received: (qmail 19968 invoked from network); 14 Mar 2008 09:47:02 -0400 Received: from unknown (HELO alderaan) (68.162.198.134) by coruscant.far-far-away.us with SMTP; 14 Mar 2008 09:47:02 -0400 Message-ID: From: "Yousif Hassan" To: "Benjamin Close" , "Sam Leffler" References: <47C078EC.4020907@student.utwente.nl> <200802241730.13328.fbsd.questions@rachie.is-a-geek.net> <47D63A65.8010507@clearchain.com> <200803111356.00400.fbsd.questions@rachie.is-a-geek.net> <47D68808.5060709@student.utwente.nl><47D6FB5B.3020107@clearchain.com><1205366956.2082.13.camel@localhost> <47D88DC0.1010903@freebsd.org> <47D9A5E3.1020900@clearchain.com> In-Reply-To: <47D9A5E3.1020900@clearchain.com> Date: Fri, 14 Mar 2008 09:54:36 -0400 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Mail 6.0.6000.16480 X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16545 Cc: freebsd-net@freebsd.org, Mel , Alphons Fonz van Werven , freebsd-mobile@freebsd.org Subject: Re: [Wireless] Can't connect to wlan X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Mar 2008 13:53:11 -0000 Benjamin Close wrote: > Sam Leffler wrote: >> Yousif Hassan wrote: >>> On Wed, 2008-03-12 at 08:06 +1030, Benjamin Close wrote: >>> >>> The slightly wonky: >>> - As reported by someone else: >>> wpi0: timeout resetting Tx ring 1 >>> wpi0: timeout resetting Tx ring 3 >>> wpi0: timeout resetting Tx ring 4 >>> appear on startup and occasionally on kldload - however they don't >>> appear to adversely affect too much >> >> wpi doesn't yet support background scan so doing an explicit scan from >> the command line will disconnect you from any ap you care connected to. >> It shouldn't be hard to add bgscan--but that's easy for me to say :) >> > It's certainly on my todo list! Thanks for reminding me about the bgscan thing. I had read that somewhere before and completely forgotten! Ben, are the wpi0: timeout resetting Tx ring 1 wpi0: timeout resetting Tx ring 3 wpi0: timeout resetting Tx ring 4 (and other variants thereof) messages anything to be concerned about? It doesn't seem to affect stuff but it does show up on initial startup and every other scan I do. Thanks to everyone who worked on wpi for a most excellent driver. --Y