search for: netdev_chang

On Wed, 3 Apr 2019 00:52:47 -0400 Si-Wei Liu <si-wei.liu at oracle.com> wrote: > > + if (unlikely(dev->flags & IFF_UP)) { > + struct netdev_notifier_change_info change_info = { > + .info.dev = dev, > + }; > + > + call_netdevice_notifiers_info(NETDEV_CHANGE, > + &change_info.info); > + } This notifier is not really necessary, there already is a CHANGENAME that gets sent. NETDEV_CHANGE is used in other cases to mean that the state (flags) have changed.

On Wed, 3 Apr 2019 00:52:47 -0400 Si-Wei Liu <si-wei.liu at oracle.com> wrote: > > + if (unlikely(dev->flags & IFF_UP)) { > + struct netdev_notifier_change_info change_info = { > + .info.dev = dev, > + }; > + > + call_netdevice_notifiers_info(NETDEV_CHANGE, > + &change_info.info); > + } This notifier is not really necessary, there already is a CHANGENAME that gets sent. NETDEV_CHANGE is used in other cases to mean that the state (flags) have changed.

...full duplex Dec 17 08:35:23 3_10 kernel: bonding: bond0: link status definitely up for interface eth0. Dec 17 08:35:23 3_10 kernel: bonding: bond0: making interface eth0 the new active one. Dec 17 08:35:23 3_10 kernel: bonding: bond0: first active interface up! Dec 17 08:35:23 3_10 kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Dec 17 08:35:23 3_10 kernel: bnx2: eth1 NIC Link is Up, 1000 Mbps full duplex Dec 17 08:35:23 3_10 kernel: bonding: bond0: link status definitely up for interface eth1. Dec 17 08:35:23 3_10 kernel: tg3: eth2: Link is up at 1000 Mbps, full duplex. Dec 17 08:35:24 3_10 ker...

...N Support v1.8 Ben Greear <greearb at candelatech.com> All bugs added by David S. Miller <davem at redhat.com> ADDRCONF(NETDEV_UP): eth0.543: link is not ready ADDRCONF(NETDEV_UP): eth0.820: link is not ready e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready ADDRCONF(NETDEV_CHANGE): eth0.543: link becomes ready ADDRCONF(NETDEV_CHANGE): eth0.820: link becomes ready e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready The MTU is set as usual in the ifcfg-ethN...

...Kabel pr?fen? FEHLGESCHLAGEN ... Netzwerkparameter einstellen ... OK NetworkManager-Daemon starten: OK Loading autofs4: OK automount starten: OK In /var/log/messages I see: Jul 5 16:36:08 meikel-pc kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Jul 5 16:36:23 meikel-pc kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready It takes 15 seconds between the two messages until it becomes ready. I have no idea why it first says that the link is not ready. Any ideas? Regards, Meikel

...iso) - PXE boot start and the desktop load the kernel and the inirtd file - the kernel is booted and at this time the led of the network switch goes down for the port used by the desktop. - then I have a message "no carrier detected on interface em1" - followed by " IPv6 ADDRCONF(NETDEV_CHANGED): em1: link become ready (and of course the led goes back to green on the switch) But I have no IPV6 network setup! How can I force to IPV4 setup to load the kikstart file ? I've tried do switch from legacy boot to UEFI boot (my local server setup can answer requests for the two options),...

