similar to: tg3 network link unstable

Dear All, I am having a HP xw4400 with following ethernet controller as reported by lspci Broadcom Corporation NetXtreme BCM5755 Gigabit Ethernet PCI Express (rev 02) This machine was running CentOS 5.2 without any problem. After updating the machine with yum update on 8 April, after which it is showing to be CentOS 5.3, this machine stops communicating

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]

This problem still bites us. I've tried to play around with DHCP settings (rd.net.timeout.dhcp, rd.net.dhcp.retry) to no avail. I'm happy about /any/ hint. Cheers frank On 04/24/2017 11:57 PM, Frank Thommen wrote: > Hi, > > kickstarting fails due to problems with host resolution, even though the > network seems to be properly configured through DHCP. eno1 and eno2 are

I have a machine I just deployed w/ tg3 interfaces, I have setup bonding on this same line of server (HP DL380 G4) a million times. I saw there were changes recently to how you configure a bond and have my setup configured according to: http://kbase.redhat.com/faq/docs/DOC-7431 The HP switch has a LACP trunk defined on the two ports. Problem is, when rebooting, I need to issue a `service network

CentOS Errata and Enhancement Advisory 2015:1029 Upstream details at : https://rhn.redhat.com/errata/RHEA-2015-1029.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 5dff711b2e373e9659765e628fc5ba969313021fc81608078af40dad90442a5f kmod-tg3-3.137-2.el6_6.i686.rpm x86_64:

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

I have 3 machines, T60 thinkpad with e1000 NIC Dell PowerEdge 2950 with bnx2 NIC HP DL360 G4P with tg3 NIC All running xen 3.03 / 2.6.16.29-xen I have a netbootable image with 2.6.16.29-xenU. This image when it boots creates a vlan eth0.4002, and then tries to communicate on that interface to a central server. On the machines with e1000 an bnx2 NICs, this works fine. On the

Hi, I''m having problems using Xen (2.0.7 and 3.0.0) on newer IBM HS-20 blades, which uses Broadcom network card (tg3 kernel module). Here''s the relevant entry from lspci : 05:01.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704S Gigabit Ethernet (rev 10) 05:01.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704S Gigabit Ethernet (rev 10) If xend is

Hi, i have some problems with xen-3.0.1 and the network-bridge script. After ''/etc/init.d/xend start'' or ''/etc/xen/script/network-bridge start'' everything works perfect (as well as the domU''s network) - but only for a few seconds (~20s). After that the network seems to crash - no outgoing or incoming connection possible. I have read a forum

Greetings: I know it's been mentioned before that the tg3 driver in CentOS 3.4 is buggy. I had to revert to 3.4 today from 4 (fresh install) and now I have no link and thus no network. I'm wondering if this is caused by this bug and what the work-around is. Thanks. Brendon Colby

Hello, I am desperately trying to get pci-passthrough to working. I want to pass a tg3 nic to domU. when booting domU I get a lot of messages: pcifront pci-0: pciback not responding!!! in domU, "ifconfig eth... adress up" hangs for 2 minutes, finally ifconfig -a shows a correct setting with no data transmitted rx/tx The IP Adress is being assigned, but there is no data transmission

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

Hi, I have to install Broadcom driver because the Dell Optiplex 330 running Centos 5.2 is not able to connect to the network. I am trying to install a Broadcom driver, but I get the followng error: [root at localhost tg3-3.85l]# [root at localhost tg3-3.85l]# make make -C /lib/modules/2.6.18-92.el5/build SUBDIRS=/usr/src/Server/Linux/Driver/tg3-3.85l modules make[1]: Entering directory

Hi *, I'm running into a problem configuring bonding on an HP DL 360 G4p, running 4.3 + tg3 driver version 3.43f. I'm connecting eth0 and eth1 to a Cisco 2948 (CatOS 8.1(3)) and receiving flapping notices. The ethernet address is that of the primary interface. I have tried several different modes, including balance-rr (0), active-backup (1), and balance-alb (6). All have the

CentOS Errata and Enhancement Advisory 2011:1789 Upstream details at : https://rhn.redhat.com/errata/RHEA-2011-1789.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 19ced15df18da5a3b519127157bd548b kmod-tg3-PAE-rhel5u7-3.119-2.el5_7.i686.rpm 04ef24479aa68979237b14abe0affdd1 kmod-tg3-rhel5u7-3.119-2.el5_7.i686.rpm

CentOS Errata and Enhancement Advisory 2011:1789 Upstream details at : https://rhn.redhat.com/errata/RHEA-2011-1789.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 085b01a2392f719fb0e7e779971deb99 kmod-tg3-rhel5u7-3.119-2.el5_7.x86_64.rpm 67667e01c4db99e4f9570b81f7faba05 kmod-tg3-xen-rhel5u7-3.119-2.el5_7.x86_64.rpm

CentOS Errata and Enhancement Advisory 2012:0564 Upstream details at : https://rhn.redhat.com/errata/RHEA-2012-0564.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 952425f3d4da6243fc5dbafe35279ddad98e91244b7a13fe0a5fc69c38929e76 kmod-tg3-3.122-1.el6_2.i686.rpm x86_64:

CentOS Errata and Enhancement Advisory 2012:0576 Upstream details at : https://rhn.redhat.com/errata/RHEA-2012-0576.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 6b7cb779728387373da59d1cc5d6e7d298dbe5f06b0c5fc2efa8d09e90cc3430 kmod-tg3-3.122-2.el6_2.i686.rpm x86_64:

I have a strange problem on one machine where eth0 gets killed when I add a virtual interface. It's got something to do with the NIC ordering or with the xen network script having a problem with multiple NICs and virtual interfaces. I could need some help/comments on this. Some history: I added a NIC (chip identifies as Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit

Hi all, i recently found that some frontend servers (Centos6) show: kernel: bonding: bond0: link status definitely up for interface eth2. kernel: bonding: bond0: link status definitely down for interface eth2, disabling it kernel: bonding: bond0: link status definitely up for interface eth2. On some days frequently and on others none. But there is no hw failure or similar. $ cat