From owner-freebsd-net@FreeBSD.ORG Wed Mar 19 12:35:40 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 2510B1065671; Wed, 19 Mar 2008 12:35:40 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) Received: from ipmail05.adl2.internode.on.net (ipmail05.adl2.internode.on.net [203.16.214.145]) by mx1.freebsd.org (Postfix) with ESMTP id 40F0C8FC29; Wed, 19 Mar 2008 12:35:39 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuAFADuk4Ed5LbaWWmdsb2JhbACBWo8fAR2Yfg X-IronPort-AV: E=Sophos;i="4.25,524,1199626200"; d="scan'208";a="79303087" Received: from ppp121-45-182-150.lns11.adl2.internode.on.net (HELO mail.clearchain.com) ([121.45.182.150]) by ipmail05.adl2.internode.on.net with ESMTP; 19 Mar 2008 23:05:38 +1030 Received: from [192.168.155.236] (taurus.internal.clearchain.com [192.168.155.236]) (authenticated bits=0) by mail.clearchain.com (8.14.2/8.14.2) with ESMTP id m2JCZCqJ064664 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Mar 2008 23:05:14 +1030 (CST) (envelope-from Benjamin.Close@clearchain.com) Message-ID: <47E1088A.8090203@clearchain.com> Date: Wed, 19 Mar 2008 23:05:22 +1030 From: Benjamin Close User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: Yousif Hassan 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: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.92.1, clamav-milter version 0.92.1 on pegasus.clearchain.com X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (mail.clearchain.com [192.168.154.1]); Wed, 19 Mar 2008 23:05:18 +1030 (CST) Cc: freebsd-net@freebsd.org, Sam Leffler , 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: Wed, 19 Mar 2008 12:35:40 -0000 Yousif Hassan wrote: > 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. The timeouts are related to the firmware not being able to reset the tx ring. Normally this isn't too bad as the first thing after resetting the tx rings is to stop the firmware and reinit it. Whilst it won't cause a crash, it still a bug that needs fixing. Cheers, Benjamin