Date: Tue, 5 May 2009 15:16:17 +0200 From: Guido Falsi <mad@madpilot.net> To: Gavin Atkinson <gavin@FreeBSD.org> Cc: freebsd-stable@FreeBSD.org Subject: Re: [PANIC] recent 7.2-STABLE when probing drm Message-ID: <20090505131617.GB83487@megatron.madpilot.net> In-Reply-To: <1241521951.47323.3.camel@buffy.york.ac.uk> References: <20090505110624.GA83487@megatron.madpilot.net> <1241521951.47323.3.camel@buffy.york.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 05, 2009 at 12:12:31PM +0100, Gavin Atkinson wrote: > > Is any more information needed? > > When it panics, can you please type "bt" (assuming you have the debugger > compiled in) and show the output? I did not have a kernel with debugger handy. Here you go (copying by hand...): drm0: <Intel Q35> on vgapci0 panic: resource_list_alloc: resource entry busy cpuid = 0 KDB: enter: panic [thread pid 0 tid 0 ] Stopped at kdb_enter_why+0x3a: movl $0,kdb_why db> bt kdb_enter_why(c07d0374,c07d0374,c07d2cf1,c0c20760,0,...) at kdb_enter_why+0x3a panic(c07d2cf1,3,10,c086a7b4,c0c20788,...) at panic+0x131 resource_list_alloc(c6d56604,c6d88a80,c6d88a80,3,c6d79dfc,...) at resource_list_alloc+0xee pci_alloc_resource(c6d88a80,c6d88a80,3,c6d79dfc,0,ffffffff,1,4) at pci_alloc_resource+0x554 bus_alloc_resource(c6d88a80,3,c6d79dfc,0,ffffffff,...) at bus_alloc_resource+0x7e vga_pci_alloc_resource(c6d88a80,c6d81d80,3,c6d79dfc,0,ffffffff,1,4) at vga_pci_alloc_resource+0x3b bus_alloc_resource(c6d88a80,3,c6d79dfc,0,ffffffff,...) at bus_alloc_resource+0x7e drm_alloc_resource(c6d88b80,c6d88b80,c6d79c00,c0c208fc,c04a6946,...) at drm_alloc_resource+0xea drm_get_resource_start(c6d79c00,0,1,8,c07b652b,...) at drm_get_resource_start0x17 i915_driver_load(c6d79c00,6,c07b652b,1c2,ffffffff,...) at i915_driver_load+0x139 drm_attach(c6d81d80,c08078a0,102) at drm_attach+0x604 i915_attach(c6d81d80,c6d0f858,c0818470,c07d2b42,80000000,...) at i915_attach+0x10a device_attach(c6d81d80,c6d81d80,c07d2aa0,932,c6d81d80,...) at device+attach+0x36a device_probe_and_attach(c6d81d80,c6d88b80,c0c209f4,c04dc7f8,c6d88b80,...) at device_probe_and_attach+0xfd bus_generic_attach(...) at bus_generic_attach+0x19 vga_pci_attach(...) at vga_pci_attach+0x32 device_attach(...) at device_attach+0x36a device_probe_and_attach(...) at device_probe_and_attach+0xfd bus_generic_attach(...) at bus_generic_attach+0x19 acpi_pci_attach(...) at acpi_pci_attach+0x171 device_attach(...) at device_attach+0x36a device_probe_and_attach(...) at device_probe_and_attach+0xfd bus_generic_attach(...) at bus_generic_attach+0x19 acpi_pcib_attach(...) at acpi_pcib_attach+0x18e acpi_pcib_acpi_attach(...) at acpi_pcib_acpi_attach+0x1ad device_attach(...) at device_attach+0x36a device_probe_and_attach(...) at device_probe_and_attach+0xfd bus_generic_attach(...) at bus_generic_attach+0x19 acpi_pci_attach(...) at acpi_pci_attach+0x171 device_attach(...) at device_attach+0x36a device_probe_and_attach(...) at device_probe_and_attach+0xfd bus_generic_attach(...) at bus_generic_attach+0x19 nexus_attach(...) at nexus_attach+0x1a device_attach(...) at device_attach+0x36a device_probe_and_attach(...) at device_probe_and_attach+0xfd root_bus_configure(...) at root_bus_configure+0x1b configure(...) at configure0xc mi_startup() at mi_startup+0x90 begin() at begin+0x2c (I cut some parameters, hope they were not important) Contact me as you wish if any other information or tests are needed. -- Guido Falsi <mad@madpilot.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090505131617.GB83487>