msi broken?

Arno J. Klaassen arno at heho.snv.jussieu.fr
Tue Mar 10 15:51:52 PDT 2009


John Baldwin <jhb at freebsd.org> writes:

> On Tuesday 10 March 2009 3:00:00 pm Arno J. Klaassen wrote:
>> John Baldwin <jhb at 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


More information about the freebsd-current mailing list