similar to: kernel NETDEV WATCHDOG: eth0: transmit timed out

Hi, anybody know how to fix this. May 20 12:16:15 wolfpac kernel: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out May 20 12:16:15 wolfpac kernel: Modules linked in: pf_ring(U) af_key iptable_nat ipt_LOG iptable_filter ip_tables nf_conntrack_ipv6 nf_defrag_ipv6 xt_state ip6t_LOG xt_limit ip6table_filter ip6_tables bridge stp llc nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4

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

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

A bunch of drivers want to know which tx queue triggered a timeout, and virtio wants to do the same. We actually have the info to hand, let's just pass it on to drivers. Note: tested with an experimental virtio patch by Julio. That patch itself isn't ready yet though, so not included. Other drivers compiled only. Michael S. Tsirkin (3): netdev: pass the stuck queue to the timeout

Sorry about the churn, v10 was based on net - not on net-next by mistake. A bunch of drivers want to know which tx queue triggered a timeout, and virtio wants to do the same. We actually have the info to hand, let's just pass it on to drivers. Note: tested with an experimental virtio patch by Julio. That patch itself isn't ready yet though, so not included. Other drivers compiled only.

Sorry about the churn, v10 was based on net - not on net-next by mistake. A bunch of drivers want to know which tx queue triggered a timeout, and virtio wants to do the same. We actually have the info to hand, let's just pass it on to drivers. Note: tested with an experimental virtio patch by Julio. That patch itself isn't ready yet though, so not included. Other drivers compiled only.

Yet another forward declaration I missed. Hopfully the last one ... A bunch of drivers want to know which tx queue triggered a timeout, and virtio wants to do the same. We actually have the info to hand, let's just pass it on to drivers. Note: tested with an experimental virtio patch by Julio. That patch itself isn't ready yet though, so not included. Other drivers compiled only.

A bunch of drivers want to know which tx queue triggered a timeout, and virtio wants to do the same. We actually have the info to hand, let's just pass it on to drivers. Note: tested with an experimental virtio patch by Julio. That patch itself isn't ready yet though, so not included. Other drivers compiled only. Michael S. Tsirkin (3): netdev: pass the stuck queue to the timeout

A bunch of drivers want to know which tx queue triggered a timeout, and virtio wants to do the same. We actually have the info to hand, let's just pass it on to drivers. Note: tested with an experimental virtio patch by Julio. That patch itself isn't ready yet though, so not included. Other drivers compiled only. Michael S. Tsirkin (3): netdev: pass the stuck queue to the timeout

Good morning! On a CentOS 6.4 / 64 bit server I have installed the watchdog 5.5 package. The rpm -qi watchdog states: The watchdog program can be used as a powerful software watchdog daemon or may be alternately used with a hardware watchdog device such as the IPMI hardware watchdog driver interface to a resident Baseboard Management Controller (BMC). ... This configuration file is also used to

Hello I have some problems with 3Com nics, after a upgrade from 5.5-STABLE to 6.4-STABLE. This machine has two 3com nics (one is LAN other is WAN) and i see too much "watchdog timeout" on both cards. This on/off up/down on cards, affect the interrupt to clients that are downloading from apache web server, especially on large files. --------------------------------------------

Dear Developers, I've released a patch against openssh-2.5.2p2. The patch adds heartbeat (keepalive) function to ssh(1), and watchdog timeout function to sshd(8). The watchdog timeout is intended to terminate user's processes as soon as possible after the link has been lost. http://www.ecip.tohoku.ac.jp/~hgot/sources/openssh-watchdog.html The combination of the heartbeat and the

Hi Michael, Em sex., 22 de nov. de 2019 ?s 07:31, Michael S. Tsirkin <mst at redhat.com> escreveu: > > On Thu, Nov 21, 2019 at 10:36:36PM -0300, Julio Faracco wrote: > > Driver virtio_net is not handling error events for TX provided by > > dev_watchdog. This event is reached when transmission queue is having > > problems to transmit packets. This could happen for any

Hi Michael, Em sex., 22 de nov. de 2019 ?s 07:31, Michael S. Tsirkin <mst at redhat.com> escreveu: > > On Thu, Nov 21, 2019 at 10:36:36PM -0300, Julio Faracco wrote: > > Driver virtio_net is not handling error events for TX provided by > > dev_watchdog. This event is reached when transmission queue is having > > problems to transmit packets. This could happen for any

Hello Nut Devs, I'm working with usbhid-ups and a Tripplite OMNI1000LCD. I used a USB packet sniffer to discover something cool about the watchdog feature in this unit. (not sure if the other OMNI-X-LCD models work the same or not.) Basically there's a single HID variable at Report ID 0x52 (UPS.OutletSystem.Outlet.ffff0092) that's one byte (0-255 int) and it contains the Watchdog

Hi! I''m trying to run w83627hf_wdt.ko watchdog driver in domain 0 (xenlinux 2.6.10-xen0), but the driver doesn''t seem to work (the machine reboots all the time after the watchdog-timeout set in BIOS). Is there something that could prevent the driver from accessing the watchdog-hardware (io-ports/registers) ? The watchdog-driver is very simple, and you can find it in

This patch is based on one which has been in XenServer for a very long. To keep the trend of documentation going, it also corrects the new command line document. -- Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer T: +44 (0)1223 225 900, http://www.citrix.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

Got some solutions myself. LAG is caused by : NETDEV WATCHDOG eth0 timeout this is caused bacause of problems with rtl8139 network card in kernel 2.6.x Solutions : 1.add in lilo.conf : append="noapic" 2.turn apic off in bios 3.if u have 2 rtl8139 cards, then exchange one with some other card type (chipset) btw. all above was found in various polish forums, but none has worked for