From owner-freebsd-mobile@FreeBSD.ORG  Sun Jan 11 13:24:37 2004
Return-Path: <owner-freebsd-mobile@FreeBSD.ORG>
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 7930E16A4CE; Sun, 11 Jan 2004 13:24:37 -0800 (PST)
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id B278043D1D; Sun, 11 Jan 2004 13:24:35 -0800 (PST)
	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.12.10/8.12.9) with ESMTP id i0BLOXET042436;
	Sun, 11 Jan 2004 14:24:34 -0700 (MST)
	(envelope-from imp@bsdimp.com)
Date: Sun, 11 Jan 2004 14:23:57 -0700 (MST)
Message-Id: <20040111.142357.50578253.imp@bsdimp.com>
To: lorenzo@vicisano.net
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20040111011553.A12385@cisco.com>
References: <20040111003426.E0EF55D08@ptavv.es.net>
	<200401110229.46446.zec@tel.fer.hr>
	<20040111011553.A12385@cisco.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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 <freebsd-mobile.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mobile>,
	<mailto:freebsd-mobile-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-mobile>
List-Post: <mailto:freebsd-mobile@freebsd.org>
List-Help: <mailto:freebsd-mobile-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mobile>,
	<mailto:freebsd-mobile-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Jan 2004 21:24:37 -0000

In message: <20040111011553.A12385@cisco.com>
            Lorenzo Vicisano <lorenzo@vicisano.net> writes:
: However after upgrding the Prism firmware (1.1.0 -> 1.1.1)
: the lock up stopped.

You really really really want to be using 1.4.5 firmware.  Older
firmware is known to be buggy.

Warner