From owner-freebsd-acpi@FreeBSD.ORG Mon May 23 08:32:12 2011 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFA23106566C for ; Mon, 23 May 2011 08:32:12 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 401BE8FC1C for ; Mon, 23 May 2011 08:32:11 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA06842; Mon, 23 May 2011 11:12:47 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QOQFr-0003Mj-NK; Mon, 23 May 2011 11:12:47 +0300 Message-ID: <4DDA16FF.8080802@FreeBSD.org> Date: Mon, 23 May 2011 11:12:47 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110503 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: John Baldwin , freebsd-acpi@FreeBSD.org X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=X-VIET-VPS Content-Transfer-Encoding: 7bit Cc: Subject: acpi resources problem potentially because of new pcib code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2011 08:32:13 -0000 John, it seems that possibly your recent changes for PCI bridges could have broken something for my old 440BX/PIIX4/PIII type test machine. Looks like now some I/O resources get assigned to a PCI bridge instead of ACPI. Some highlights follow: ... acpi_timer0: couldn't allocate resource (port 0x4008) ... pcib0: port 0xcf8-0xcff,0x4000-0x4041,0x5000-0x500f on acpi0 ... device_attach: acpi_throttle0 attach returned 6 More data here: http://people.freebsd.org/~avg/ms6163/ I see that _CRS of the Host-PCI bridge indeed claims that 0x4000 range, so I realize that this is a BIOS bug, but I think that perhaps we could have some quirk there to leave this range to ACPI. -- Andriy Gapon