From owner-freebsd-current@FreeBSD.ORG Fri Mar 5 20:53:53 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 49F3B106566B; Fri, 5 Mar 2010 20:53:53 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.26]) by mx1.freebsd.org (Postfix) with ESMTP id 9EA108FC08; Fri, 5 Mar 2010 20:53:52 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id 25so640502eya.9 for ; Fri, 05 Mar 2010 12:53:45 -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=Tr613J3pvrI4dW52Wrq0LTkglNXGIb+4lmQiT4g8MAA=; b=KDPL8jneEGnQfbTQtS4V18eItIJrGxdhhM9lT1s6qUlslW4qjsWjV6J+KkeKagaYfT rkos7EW8lX4sJEJPe62E3ol3toM0DLjqT/2q7pr096o5zPrvt317doVjRscOUWbf0fg1 AZ4cJA1Azrz13OD09/pm2f7SKe1hko3DHLcxs= 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=pR66JAA2i0kePY+anGu3cOraNOaELHLhzTR3ggPec5o3+9yErV/nA5PqCZvOrRMEuK /GSYTovg7qJmHgR/TWhDHsvBfwceDIptD0W758RkRVhE5PnjpQyMXK+CjZrm6YheWyKx xJG88TAykN/yhDHcR6Ai0AbD8G9DJlDhEin6M= Received: by 10.213.0.212 with SMTP id 20mr817533ebc.41.1267822425749; Fri, 05 Mar 2010 12:53:45 -0800 (PST) Received: from weongyo ([174.35.1.224]) by mx.google.com with ESMTPS id 15sm1248158ewy.4.2010.03.05.12.53.43 (version=SSLv3 cipher=RC4-MD5); Fri, 05 Mar 2010 12:53:44 -0800 (PST) Received: by weongyo (sSMTP sendmail emulation); Fri, 5 Mar 2010 12:53:49 -0800 From: Weongyo Jeong Date: Fri, 5 Mar 2010 12:53:49 -0800 To: Joe Marcus Clarke Message-ID: <20100305205349.GR1295@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> <20100303231416.GN1295@weongyo> <1267679522.5324.20.camel@shumai.marcuscom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1267679522.5324.20.camel@shumai.marcuscom.com> 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: Fri, 05 Mar 2010 20:53:53 -0000 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. regards, Weongyo Jeong