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 :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
