From owner-freebsd-stable@FreeBSD.ORG Thu Feb 2 08:58:02 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8829816A420 for ; Thu, 2 Feb 2006 08:58:02 +0000 (GMT) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5424643D48 for ; Thu, 2 Feb 2006 08:58:02 +0000 (GMT) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.12.11) with ESMTP id k128w0r2096376; Thu, 2 Feb 2006 00:58:00 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id k128w0tr096375; Thu, 2 Feb 2006 00:58:00 -0800 (PST) (envelope-from rizzo) Date: Thu, 2 Feb 2006 00:58:00 -0800 From: Luigi Rizzo To: stable@freebsd.org Message-ID: <20060202005800.D95993@xorpc.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Cc: Subject: frequent freeze on 6.0-STABLE at startup when loading iwi firmware X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2006 08:58:02 -0000 yesterday upgraded my laptop (Dell X1 with iwi wireless card) running 6.0 to a fresh version of stable and the newest iwi-firmware, and since then it frequently hangs at boot time right after loading the iwi firmware - in fact, it booted ok only 2 times out of the last 10. The last msg i see on the console is Starting iwi [iwi0:bss] and then i have to reset the machine. With the previous firmware it never hung, but i don;t know if it is the microcode or the loading mechanism that has changed. The workaround i have found is to disable iwi in /etc/rc.conf and then start it later, manually. Obviously, this is suboptimal. I am not sure what to look at, a race somewhere that could be fixed adding some 'sleep' before or after loading the microcode ? something else ? if that matters, there is an access point active where i boot, and the config command tell the card the parameters to associate with it. cheers luigi