Date: Thu, 01 Feb 2007 16:21:51 -0800 From: Julian Elischer <julian@elischer.org> To: FreeBSD Current <current@freebsd.org> Subject: still getting this panic on boot after update of sources. Message-ID: <45C2841F.1030801@elischer.org>
next in thread | raw e-mail | index | archive | help
cpu1: <ACPI CPU> on acpi0 cpu2: <ACPI CPU> on acpi0 cpu3: <ACPI CPU> on acpi0 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 pci0: <ACPI PCI bus> on pcib0 panic: mtx_lock() of spin mutex @ ../../../kern/kern_sx.c:172 cpuid = 0 KDB: enter: panic [thread pid 0 tid 0 ] Stopped at kdb_enter+0x2b: nop db> tr Tracing pid 0 tid 0 td 0xc075cd08 kdb_enter(c06c95c9) at kdb_enter+0x2b panic(c06c866c,c5f3e640,c06c9dc3,ac,0,...) at panic+0x11c _mtx_lock_flags(c5f3e680,0,c06c9dc3,ac) at _mtx_lock_flags+0x78 _sx_xlock(c090aa40,c0904c02,dd,c0692922,ff,...) at _sx_xlock+0x34 acpi_pcib_route_interrupt(c5fb8600,c5fce300,1,c5fc5df4,c5fb8600,...) at acpi_pcib2 acpi_pcib_acpi_route_interrupt(c5fb8600,c5fce300,1) at acpi_pcib_acpi_route_intert pci_assign_interrupt_method(c5fce880,c5fce300) at pci_assign_interrupt_method+0x58 pci_assign_interrupt(c5fce880,c5fce300,1) at pci_assign_interrupt+0xc0 [...] I saw some talk of changes in pci interrupt routing etc. this related? (am rebuilding from scratch just to make sure)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45C2841F.1030801>