From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 01:15:58 2004 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1747E16A4CE; Sun, 11 Jan 2004 01:15:58 -0800 (PST) Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id B83C943D39; Sun, 11 Jan 2004 01:15:56 -0800 (PST) (envelope-from lorenzo@cisco.com) Received: from sj-core-3.cisco.com (171.68.223.137) by sj-iport-3.cisco.com with ESMTP; 11 Jan 2004 01:18:01 +0000 Received: from cisco.com (cypher.cisco.com [171.69.11.143]) by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id i0B9FrQu002718; Sun, 11 Jan 2004 01:15:53 -0800 (PST) Received: (from lorenzo@localhost) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id BAA13952; Sun, 11 Jan 2004 01:15:53 -0800 (PST) Date: Sun, 11 Jan 2004 01:15:53 -0800 From: Lorenzo Vicisano To: Marko Zec Message-ID: <20040111011553.A12385@cisco.com> References: <20040111003426.E0EF55D08@ptavv.es.net> <200401110229.46446.zec@tel.fer.hr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200401110229.46446.zec@tel.fer.hr> User-Agent: Mutt/1.3.23i cc: freebsd-net@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: prism 2.5 timeout in wi_cmd 0x010b X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2004 09:15:58 -0000 same result: the patch doesn't fix the problem. However after upgrding the Prism firmware (1.1.0 -> 1.1.1) the lock up stopped. Still I cannot get more that 2.5Mb/s Tx from the Prism (as a client) to another client (Aironet). A little better (3 / 3.5) from the Prism to the AP (DI 614+). "wi" is reporting a lot of TX collision, but "an" isn't when I change the direction of the traffic. In this case I get better rate.. but still not optimal as "wi" get conficts on the ACKs. Another anomaly shows up when running dhclient: often the system freezes/slows down for a few fractions of a second (BTW: I've noticed this with the Aironet driver as well). Also acquiring a lease has become more unreliable.. Lorenzo On Sun, Jan 11, 2004 at 02:29:46AM +0100, Marko Zec wrote: > On Sunday 11 January 2004 01:34, Kevin Oberman wrote: > > > > Marko, > > > > I just started re-building my kernel with this patch. I have > > previously reported this under CURRENT and hope that this might fix > > the problem. It has also been reported by several others under > > slightly different circumstances. I'll report what I see. It's pretty > > easy to test...just copy a multi-megabyte file from my laptop to my > > workstation over the wireless. > > > > Whoops... it seems that my hack doesn't fix the problem of outgoing > traffic hosing the wi interface - next time I'll do more testing before > making a post. However, without this patch my wi would lock up every > now and than out of the blue, regardless whether it was associated to > an AP or it was disconnected, and regardless whether there was any > traffic flowing through it or not. The same card (Prism 2.5 mini-PCI) > used to play nicely with 4.8-R, and works quite well with M$ also. > There must be something rotten in the recent wi driver... > > Cheers, > > Marko