On Sat, Oct 12, 2013 at 12:08 AM, Bjorn Helgaas <bhelg...@google.com> wrote: > [+cc Don, e1000-devel] > > On Fri, Oct 11, 2013 at 9:35 AM, Greg KH <gre...@linuxfoundation.org> wrote: >> On Fri, Oct 11, 2013 at 10:58:18AM +0800, ethan.zhao wrote: >>> From: "ethan.zhao" <ethan.ker...@gmail.com> >>> >>> While loading ixgbevf driver,every vf detected will be output as the >>> same name 'eth4': >>> >>> ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network Driver - >>> version 2.8.7 >>> Copyright (c) 2009-2012 Intel Corporation. >>> ixgbevf 0000:20:10.0: enabling device (0000 -> 0002) >>> ixgbe 0000:20:00.0 eth0: VF Reset msg received from vf 0 >>> ixgbevf 0000:20:10.0: irq 199 for MSI/MSI-X >>> ixgbevf 0000:20:10.0: irq 200 for MSI/MSI-X >>> ixgbevf: eth%d: ixgbevf_init_interrupt_scheme: Multiqueue Disabled: Rx >>> Queue >>> count = 1, Tx Queue count = 1 >> >> What is that message? That's not good, "eth%d"? > > Just a reminder that ixgbevf 2.8.7 is not the driver version that's in > the kernel tree, so it's easy to spend time on mainline issue that > have been fixed in the out-of-tree versions, or vice versa. > Thanks, Yes, the driver version of ixgbevf in mainline is far later from the ones in sourceforge. the "eth%d" issue maybe was fixed in recent 2.11.3 .
> Per Don, the latest ixgbevf driver is here: > https://sourceforge.net/projects/e1000/files/ixgbevf%20stable/ > > Bjorn -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
