search for: netdev_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

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

I use bonding under CENTOS4.5 x32_62. I have these weird messages when I'm restarting network. Do you have any ideas how to fix this? (there is similar bug for centos5 http://bugs.centos.org/view.php?id=2404, but the author says that it worked for him in centos4...) Thanks Vitaly Dec 17 08:34:21 3_10 kernel: bonding: Warning: the permanent HWaddr of eth0 - 00:1A:64:0A:DC:9C - is still in

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, I have a *very* strange problem, unfortunately it's kind of a show stopper regarding the deployment of the machine. :( I have two Intel Gigabit Ethernet NICs on board (Supermicro-based Server), quoting lspci (full output see at the end of the email): 0d:00.0 Ethernet controller: Intel Corporation 82573E Gigabit Ethernet Controller

Am 02.07.2015 um 20:16 schrieb Gordon Messmer: > Have you yet: > setsebool -P use_samba_home_dirs 1 > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > > No, I didn't set it. Now I've set it and when logging into text console I no longer have the problem with the home

...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), up...

Hi Si-Wei, Thank you for the patch! Yet something to improve: [auto build test ERROR on net/master] url: https://github.com/0day-ci/linux/commits/Si-Wei-Liu/failover-allow-name-change-on-IFF_UP-slave-interfaces/20190329-195445 config: x86_64-lkp (attached as .config) compiler: gcc-7 (Debian 7.3.0-1) 7.3.0 reproduce: # save the attached .config to linux build tree make

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.

On Fri, Apr 05, 2019 at 02:47:01PM -0700, Stephen Hemminger wrote: > 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, > > + }; > > + > > +

I am trying to transport a dd image between to hosts over a cross linked gigabit connection. Both hosts have an eth1 configured to a non routable ip addr on a shared network. No other devices exist on this link. When transferring via sftp I received a stall warning. Checking the logs I see this: dmesg | grep eth e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:1c:c0:f2:1f:bb

After running out of swap and memory and freezing, a domU called web02 won't start up. Both dom0 and domU are running CentOS release 5.4. dom0's kernel is 2.6.18-164.el5xen and I'm running the stock xen from CentOS: xen-3.0.3-94.el5 After issuing 'xen create web02' I see the following in the xen console: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) vmalloc

I am using centos 5 x86_64 AMD64 X2 4200+. I am current on yum update. My machine has two ethernet cards. e1000 (eth0) and forcedeth (eth1) [root at fsdsigns2 ~]# more /etc/modprobe.conf alias eth0 e1000 alias eth1 forcedeth sometimes on boot the forcedeth driver thinks it is eth0: [root at fsdsigns2 ~]# dmesg | grep eth forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60.

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

Getting "bnx2i: iSCSI not supported, dev=eth0" for all the NIC adapters on all of my R710's running CentOS 5.5. Here is an sample of the error messages: bonding: Warning: either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link failures! see bonding.txt for details. bonding: bond0: setting mode to active-backup

Hi, kickstarting fails due to problems with host resolution, even though the network seems to be properly configured through DHCP. eno1 and eno2 are both attached to the network, but only eno1 gets an IP via DHCP. Still `curl` cannot resolve the mirror host and the kickstart host during dracut-initqueue: rdsosreport.txt ------------------------------------------------ [...] [ 14.780428]

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?

Hi, I have Xen 3.0.3 installed on CentOS 5.5 with 2 paravirtualized domU''s configured to use the default bridge networking and am having networking issues. If I boot the computer fresh I am able to ping dom0 and can SSH into it and start the domU''s. The following ping snippet demonstrates the problem. The first group of "Destination Host Unreachable" is while the

I'm trying to get an Archlinux guest running on a Archlinux host. Everything works except ethernet. When I boot the host, --- # dmesg |tail [ 8.265493] Bridge firewalling registered [ 8.514547] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [ 8.645303] ip6_tables: (C) 2000-2006 Netfilter Core Team --- Then I do --- # virsh -c lxc:/// start gitolite Domain gitolite started #

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

I come across some problem when using xen-4.1.1-rc1-pre from xen-4.1-testing tree and 2.6.32.36xen linux kernel from git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git. when I use ''xend restart'' , it hangs when kernel dmesg printing ''Bridge firewalling registered'' and the console show below messages: localhost# xend restart Nothing to flush. Cannot