From owner-freebsd-acpi@FreeBSD.ORG Wed May 11 20:12:49 2005 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70A9D16A4CE for ; Wed, 11 May 2005 20:12:49 +0000 (GMT) Received: from mail21.sea5.speakeasy.net (mail21.sea5.speakeasy.net [69.17.117.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3425A43D80 for ; Wed, 11 May 2005 20:12:49 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 13066 invoked from network); 11 May 2005 20:12:49 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 11 May 2005 20:12:48 -0000 Received: from [10.50.41.242] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j4BKCfxN058785; Wed, 11 May 2005 16:12:42 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-acpi@FreeBSD.org Date: Wed, 11 May 2005 15:25:19 -0400 User-Agent: KMail/1.8 References: <20050510061713.GA5437@svzserv.kemerovo.su> <200505101647.37678.jhb@FreeBSD.org> <428189D8.C51D289D@kuzbass.ru> In-Reply-To: <428189D8.C51D289D@kuzbass.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200505111525.20199.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: Eugene Grosbein Subject: Re: 5.4: pci_link problem on 440BX X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 May 2005 20:12:49 -0000 On Wednesday 11 May 2005 12:28 am, Eugene Grosbein wrote: > John Baldwin wrote: > > > > Are any of the IRQs different when you do use the pci_link code > > > > compared to the dmesg when you have pci_link disabled? > > > > > > It seems, no: > > > > > > --- dmesg_full Tue May 10 14:02:42 2005 > > > +++ dmesg_no_pci_link Tue May 10 14:00:59 2005 > > > @@ -20,9 +20,13 @@ > > > acpi_button0: on acpi0 > > > pcib0: port > > > 0x5000-0x500f,0x4000-0x4041,0xcf8-0xcff on acpi0 pci0: > > > on pcib0 > > > +pcib0: no PRT entry for 0.7.INTD > > > +pcib0: no PRT entry for 0.16.INTA > > > +pcib0: no PRT entry for 0.18.INTA > > > > Your BIOS is broken and there's not anything FreeBSD can really do about > > it. It's refusing to tell us how to handle certain IRQs which is probably > > why you are having the problems you are having. > > I'm afraid that I don't understand quite right. > The message "no PRT entry" is here only when pci_link is disabled > and then problem disappears. What makes you guess that BIOS is broken? We shouldn't print that message unless pci_link is enabled. When pci_link is disabled we shouldn't even be looking at PRT entries. Can you try booting a 6.0-snapshot CD and seeing if it works ok? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org