Date: Sat, 19 Jan 2008 00:32:48 -1000 From: Parv <parv@pair.com> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: PCI MSI (was Re: What current Dell Systems are supported/work) Message-ID: <20080119103248.GA1317@holstein.holy.cow> In-Reply-To: <200801181010.04965.jhb@freebsd.org> References: <DB4DDB04-1ADE-4C36-A846-BB6B7C12EB1B@patmedia.net> <20080118103006.GA1443@holstein.holy.cow> <200801180850.32062.jhb@freebsd.org> <200801181010.04965.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
in message <200801181010.04965.jhb@freebsd.org>, wrote John Baldwin thusly... > > On Friday 18 January 2008 08:50:31 am John Baldwin wrote: > > On Friday 18 January 2008 05:30:06 am Parv wrote: > > > There was no page fault or trap 12 message when the panic > > > happened. After some of messages are printed (as in dmesg), > > > kdb is entered ... > > > > > > ioapic0: Assigning PCI IRQ 23 to local APIC 1 > > > msi: Assigning MSI IRQ 256 to local APIC 0 > > > panic: blockabke sleep block (sleep mutex) msi @ /misc/src-6/sys/i386/i386/msi.c:381 > > > cpuid: 0 > > > kdb: stack backtrace > > > kbd_backtrace( c0adc531,0,c0abaafd,c1020c34,c0bab700,...) at ... \ > > > [I skipped from here to the "db>" prompt] ... > > > Tomorrow, rather later today, I will type up the "trace" > > > output. Please let me know if you would like to see any other > > > output that I could possibly provide. > > > > This is good enough for me to see the bug, I'll work on fixing > > it. There are some locking changes in the x86 interrupt code I > > need to MFC. > > Try this patch: ... Thanks much John. Your patch allowed my computer to resume normal operation without disabling MSI via hw.pci.enable_msi*. Lest I forget, mahalo for saving me from typing up the trace output. - Parv --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080119103248.GA1317>