Ixgbe question
Subsystems (2)
I have a pair of IXGBE NICs in a system, and notice a strange case where the NIC is not always 'UP' after my programs finish trying to configure it. I haven't noticed this with any other NICs, but I also just moved to 2.6.23.17 from 23.9 and 23.14.
I see this in the logs:
ADDRCONF(NETDEV_UP): eth0: link is not ready
It would seem to me that we should be able to set the admin state to UP, even if the link is not up??
Kernel is 2.6.23.17 plus my hacks. Ixgbe driver is version 1.3.7.8-lro.
Hardware is quad-core Intel, 2 build-in e1000, 2-port ixgbe (CX4) chipset NIC on a pcie riser.
Thanks,
Ben
Signature · 2 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com
Quoted 12 lines · Ben Greear
I have a pair of IXGBE NICs in a system, and notice a strange case where the NIC is not always 'UP' after my programs finish trying to configure it. I haven't noticed this with any other NICs, but I also just moved to 2.6.23.17 from 23.9 and 23.14.
I see this in the logs:
ADDRCONF(NETDEV_UP): eth0: link is not readyIt would seem to me that we should be able to set the admin state to UP, even if the link is not up??
Quoted 6 lines
Kernel is 2.6.23.17 plus my hacks. Ixgbe driver is version
1.3.7.8-lro.Hardware is quad-core Intel, 2 build-in e1000, 2-port ixgbe (CX4) chipset NIC
on a pcie riser.
addrconf_notify() is printing that message, and I see it if you enable IPv6 on an interface. I don't think it is ixgbe specific.
it doesn't depend or preclude administrative UP, it is from the notify handler getting a NETDEV_UP message, regardless of link state.
you'll see some other message like:ADDRCONF(NETDEV_CHANGE): eth6: link becomes ready
when you plug in the cable, all courtesy of Ipv6
Jesse