similar to: weird network error

Hi, one of our rented root-server has a problem with the network-adapter.The network is interrupted from time to time and i can not longer connect to our server. We can only reboote (remote) the server and restart the network. I think it was an network-driver-problem from an "Intel Corporation 82574L Gigabit Network" --- e1000e But now i have install a new kernel-driver and i have

I have a server thats been running fine for a year or two lock up a few times recently, requiring power cycling. The /var/log/messages after a lockup last night is appended to this message. hardware is a pretty typical server, Supermicro X8DTE-F motherboard, dual Xeon X5650, 48GB ECC memory, LSI SAS 2008 for the boot disks, and LSI MegaRAID SAS 9261-8i for the data volume. Lots of 3TB

Hi all, I'm facing a serious problem with the e100e kernel module for Intel 82574L gigabit nics on Centos 6. The device eth0 suddenly stops working i.e. no more networking. When I do ifconfig from console I get eth0 Link encap:Ethernet HWaddr 00:xx:xx:xx:xx:EA inet6 addr: fe80::225:90ff:fe50:8fea/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

Have you experienced this? What's going on when this occurs? What do I need to do to keep it from occurring? Please advise. Thanks. Dec 4 10:18:17 localhost kernel: e1000: eth1 NIC Link is Down Dec 4 10:18:19 localhost kernel: e1000: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX Dec 4 10:18:21 localhost kernel: e1000: eth1 NIC Link is Down Dec 4 10:18:23 localhost kernel:

Hello CentOS Community, So I bought a NIC (using the Intel 82579V chipset) that supports Dual RX and TX queues , my goal with that is so iam able to see and use two IRQs in /proc/interrupts and hence be able to take advantage of 2 cores on my CPU. Instead I only see one IRQ being used, and hence only one CPU core.. Please see below. Advisement is appreciated! Alex

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

Hi, I've set up a bridge using the 2.6.11.6 kernel. The machine is running Debian testing with three NICs in it. eth0 is a standard 100Mb Intel NIC, eth1 and eth2 are both Intel gigabit cards using the e1000 driver. I tested everything at 100Mb and it worked fine. I moved the machine into production, eth1 plugging into a dumb 100Mb D-link switch, eth2 plugging into a shiney new Cisco

Hey all, i am fighting with a strange behavior here - i have two systems connected via a direct crosslink wire. After booting, the connection is up and both systems can reach the other one. After a small time window the interface is down. $ dmesg |grep eth4 igb 0000:41:00.2: added PHC on eth4 igb 0000:41:00.2: eth4: (PCIe:5.0Gb/s:Width x4) igb 0000:41:00.2: eth4: PBA No: G13158-000 8021q:

Hello, I have been using Xen on a Debian Lenny server for quite some time. I decided to build a new Dom0 using identical hardware, but newest version of Xen from repositories with Debian Squeeze. I attempting to create a new DomU on the new host which is similar to an existing DomU running on the older Lenny host. The DomU is a three NIC firewall. Two of the NICs are virtualized. One NIC is a

Hi all, I am using OCFS2-1.4.7 for 2 servers which is running Red hat enterprise 5.7 kernel 2.6.18-274.el5. OCFS2 I use for drdb for replicating master-master. My 2 servers was installed HA-Proxy. Yesterday, server web1 was down with the log kernel panic. And today, web2 was down too. After that, I trace the log file on these server and found that the reason from ocfs2. The log

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.

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

On 07/06/2015 10:00 PM, Meikel wrote: > I'll check the cable (not clear how I can do that, probably using > another cable and connecting to another outlet). Use a different cable to the same switch port, first. If you change both the cable and the switch port, you won't know if the problem was the cable or the switch port. If the problem persists with a different cable, *then*

Hi, I hope someone can help me, I cannot seem to get a system's ethernet interface to correctly work in promiscuous mode... I have a Centos 6.4 system with 2 bnx2 interfaces on it. I have set up eth1 in promiscuous mode and am sending traffic to it using the port mirroring configuration on a Nortel 3510-24T switch. The switch reports that it is sending a fair amount of traffic to the

We're trying to setup a dual-primary DRBD environment, with a shared disk with either OCFS2 or GFS. The environment is a Centos 5.3 with DRBD82 (but also tried with DRBD83 from testing) . Setting up a single primary disk and running bonnie++ on it works. Setting up a dual-primary disk, only mounting it on one node (ext3) and running bonnie++ works When setting up ocfs2 on the /dev/drbd0

We're trying to setup a dual-primary DRBD environment, with a shared disk with either OCFS2 or GFS. The environment is a Centos 5.3 with DRBD82 (but also tried with DRBD83 from testing) . Setting up a single primary disk and running bonnie++ on it works. Setting up a dual-primary disk, only mounting it on one node (ext3) and running bonnie++ works When setting up ocfs2 on the /dev/drbd0

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

We're using a storage solution involving two SunFire X4500 servers using DRBD to replicate a 15TB partition across the network with ocfs2 on top. We're sharing the partition from one server over NFS and the other is mounted read-only at present. The DBRD backing store is software RAID 60 on 40 disks. We've been seeing periodic issues whereby our NFS clients (Debian Lenny) are very

Full updated EL6: Does someone have the same behaviour, unstable eth interface (tg3/no dhcp)? Jan 19 18:01:46 ane kernel: tg3 0000:04:00.0: eth0: Link is up at 1000 Mbps, full duplex Jan 19 18:01:46 ane kernel: tg3 0000:04:00.0: eth0: Flow control is on for TX and on for RX Jan 19 18:01:46 ane kernel: tg3 0000:04:00.0: eth0: EEE is enabled Jan 19 18:01:46 ane NetworkManager[1735]: <info>

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