Date: Tue, 10 Mar 2009 16:37:30 -0400 From: John Baldwin <jhb@freebsd.org> To: "Arno J. Klaassen" <arno@heho.snv.jussieu.fr> Cc: freebsd-current@freebsd.org Subject: Re: msi broken? Message-ID: <200903101637.31039.jhb@freebsd.org> In-Reply-To: <wpab7tp5jj.fsf@heho.snv.jussieu.fr> References: <wp1vt5bhc4.fsf@heho.snv.jussieu.fr> <200903101425.28608.jhb@freebsd.org> <wpab7tp5jj.fsf@heho.snv.jussieu.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
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()? -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200903101637.31039.jhb>