Date: Sun, 07 Mar 2010 00:05:43 -0500 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Weongyo Jeong <weongyo@freebsd.org> Cc: current <current@freebsd.org> Subject: Re: Problem with new bwn driver on -CURRENT Message-ID: <1267938343.96436.9.camel@shumai.marcuscom.com> In-Reply-To: <20100306001656.GS1295@weongyo> 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> <4B917B42.1060900@freebsd.org> <20100306001656.GS1295@weongyo>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-Y+8pNrll7JNQaHmZYowB Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable On Fri, 2010-03-05 at 16:16 -0800, Weongyo Jeong wrote: > On Fri, Mar 05, 2010 at 04:44:34PM -0500, Joe Marcus Clarke wrote: > > 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 dmes= g. 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 > > >=20 > > > Thank you for dmesg. It looks using PIO mode is only a way to avoid > > > this problem. > > >=20 > > > I looked sources and problems of other Broadcom wireless driver for L= P > > > PHY users. They also encounters this issue and are trying to solve > > > this but no luck and no perfect patch until now. > > >=20 > > > Recently AFAIK wireless-test git of linux adopted a patch `gracefully > > > convert DMA to PIO mode' to solve it. > > >=20 > > > Additionally some guys tolds some success story when they disabled AC= PI > > > but it looks it's not a perfect solution. > > >=20 > > > 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 yo= u > > > please recheck whether PIO mode worked? I'll try to test PIO mode on= my > > > environment again. > >=20 > > 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. >=20 > OK. I'd like to see some verbose message from bwn(4) after applying > attached patch with email. Could you please test with it and show me > dmesg? >=20 > I tested 3 broadcom card whose revisions are 5 and 9 and it looks it's > working. >=20 > I have one LP PHY device, half MiniPCI-E for laptop, but could not test > with this patch because I could not turn on RF; it's connected with > desktop using converter MiniPCI-E to PCI-E though normally it looks > MiniPCI-E devices are turned on using H/W RF switch. Here are two dmesg outputs. Both were taken with this patch. One is with PIO mode, and the other is with (working) DMA mode. The names indicate which is which. http://www.marcuscom.com/downloads/salami_pio.dmesg http://www.marcuscom.com/downloads/salami_dma.dmesg Joe --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-Y+8pNrll7JNQaHmZYowB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEABECAAYFAkuTNCYACgkQb2iPiv4Uz4c8KQCgn+DEXTQcyMygA4P40tcuccCe ba0AoKrNiDVO89xtsbHOb740QCHD/Ic2 =xVdq -----END PGP SIGNATURE----- --=-Y+8pNrll7JNQaHmZYowB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1267938343.96436.9.camel>