search for: addrconf

...ng interface eth1 the new active one. Dec 17 08:34:21 3_10 kernel: bonding: bond0: releasing active interface eth1 Dec 17 08:34:21 3_10 network: Shutting down interface bond0: succeeded Dec 17 08:34:21 3_10 network: Shutting down interface eth2: succeeded ........ Dec 17 08:35:16 3_10 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready Dec 17 08:35:20 3_10 ifup: Enslaving eth0 to bond0 Dec 17 08:35:20 3_10 kernel: bnx2: eth0: using MSI Dec 17 08:35:20 3_10 kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Dec 17 08:35:20 3_10 kernel: bonding: bond0: enslaving eth0 as a backup interface with...

...bit Ethernet Controller While the first device (seen as eth0) does *not* allow to set a different MTU (tried with 1576 and 1546, both values I could use; I am forced to use values >1500 here due to protocol stuff), the second works without a problem. dmesg shows: eth0: Unsupported MTU setting ADDRCONF(NETDEV_UP): eth0: link is not ready eth1: changing MTU from 1500 to 1576 ADDRCONF(NETDEV_UP): eth1: link is not ready 802.1Q VLAN 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...

When i do #xm create name.cfg i''ve ADDRCONF(NETDEV_UP): vif2.0: link is not ready My DomU was created but can''t access to network.... What do think about it? I use xen 3.0.4 HVM. Thanks! -- Benjamin HENRION Elève de 4eme année de l'' EXIA (Nancy) Ecole supérieure d''informatique Spé Réseaux ____________________...

...P-Informationen f?r eth0 werden bestimmt ... fehlgeschlagen; keine Verbindung vorhanden. 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

Hi, after upgrading to 7.6, kernel 3.10.0-957.1.3.el7.x86_64, at boot instead of the GUI login screen I got two lines like this: IPv6: ADDRCONF(NETDEV_UP): em1: link is not ready IPv6: ADDRCONF(NETDEV_UP): em1: link is not ready The server is accessible via ssh on IPv4 Server: DELL PowerEdge T 110 II NIC: Broadcom, driver tg3, lspci -v: 04:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5722 Gigabit Ethernet PCI...

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 12/25/18 11:54 PM, Luigi Rosa wrote: > Hi, after upgrading to 7.6, kernel 3.10.0-957.1.3.el7.x86_64, at boot > instead of the GUI login screen I got two lines like this: The output you see is probably unrelated to the problem.? Check the output of "systemctl status gdm" and /var/log/Xorg.0.log

...00:19.0: eth0: Intel(R) PRO/1000 Network Connection e1000e 0000:00:19.0: eth0: MAC: 7, PHY: 8, PBA No: FFFFFF-0FF r8169 0000:01:00.0: eth1: RTL8168d/8111d at 0xffffc9000187c000, 00:0a:cd:1d:44:fe, XID 081000c0 IRQ 31 r8169 0000:01:00.0: eth1: jumbo features [frames: 9200 bytes, tx checksumming: ko] ADDRCONF(NETDEV_UP): eth0: link is not ready device eth0 entered promiscuous 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:...

...DRM: allocated 1920x1080 fb: 0x200000, bo 9de54446 [ 11.893865] Console: switching to colour frame buffer device 240x67 [ 12.114354] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device [ 12.341697] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0 [ 13.382580] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 13.554107] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 13.569792] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [ 13.570666] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [ 13.586227] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready...

...calhost kernel: [ 9.658257] Adding 1952764k swap on /dev/sda1. Priority:-2 extents:1 across:1952764k SS Jan 25 13:16:36 localhost kernel: [ 10.274184] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: errors=remount-ro Jan 25 13:16:38 localhost kernel: [ 13.686118] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Jan 25 13:16:39 localhost kernel: [ 13.783210] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Jan 25 13:16:39 localhost kernel: [ 13.801772] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready Jan 25 13:16:39 localhost kernel: [ 13.802572] IPv6: ADDRCONF...

...he forcedeth driver thinks it is eth0: [root at fsdsigns2 ~]# dmesg | grep eth forcedeth.c: Reverse Engineered nForce ethernet driver. Version 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...

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 re...

...essages: 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 (1). bonding: bond0: Setting MII monitoring interval to 500. ADDRCONF(NETDEV_UP): bond0: link is not ready bonding: bond0: Adding slave eth0. bnx2: eth0: using MSIX bnx2i: iSCSI not supported, dev=eth0 bonding: bond0: enslaving eth0 as a backup interface with a down link. bnx2i: iSCSI not supported, dev=eth0 bonding: bond0: Adding slave eth2. bnx2: eth2: using MSIX b...

...gh 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] localhost kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready [ 19.977052] 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 disabl...

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 # dmesg |tail [ 348.793398] device veth0 entered promiscuous mode [ 348.793553] IPv6: ADDRCONF(NETDEV_UP): veth0: link...

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

...ect to CUPS server localhost:631 - Connection refused 9691 Apr 26 10:17:11 houyi-vm12 kernel: Bridge firewalling registered 9692 Apr 26 10:17:11 houyi-vm12 kernel: bnx2: peth0: using MSIX 9693 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 m...

...DMESG: e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:22:4d:9d:55:13 e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection e1000e 0000:00:19.0: eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF e1000e 0000:00:19.0: irq 33 for MSI/MSI-X e1000e 0000:00:19.0: irq 33 for MSI/MSI-X ADDRCONF(NETDEV_UP): eth0: link is not ready e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx e1000e 0000:00:19.0: eth0: 10/100 speed: disabling TSO ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready eth0: no IPv6 routers present usb 1-1.5: USB disconnect, device number 3 lo: Disabled Pr...

Hi all, it''s happening a strange thing: After I boot the xen dom0 network is unavailable: I have to unload the network modules and load it again ( rmmod / modprobe) and execute a service network restart) This is strange, what do you suggest me to check? Thanks Marco Strullato _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

https://bugs.freedesktop.org/show_bug.cgi?id=55227 Bug #: 55227 Summary: GeForce GTX 560 Ti fails to resume Classification: Unclassified Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: