similar to: kernel: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out

Hi , all : Sometimes my server network connection on Linux goes down with short message in syslog saying: "[localhost kernel] NETDEV WATCHDOG: eth0: transmit timed out" (or similar). By the way , I installed the CentOS 5.4 x86_64 bit and the kernel version was 2.6.18-164. Has anyone experienced this problem or is it the bug of the kernel ? I restart the network and that problem

Apologies if this is posted on the wrong list, but when I try to get pci passthrough to work on a Wheezy Xen box I get NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out and then not much else works at all. The same hardware works just fine with Xen and Squeeze. It seemed to me that the problem I am seeing is very similar to

Hi all, Another FYI-mail (and just to verify that I'm not going insane here); I recently purchased an ASUS M3A78-EMH HDMI -board with a tri-core Phenom. This is a small uATX-board with all the garnish integrated motherboards are supposed to come with, and fairly well supported in CentOS 5 and other modern distros. When I installed it (~2 months ago) the NIC was not supported; Ethernet

Hi all. I have two servers 2.6.18-308.4.1.el5PAE CentOS release 5.7 (Final) Both have two external gigabit network cards (installed Planet with Realtek r8169 chipset). lspci 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) 04:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) /var/log/messages May 3

Two problems I hope to solve: 1. The switch being used has autoneg off and has port set to 100 full duplex. 2. Many times NIC fails to come up properly during PXE boot: r8169: eth0: link down ADDRCONF(NETDEV_UP): eth0: link is not ready I can't use ethtool to disable autoneg because the nic driver is built into a bzImage. The root fs is currently being mounted via nfs during pxeboot at

Bill, your CentOS 5 RTL8110 page should probably be updated. I've confirmed that there's a newer r8169 driver in the kernel that works with the RTL8110. RealTek's web site now carries the new r8169 instead of the r1000. The newer driver fixed a problem I was having on one host so we should probably recommend it over the older r1000. I've updated my CentOS 4 page. Kirk Bocek

Hi all, I've recently upgraded a system from CentOS 4.4 to CentOS5, and now when the system boots, the r8169 ethernet card doesn't come up. After the boot sequence, if I type "ifup eth1 | ifup eth1.10 | ifup eth1.203" then the adapter starts up ok. It seems to be something with the boot sequence it loads the ethernet adapters a different way around (ie 4.4 eth0 is now

lspci gives 02:04.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Unknown device 8167 (rev 10) insmod r8169 loads the module but doesn;t pick the card up. Im connecting to internet using a live CD. how do i get centos 5(vanilla install) to recognise my lan card!? thanks R

Hi all, Our intranet's WAN interface just stopped working yesterday, and I can't figure it out. The machine has a Gigabyte motherboard, with on-board RTL-8110SC/8169SC Gigabit Ethernet and D-Link PCI NIC for the LAN side. I can get into the LAN side without an issue, but can't see the WAN side at all. [root at intranet ~]# ifconfig eth0 up eth0: unknown interface: No such device

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

I have no output in the logs, but /etc/init.d/network restart fixes the issue. I am rsync/scp (10GB) data from one 100MB Full duplex host to an ASUS M3A78-EM (RTL8111B/C). It locks up around the 1.5GB Tx mark. If I ethtool -s eth0 autoneg off speed 100 duplex full it does not happen again. Ideas? -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -

> > Are you sure you are > > putting the apic= line on the *Xen* grub line, not Linux? > > > The contrary - I am sure that I put the acpi=off in the Linux > Kernel grub line and never even tried to use this on the xen > grub line! > > Does that make everything said in this thread invalid? Yes. The acpi= line must go on the *xen* command line, which will

Yes, acpi=off seems to have decided my problem of instability. Soon, then I will be returning the HD in the machine in production and I dispatched by post the result. -- Leonardo Pinto listas#openlogic dot com br > The troubles went away when adding kernel options "noapic > acpi=off" to > the modules grub line. > > Both noapic and acpi=off make big difference to the

> Like I just mentioned in a different thread, I need to use > the ''noapic'' > options on both the PowerEdge models I''ve tried.. I''ll try to > build up a Xen vs. non-Xen kernel tomorrow or Tuesday and > grab a diff for you. Which PE models are they? We have quite a few different Dell PowerEdge models running 24x7 in the test lab, and

I am having an issue where eth1 is throwing some messages and stops responding. Restarting networking doesn't work and also just bringing down eth1 with 'ifdown' doesn't fix it. I have never seen anything like these messages: eth1: no IPv6 routers present r8169 0000:03:00.0: eth1: rtl_counters_cond == 1 (loop: 1000, delay: 10). r8169 0000:03:00.0: eth1: rtl_chipcmd_cond == 1

I am having an issue where eth1 is throwing some messages and stops responding. Restarting networking doesn't work and also just bringing down eth1 with 'ifdown' doesn't fix it. I have never seen anything like these messages: eth1: no IPv6 routers present r8169 0000:03:00.0: eth1: rtl_counters_cond == 1 (loop: 1000, delay: 10). r8169 0000:03:00.0: eth1: rtl_chipcmd_cond == 1

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

Network stopped just out of the blue leaving this backtrace After this or during this my network switch just stopped working ang got stuck. Maybe the switch made the problem? Thanks, Eliezer Feb 1 04:07:15 localhost kernel: ------------[ cut here ]------------ Feb 1 04:07:15 localhost kernel: WARNING: at net/sched/sch_generic.c:261 dev_watchdog+0x26d/0x280() (Not tainted) Feb 1 04:07:15

On 16/02/2019 02:43, Saurabh Nanda via samba wrote: >>> 2) Is this normal -- fs/cifs/smb2misc.c: Calculated size 157 length 156 >>> mismatch mid 11907 >> Could be a bug or miscalculated length + non critical warning, I also >> see this on master kernel. Either way I doubt it's slowing everything down. >> > Should I file a bug for this? > > >>

So I'm back to this problem. A quick run down of what the original problem was: I have a machine that I'm configuring to use kickstart to setup. It has two builtin ethernet ports (labeled ports 1 and 2) and I'm adding a third one on its PCIe bus. Originally I was using an r8169 clone a default kickstart always put it as eth0 with the builtin ones as eth1 and eth2 respectively. After