From owner-freebsd-current@FreeBSD.ORG Wed Mar 3 23:14:21 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91075106564A; Wed, 3 Mar 2010 23:14:21 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: from mail-qy0-f183.google.com (mail-qy0-f183.google.com [209.85.221.183]) by mx1.freebsd.org (Postfix) with ESMTP id 2BC278FC0C; Wed, 3 Mar 2010 23:14:20 +0000 (UTC) Received: by qyk14 with SMTP id 14so1942456qyk.9 for ; Wed, 03 Mar 2010 15:14:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent:organization:x-operation-sytem; bh=Y5yA4OH/FwwgR3DycvS7zFkemS8piSWiiHAte6/msoY=; b=JWUU2ol24e2EVZCbFdrTALHfJBs3CAVQrHPFX6BNJ/ouHEJkfdTQBcIyYxJdKOEEm3 CBvEv42Qa6ooC01Z94A97iNxgAzdGFyv/sxV7FSN0yzahxEBa79BULiEPYBCJgbaIAwi UWpENDS5TwPrWAQV7IJ6ZbqwvAgWioIM55C5Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:mail-followup-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent:organization:x-operation-sytem; b=fdF/Jg2mwE7IG1RiWIDyphBIPJ6/sHQH9WHbGD8XeYI/yuWPEwQK0E1IzH4Cuh8oeN CcgFgJbaAUkSPjsFSrW/edeuPLeIEzNc5TB5Oryx35k5OBE/OXL2VzVvi1IPKbBxflXx IBUekF8r+P/40HMoSN0sGdBaLadvoBoi0chBo= Received: by 10.224.87.68 with SMTP id v4mr232047qal.192.1267658052920; Wed, 03 Mar 2010 15:14:12 -0800 (PST) Received: from weongyo ([174.35.1.224]) by mx.google.com with ESMTPS id 5sm16867789qwg.3.2010.03.03.15.14.12 (version=SSLv3 cipher=RC4-MD5); Wed, 03 Mar 2010 15:14:12 -0800 (PST) Received: by weongyo (sSMTP sendmail emulation); Wed, 3 Mar 2010 15:14:16 -0800 From: Weongyo Jeong Date: Wed, 3 Mar 2010 15:14:16 -0800 To: Joe Marcus Clarke Message-ID: <20100303231416.GN1295@weongyo> Mail-Followup-To: Joe Marcus Clarke , current References: <1267388668.39569.2410.camel@shumai.marcuscom.com> <20100301233706.GH1295@weongyo> <1267505443.35639.9.camel@shumai.marcuscom.com> <20100303220452.GL1295@weongyo> <4B8EE6B1.6030605@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B8EE6B1.6030605@freebsd.org> User-Agent: Mutt/1.4.2.3i Organization: CDNetworks. X-Operation-Sytem: FreeBSD Cc: current Subject: Re: Problem with new bwn driver on -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Weongyo Jeong List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Mar 2010 23:14:21 -0000 On Wed, Mar 03, 2010 at 05:46:09PM -0500, Joe Marcus Clarke wrote: > On 3/3/10 5:04 PM, Weongyo Jeong wrote: > > On Mon, Mar 01, 2010 at 11:50:43PM -0500, Joe Marcus Clarke wrote: > >> On Mon, 2010-03-01 at 15:37 -0800, Weongyo Jeong wrote: > >>> On Sun, Feb 28, 2010 at 03:24:28PM -0500, Joe Marcus Clarke wrote: > >>>> I was extremely pleased to see this driver, so I could get off of the > >>>> flaky NDIS version. I have a Dell Vostra 2510 with a LP bwn mini-PCI > >>>> card. I have set if_bwn_load="YES" in /boot/loader.conf. I also have > >>>> bwn_v4_lp_ucode_load="YES" set. > >>>> > >>>> The firmware and driver loads. However, if_bwn doesn't attach to the > >>>> card. Once the OS is fully booted, I kldunload if_bwn, then reload it, > >>>> and the driver attaches just fine. > >>> > >>> This issue is reported by some people and I'm looking codes. > >> > >> Good to know. > > > > This issue is solved in r204657. Thank you for reporting! > > Saw that, thanks! > > > >>>> bwn0: out of bounds of the square-root table (-770884) > >>>> bwn0: out of bounds of the square-root table (-225625) > >>>> bwn0: out of bounds of the square-root table (-240100) > >>> > >>> Patch is attached with email and it'll fix this message. Could you > >>> please test with it? > >> > >> Yes, the patch removes those messages. Thanks! > > Was this patch committed? I don't recall seeing an svn notice. Yes at r204542. > > >> > >>> > >>> Was it successful to associate with AP? > >> > >> Yes, in DMA mode. In PIO mode, it associates, but does not pass any > >> traffic. After a while, there was a critical DMA error, and the driver > >> looped forever trying to communicate with the card. > > > > Are there any messages from bwn(4) related with DMA error? If yes and > > you reproduce DMA error easily could you please show me the full dmesg? > > When it occurs, it is a fatal DMA error, and this streams on the console > until reboot. In order to get the card to work again (with either bwn > or ndis), I need to power-cycle the laptop. > > When it occurs again, I will get you the details and the full dmesg. Do > you want a verbose dmesg, or a standard one? I think a standard one is enough. Thank you. regards, Weongyo Jeong