2011/4/28 Jack Vogel <jfvo...@gmail.com>: > On Thu, Apr 28, 2011 at 2:28 PM, John Baldwin <j...@freebsd.org> wrote: >> >> On Thursday, April 28, 2011 5:17:11 pm Wiktor Niesiobedzki wrote: >> > Though they mention that HT MSI windows is disabled. I'm not sure, >> > whether this matters. >> >> Yes, that is probably what breaks this. >> >> -- >> John Baldwin > > Opps, missed that, thanks John. So, disable MSIX and MSI using sysctl, > then the driver should use legacy when it loads. > > Still, I'd get a different motherboard, sucks to not have MSIX :( >
Thanks for hints. I've disabled MSIX and MSI: kadlubek# sysctl hw.pci | grep msi hw.pci.honor_msi_blacklist: 1 hw.pci.enable_msix: 0 hw.pci.enable_msi: 0 and reloaded if_em module. During initialization it confirmed, that will not use MSI(X): em0: <Intel(R) PRO/1000 Network Connection 7.1.9> port 0xdc00-0xdc1f mem 0xfe9e0000-0xfe9fffff,0xfe900000-0xfe97ffff,0xfe9dc000-0xfe9dffff irq 24 at device 0.0 on pci2 em0: MSIX: insufficient vectors, using MSI em0: No MSI/MSIX using a Legacy IRQ em0: [FILTER] em0: Ethernet address: 00:1b:21:9d:52:1b em0: link state changed to UP Though behavior hasn't change - I still see outgoing packets, and no incoming traffic. As far as I see, linux driver does that automagically, when no MSI(-X) is available, then it fallbacks to IRQ: [ 16.377387] e1000e 0000:02:00.0: (unregistered net_device): Failed to initialize MSI-X interrupts. Falling back to MSI interrupts. [ 16.377511] e1000e 0000:02:00.0: (unregistered net_device): Failed to initialize MSI interrupts. Falling back to legacy interrupts. Does anything come to your mind, that I can do, to debug, why this card is not working? Cheers, Wiktor _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"