Date: Fri, 07 Jan 2005 16:39:15 -0800 From: Nate Lawson <nate@root.org> To: John Baldwin <jhb@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: Re: page fault panic in device_get_softc/acpi_pcib_route_interrupt Message-ID: <41DF2BB3.60800@root.org> In-Reply-To: <200501071728.16828.jhb@FreeBSD.org> References: <20587818.1102626838092.JavaMail.tomcat@pne-ps4-sn1> <41DEED05.4040000@root.org> <41DF0839.6040700@telia.com> <200501071728.16828.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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: <ACPI Host-PCI bridge> on acpi0 >>pci0: <ACPI PCI bus> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41DF2BB3.60800>