Date: Fri, 04 May 2007 17:06:07 +0100 From: Rui Paulo <rpaulo@fnop.net> To: John Baldwin <jhb@FreeBSD.org>, Pyun YongHyeon <pyunyh@gmail.com> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/amd64/amd64 mptable_pci.c msi.c nexus.c src/sys/amd64/include intr_machdep.h src/sys/amd64/pci pci_bus.c src/sys/dev/acpica acpi_pcib_acpi.c acpi_pcib_pci.c src/sys/dev/pci pci.c pci_if.m pci_pci.c pci_private.h pcib_if.m ... Message-ID: <86k5vozi8g.wl%rpaulo@fnop.net> In-Reply-To: <86hcqs612o.wl%rpaulo@fnop.net> References: <200705021750.l42HoaMj067787@repoman.freebsd.org> <86hcqs612o.wl%rpaulo@fnop.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At Fri, 04 May 2007 16:49:35 +0100, Rui Paulo wrote: > With this change, I think, I get a WITNESS panic when booting the > second core on my MacBook > > After SMP: AP #1 Launched, I get this panic: > panic: blockable sleep lock (sx) msi @ i386/i386/msi.c:374 > > The backtrace is: > witness_checkorder() > _sx_lock() > msi_map() > nexus_map_msi() > acpi_pcib_map_msi() > pcib_map_msi() > pci_remap_msi_irq() > msi_assign_cpu() BTW the source of the problem is related to msk(4). If I disable MSI only on the msk device (via hw.msk.msi_disable=1 tunable), everything works fine.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86k5vozi8g.wl%rpaulo>