From owner-freebsd-smp@FreeBSD.ORG Tue Aug 30 18:59:59 2005 Return-Path: X-Original-To: freebsd-smp@freebsd.org Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D871716A41F; Tue, 30 Aug 2005 18:59:59 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.village.org (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0F4643D53; Tue, 30 Aug 2005 18:59:57 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1]) by harmony.village.org (8.13.3/8.13.3) with ESMTP id j7UIx2mH062418; Tue, 30 Aug 2005 12:59:02 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 30 Aug 2005 12:59:25 -0600 (MDT) Message-Id: <20050830.125925.124085095.imp@bsdimp.com> To: jhb@freebsd.org From: "M. Warner Losh" In-Reply-To: <200508301422.46354.jhb@FreeBSD.org> References: <200508291157.26619.jhb@FreeBSD.org> <4313AD8E.7080906@paradise.net.nz> <200508301422.46354.jhb@FreeBSD.org> 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 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.village.org [127.0.0.1]); Tue, 30 Aug 2005 12:59:02 -0600 (MDT) Cc: freebsd-smp@freebsd.org, markir@paradise.net.nz Subject: Re: 6.0 BETA3 reboot hangs on SMP system if BIOS USB disabled X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 19:00:00 -0000 In message: <200508301422.46354.jhb@FreeBSD.org> John Baldwin writes: : On Monday 29 August 2005 08:51 pm, Mark Kirkwood wrote: : > John Baldwin wrote: : > > Ok, your BIOS is being a PITA. :) First off, can you try setting : > > 'hw.pci.enable_io_modes=0' from the loader and seeing if that fixes the : > > problem? : > : > Sure does, thanks for looking at this! : : Ok, don't go away. :) Warner or I can work on a patch to fix this then that : won't require you to set that tunable. I think that might be very hard to do that. While some (bogus) BIOSes set the maps to be all f's for devices they have disabled, many devices default to this value on power up. Since we have to perform lazy resource assignment for these devices, it may be difficult to differentiate between the unassigned case and the disabled case. Is there something I'm missing as to how we can tell the difference between these two cases? Warner