...s (new ones prefixed by >>): net/core/dev.c: In function 'dev_change_name': >> net/core/dev.c:1252:48: error: passing argument 2 of 'call_netdevice_notifiers_info' from incompatible pointer type [-Werror=incompatible-pointer-types] call_netdevice_notifiers_info(NETDEV_CHANGE, dev, ^~~ net/core/dev.c:164:12: note: expected 'struct netdev_notifier_info *' but argument is of type 'struct net_device *' static int call_netdevice_notifiers_info(unsigned long val, ^~~~~~~~~~~~~~~~~~~~~~~...

I inherited a xen server that is setup to have all the VM images hosted on an iSCSI mounted NAS array. We been experiencing a random (about every 2-3 days) issue where xen would crash all the VMs, leaving nothing but the Domain0 running. What appears to be happening is something causes the iSCI mount to hiccup. Running "vgchange -a y" and restarting all the VMs brings everything up.

...400 > Si-Wei Liu <si-wei.liu at oracle.com> wrote: > > > > > + if (unlikely(dev->flags & IFF_UP)) { > > + struct netdev_notifier_change_info change_info = { > > + .info.dev = dev, > > + }; > > + > > + call_netdevice_notifiers_info(NETDEV_CHANGE, > > + &change_info.info); > > + } > > This notifier is not really necessary, there already is a CHANGENAME > that gets sent. > NETDEV_CHANGE is used in other cases to mean that the state (flags) > have changed. The point is some existing scripts might no...

...iscuous mode r8169 0000:01:00.0: eth1: invalid firwmare r8169 0000:01:00.0: eth1: unable to load firmware patch rtl_nic/rtl8168d-1.fw (-22) r8169 0000:01:00.0: eth1: link down r8169 0000:01:00.0: eth1: link down ADDRCONF(NETDEV_UP): eth1: link is not ready r8169 0000:01:00.0: eth1: link up ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready br0: port 1(eth0) entering learning state eth1: no IPv6 routers present eth0: no IPv6 routers present br0: port 1(eth0) entering forwarding state r8169...

...see in dom0's xend log is: Dec 20 13:18:10 kr kernel: device vif25.0 entered promiscuous mode Dec 20 13:18:10 kr kernel: ADDRCONF(NETDEV_UP): vif25.0: link is not ready Dec 20 13:18:12 kr kernel: blkback: ring-ref 8, event-channel 9, protocol 1 (x86_32-abi) Dec 20 13:18:12 kr kernel: ADDRCONF(NETDEV_CHANGE): vif25.0: link becomes ready Dec 20 13:18:12 kr kernel: xenbr0: topology change detected, propagating Dec 20 13:18:12 kr kernel: xenbr0: port 5(vif25.0) entering forwarding state In dom0's /var/log/messages I see: Dec 20 13:18:12 kr kernel: blkback: ring-ref 8, event-channel 9, protocol 1 (...

...0.60. forcedeth: using HIGHDMA eth0: forcedeth.c: subsystem: 01458:e000 bound to 0000:00:07.0 e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection ADDRCONF(NETDEV_UP): eth1: link is not ready e1000: eth1: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready eth0: no IPv6 routers present eth1: no IPv6 routers present however, sometimes it starts up correctly: [root at fsdsigns2 ~]# dmesg | grep eth forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60. e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Co...

Am 05.07.2015 um 20:52 schrieb Gordon Messmer: > On 07/05/2015 07:57 AM, Meikel wrote: >> Jul 5 16:36:08 meikel-pc kernel: ADDRCONF(NETDEV_UP): eth0: link is not >> ready >> Jul 5 16:36:23 meikel-pc kernel: ADDRCONF(NETDEV_CHANGE): eth0: link >> becomes ready >> >> It takes 15 seconds between the two messages until it becomes ready. I >> have no idea why it first says that the link is not ready. > > It's probably autonegotiation of link speed. I'm not sure why it'd > take that...

...interface with a down link. bnx2i: iSCSI not supported, dev=eth2 bonding: bond0: link status definitely up for interface eth0. bonding: bond0: making interface eth0 the new active one. bonding: bond0: first active interface up! bonding: bond0: link status definitely up for interface eth2. ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready bonding: bond0: link status definitely down for interface eth2, disabling it bnx2: eth2 NIC Copper Link is Up, 1000 Mbps full duplex bonding: bond0: link status definitely up for interface eth2. bond0: no IPv6 routers present Understanding that bnx2i is used for hardw...

...] localhost kernel: tg3 0000:0b:00.0 eno1: Link is up at 1000 Mbps, full duplex [ 19.977118] localhost kernel: tg3 0000:0b:00.0 eno1: Flow control is off for TX and off for RX [ 19.978880] localhost kernel: tg3 0000:0b:00.0 eno1: EEE is disabled [ 19.980693] localhost kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready [ 19.829468] localhost dracut-initqueue[992]: dhcp: PREINIT eno1 up [ 19.853734] localhost dhclient[1393]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 6 (xid=0x4df19201) [ 26.030151] localhost dhclient[1393]: DHCPDISCOVER on eno1 to 255.255.255.255...

Hi there, my Server: Debian 4.0, XEN xen-hypervisor-3.0.3-1-i386-pae I have successfully installed and running 13 domU. I have enough free ressources for number 14. I set it up in exactly the same way like the others. Once started this dumU Nr 14, every other domU lost its network connection. If I shutdown Nr 14, everything is working finde again. Is there a maximum number of domUs per Host?

...ed iptables and the firewall on the domU''s, hoping that would address the issue, but it hasn''t. Not sure if this is any help, but here is a snippet of /var/log/messages when I start the above domU using "xm create mailsrv01": Jun 13 18:13:38 mailprod01 kernel: ADDRCONF(NETDEV_CHANGE): vif4.0: link becomes ready Jun 13 18:13:38 mailprod01 kernel: xenbr0: topology change detected, propagating Jun 13 18:13:38 mailprod01 kernel: xenbr0: port 3(vif4.0) entering forwarding state Jun 13 18:14:53 mailprod01 ntpd[3572]: synchronized to 173.203.202.87, stratum 2 Jun 13 18:15:37 mailpro...

...8.645303] ip6_tables: (C) 2000-2006 Netfilter Core Team --- Then I do --- # virsh -c lxc:/// start gitolite Domain gitolite started # dmesg |tail [ 348.793398] device veth0 entered promiscuous mode [ 348.793553] IPv6: ADDRCONF(NETDEV_UP): veth0: link is not ready [ 348.997973] IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready [ 348.997998] virbr0: topology change detected, propagating [ 348.998001] virbr0: port 1(veth0) entered forwarding state [ 348.998008] virbr0: port 1(veth0) entered forwarding state [ 348.998017] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [ 349.78417...

Hi folks, I'm running CentOS 6.6 on my workstation. There I have a user meikel, and its home directory /home/meikel ist stored on a samba share on a server which also runs CentOS 6.6. In the very beginning I added the mount options for that home directory into the /etc/fstab file which led to some problems, so I set up autofs for mounting the home directory. The autofs seems to work for

...Apr 26 10:17:11 houyi-vm12 syslogd: sendto: Network is unreachable 9694 Apr 26 10:17:11 houyi-vm12 kernel: ADDRCONF(NETDEV_UP): peth0: link is not ready 9695 Apr 26 10:17:14 houyi-vm12 kernel: bnx2: peth0 NIC Copper Link is Up, 1000 Mbps full duplex 9696 Apr 26 10:17:14 houyi-vm12 kernel: ADDRCONF(NETDEV_CHANGE): peth0: link becomes ready 9697 Apr 26 10:17:15 houyi-vm12 kernel: device peth0 entered promiscuous mode 9698 Apr 26 10:17:15 houyi-vm12 kernel: eth0: port 1(peth0) entering forwarding state 9699 Apr 26 10:17:20 houyi-vm12 sshd[4353]: Accepted password for root from 10.1.171.135 port after I ki...