From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 5 19:31:42 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org 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 77AE316A41F for ; Mon, 5 Dec 2005 19:31:42 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id C14B543D53 for ; Mon, 5 Dec 2005 19:31:41 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3202527 for multiple; Mon, 05 Dec 2005 14:29:33 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB5JVLHC040885; Mon, 5 Dec 2005 14:31:21 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Eugene Grosbein Date: Mon, 5 Dec 2005 14:00:02 -0500 User-Agent: KMail/1.8.2 References: <20050513140240.GA25774@svzserv.kemerovo.su> <200512021732.15866.jhb@freebsd.org> <20051205181839.GA75425@svzserv.kemerovo.su> In-Reply-To: <20051205181839.GA75425@svzserv.kemerovo.su> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512051400.03509.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-acpi@freebsd.org Subject: Re: 5.4: pci_link problem on 440BX 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, 05 Dec 2005 19:31:42 -0000 On Monday 05 December 2005 01:18 pm, Eugene Grosbein wrote: > On Fri, Dec 02, 2005 at 05:32:14PM -0500, John Baldwin wrote: > > > > 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? > > > > > > Now 6.0 boots to multiuser mode with ACPI fully enabled or fully > > > disabled. make buildworld cannot be completed with ACPI - still silent > > > hang of userland and no console switching (keyboard leds do switch and > > > KDB works). > > > > > > 6.0's GENERIC does not boot to single user with > > > debug.acpi.disabled="pci_link", fatal trap 12 occures: page fault while > > > in kernel mode, > > > fault virtual address 0x0, supervisor read, page not present > > > in acpi_pci_link_lookup+0x26. > > > > I think I know what this is and this patch probably fixes the panic in > > the case that you use 'debug.acpi.disabled="pci_link"' > > > > --- //depot/vendor/freebsd/src/sys/dev/acpica/acpi_pci_link.c > > 2005/11/23 16:40:40 +++ > > //depot/user/jhb/acpipci/dev/acpica/acpi_pci_link.c 2005/12/02 22:28:08 > > @@ -1011,6 +1011,9 @@ > > { > > struct link *link; > > > > + if (acpi_disabled("pci_link")) > > + return (PCI_INVALID_IRQ); > > + > > ACPI_SERIAL_BEGIN(pci_link); > > link = acpi_pci_link_lookup(dev, index); > > if (link == NULL) > > I'll try this patch a bit later. > > > How does the 6.0 install CD do on your machine both with ACPI enabled and > > disabled? > > I've just installed 6.0-RELEASE again. > I booted it using [default] option (e.g. with ACPI enabled) > and installation ran smoothly. However, I could not extract > /usr/ports/distfiles/gettext-0.14.5.tar.gz, /usr/ports is mounted > from 4.11 installation. All disk activity stopped and kernel > repeatedly wrote something about "DANGER Will Robinson !!", > I think it was from /usr/src/sys/dev/ata/ata-queue.c > > I rebooted with ACPI disabled and the problem disappeared. > Now I'm going to test 'debug.acpi.disabled="pci_link"' case. Well, ACPI is probably not going to be all that happy with pci_link disabled as your machine will no longer be able to route interrupts. Are any IRQs different in the non-ACPI vs ACPI dmesgs? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org