From owner-freebsd-current@FreeBSD.ORG Fri Mar 5 21:44:35 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 CF9E4106566C for ; Fri, 5 Mar 2010 21:44:35 +0000 (UTC) (envelope-from marcus@freebsd.org) Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by mx1.freebsd.org (Postfix) with ESMTP id 8C5B18FC0A for ; Fri, 5 Mar 2010 21:44:35 +0000 (UTC) X-TACSUNS: Virus Scanned Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id o25LiYAO017144 for ; Fri, 5 Mar 2010 16:44:34 -0500 (EST) Received: from dhcp-64-102-220-55.cisco.com (dhcp-64-102-220-55.cisco.com [64.102.220.55]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id o25LiY2S022945 for ; Fri, 5 Mar 2010 16:44:34 -0500 (EST) Message-ID: <4B917B42.1060900@freebsd.org> Date: Fri, 05 Mar 2010 16:44:34 -0500 From: Joe Marcus Clarke Organization: FreeBSD, Inc. User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: 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> <20100303231416.GN1295@weongyo> <1267679522.5324.20.camel@shumai.marcuscom.com> <20100305205349.GR1295@weongyo> In-Reply-To: <20100305205349.GR1295@weongyo> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: Problem with new bwn driver on -CURRENT 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: Fri, 05 Mar 2010 21:44:35 -0000 On 3/5/10 3:53 PM, Weongyo Jeong wrote: > On Thu, Mar 04, 2010 at 12:12:02AM -0500, Joe Marcus Clarke wrote: >> On Wed, 2010-03-03 at 15:14 -0800, Weongyo Jeong wrote: >>>> 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. >> >> Here you go. This is on -CURRENT from about 30 minutes ago. Thanks for >> looking into this. >> >> http://www.marcuscom.com/downloads/salami.dmesg > > Thank you for dmesg. It looks using PIO mode is only a way to avoid > this problem. > > I looked sources and problems of other Broadcom wireless driver for LP > PHY users. They also encounters this issue and are trying to solve > this but no luck and no perfect patch until now. > > Recently AFAIK wireless-test git of linux adopted a patch `gracefully > convert DMA to PIO mode' to solve it. > > Additionally some guys tolds some success story when they disabled ACPI > but it looks it's not a perfect solution. > > IIRC you said PIO worked for association with your AP but no further > traffic. However I wonder that this is weird for me because paths of > sending management frames and sending data frames are same. Could you > please recheck whether PIO mode worked? I'll try to test PIO mode on my > environment again. I can absolutely confirm PIO mode does NOT work with my card. I tested on a clean power-up. The card associates, but does not pass any traffic. I do not see the same decryption messages that I do with DMA mode. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome