From owner-freebsd-current@FreeBSD.ORG Sat Jan 17 06:11:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DECBF16A4CE for ; Sat, 17 Jan 2004 06:11:29 -0800 (PST) Received: from users.altadena.net (users.altadena.net [207.151.161.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59FD943D53 for ; Sat, 17 Jan 2004 06:11:29 -0800 (PST) (envelope-from pete@users.altadena.net) Received: from pete by users.altadena.net with local (Exim 4.30) id 1AhrAf-0007PM-1m for current@freebsd.org; Sat, 17 Jan 2004 06:11:29 -0800 Date: Sat, 17 Jan 2004 06:11:29 -0800 From: Pete Carah To: current@freebsd.org Message-ID: <20040117141129.GA28446@users.altadena.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Sender: Pete Carah X-Mailman-Approved-At: Sat, 17 Jan 2004 11:45:54 -0800 Subject: allow_unsupported_io_range X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2004 14:11:30 -0000 Someone removed (or changed) "hw.pci.allow_unsupported_io_range". This breaks LOTS of laptops, in particular the pccard hardware. Causes a hang after init is started... -- Pete