similar to: RE: "netdev watchdog" error and non-working sis900network card - solution

> 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

Necessary urgent of a version of xen that it functions. The question, my people, is that I am with a stated period for the delivery of a dedicated server, and bet in the Fedora Core 4/5, however I do not obtain to make to function the versions of xen for this. The problem is that when xen does not break, is the net (xen-br0) that it does not function... Somebody would have the RPMs functional that

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

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

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

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

Hi all, I've got a Portwell NANO-6060 board I am testing out for potential use in a project of ours. One of the nice features of this board, beyond nice NICs, is that it has a hardware watchdog timer. The problem is that I don't get a /dev/watchdog device file. I know the hardware works, because when I enable it in BIOS, the box will reboot after the timer expires. However,

All, I'm having an issue with my menu.c32. I created a menu and it appears correctly, but once I get to my choice, it won't select it and begin the install. Below is my pxelinux.cfg/default: default menu.c32 timeout 600 display boot.msg menu title Welcome to the incNETWORKS RHEL5/6 PXEBOOT Server! menu color border 0 #ffffffff #00000000 menu color sel 7 #ffffffff #ff000000 menu color

Control: tag -1 upstream Jan/Andy & David, Is there anything we can improve here on either the Xen or kernel side do you think? On Thu, 2015-08-13 at 00:59 +0200, Guido G?nther wrote: > Package: xen-hypervisor-4.5-amd64 > Severity: normal > > Hi, > when running xen inside of kvm the hypervisor fails to set up the proper > IRQ routing and suggests to use noapic. FTR, it

I''m at my wits end maybe someone out there can help me. Machine Shuttle AN51R Motherboard 1GB ram AMD-64 3000+ (2GHz) 20GB HD (western digital) with 1GB for minimal install, 500MB for swap, and the rest I had planned to use for LVM volumes for VMs. I''ve been running ubuntu 5.04 (hoary) happy as a clam for a while now no problems. Now I''ve started investigating Xen

I''ve just finished installing it, I''m blog-posting about it. as soon as i finish this post, I''ll let you know. Btw, how can I disable the preview when posting a new article? It''s a little lagged and slowish while I see a dispatcher consuming some considerable cpu time. Thanks. On 7/25/06, Tiago Pinto <thpinto@gmail.com> wrote: > I tried without any

All, I have an GigaByte motherboard GA-M61P-S3 and I was wondering if any kernel watchdog processes will work with that? Jerry ----------------------------- /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog/softdog.ko /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog/ibmasr.ko

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

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

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1336153082 -7200 # Node ID 9a430b7e2df2893f7f4f75d10e66d52bdffa7efa # Parent 113fd57259b91af06a5352404dd94b484a98d2bc tools/hotplug: remove 4 from default runlevel in xen-watchdog, xend and xendomains Similar to what changeset 24847:0900b1c905f1 does in xencommons, remove runlevel 4 from the other runlevel scripts. LSB defines

CentOS 6 Hi all, I am working on setting up sanlock + watchdog on a 2 node KVM pair. Sanlock is working beautifully and is preventing access to the VM disks by more than one process as it should across both boxes. I am attempting to test failure scenarios involving watchdog, but I am having a hard time getting it to actually reset the server. I am running wdmd with -D so I can see the

hi everybody I'm testing Qemu's watchdog. My understanding was that hardware (here qemu's watchdog) would take action(cold reboot) the system if there is no ping from the OS watchdog, so I thought stopping watchdog service in VM should be a quick test. I have this in the guest: <watchdog model='i6300esb' action='reset'> <address

--- Ryan Lane <ryanlane@gmail.com> wrote: > On Fri, 11 Mar 2005 07:21:39 -0800 (PST), Steven > Vishoot > <sir_funzone@yahoo.com> wrote: > > ok now i am frustrated. this is the third day in a > row > > that my server has crashed running centos4, i can > not > > ping or access the console but the hardware is > still > > running. it does not leave