From owner-freebsd-current@FreeBSD.ORG Sat Jan 8 00:39:31 2005 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 9065E16A4CE; Sat, 8 Jan 2005 00:39:31 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 552C143D49; Sat, 8 Jan 2005 00:39:31 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j080dTGV028333 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 7 Jan 2005 16:39:30 -0800 Message-ID: <41DF2BB3.60800@root.org> Date: Fri, 07 Jan 2005 16:39:15 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <20587818.1102626838092.JavaMail.tomcat@pne-ps4-sn1> <41DEED05.4040000@root.org> <41DF0839.6040700@telia.com> <200501071728.16828.jhb@FreeBSD.org> In-Reply-To: <200501071728.16828.jhb@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@FreeBSD.org Subject: Re: page fault panic in device_get_softc/acpi_pcib_route_interrupt 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, 08 Jan 2005 00:39:31 -0000 John Baldwin wrote: > On Friday 07 January 2005 05:07 pm, Pawel Worach wrote: > >>Nate Lawson wrote: >> >>>Pawel, can you split out the lines so we can isolate where the panic is >>>occurring? At the end of acpi_pcib.c, before the call to >>>acpi_pci_link_route_interrupt() >> >>Doesn't look like device_get_state() likes this device either. >> >>acpi_MatchHid() Hid: PNP0A03 >>acpi_MatchHid() Hid: PNP0A03 >>pcib0: on acpi0 >>pci0: on pcib0 >>acpi handle 0xc1ec8d20, name \LPUS >>link device: 0 index 0 > > So it appears the handle doesn't have a device_t associated with it. :( The > next step is to maybe do a printf in the code that adds the device_t's to see > if one shows up for this handle, and if the handle is the same for the given > name. Ok, add this to acpi.c:acpi_add_child(), after AcpiAttachData(): printf("adding child %s, dev %p\n", acpi_name(handle), acpi_get_device(child)); Then send the output. -- Nate