Date: Tue, 10 Mar 2009 23:51:49 +0100 From: "Arno J. Klaassen" <arno@heho.snv.jussieu.fr> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: msi broken? Message-ID: <wp8wndxa7u.fsf@heho.snv.jussieu.fr> In-Reply-To: <200903101637.31039.jhb@freebsd.org> (John Baldwin's message of "Tue\, 10 Mar 2009 16\:37\:30 -0400") References: <wp1vt5bhc4.fsf@heho.snv.jussieu.fr> <200903101425.28608.jhb@freebsd.org> <wpab7tp5jj.fsf@heho.snv.jussieu.fr> <200903101637.31039.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin <jhb@freebsd.org> writes: > On Tuesday 10 March 2009 3:00:00 pm Arno J. Klaassen wrote: >> John Baldwin <jhb@freebsd.org> writes: >> >> > On Tuesday 10 March 2009 10:08:59 am Arno J. Klaassen wrote: >> >> >> >> Hello, >> >> >> >> when upgrading this morning from a March 1 -current, if_bge >> >> stopped working (and irq256: bge0 not showing up in >> >> vmstat -i ). Setting hw.pci.enable_msi="0" makes it work again. >> > >> > Can you get a verbose dmesg (boot -v) with MSI enabled? > > Ok, so you are getting MSI interrupts assigned and routed ok. Can you try > disabling the code that sets the INTx_MASK flag in the PCI command register > in sys/dev/pci/pci.c:pci_setup_intr()? Bon, "rid" is 0 in my case; outcommenting the "pci_clear_command_bit(dev, child, PCIM_CMD_INTxDIS);" makes no difference, and reverting rev189447 (forcing the "else" statement to be executed) gives me a panic ... But I'm not 100% sure that's what you wanted me to do ... More tomorrow, Arno
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?wp8wndxa7u.fsf>