netdev - RE: Ixgbe question

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <36D9DB17C6DE9E40B059440DB8D95F52049D5CD4@orsmsx418.amr.corp.intel.com>
Date:	Mon, 10 Mar 2008 18:01:24 -0700
From:	"Brandeburg, Jesse" <jesse.brandeburg@...el.com>
To:	"Ben Greear" <greearb@...delatech.com>
Cc:	<netdev@...r.kernel.org>
Subject: RE: Ixgbe question

Ben Greear wrote:
> 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.

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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html