similar to: how to setup a watchdog?

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

Hi-- On 7/30/23 18:25, zhanghao1 wrote: > A new virtio pci driver is added for listening to vcpus > inside guest. Each vcpu creates a corresponding thread to > periodically send data to qemu's back-end watchdog device. > If a vCPU is in the stall state, data cannot be sent to > back-end virtio device. As a result, the back-end device > can detect that the guest is in the

On Mon, 31 Jul 2023 09:25:12 +0800, "zhanghao1" <zhanghao1 at kylinos.cn> wrote: > A new virtio pci driver is added for listening to vcpus > inside guest. Each vcpu creates a corresponding thread to > periodically send data to qemu's back-end watchdog device. > If a vCPU is in the stall state, data cannot be sent to > back-end virtio device. As a result, the

I want to set up a watchdog process to keep checking if my ups (pi_ups) is reachable. Something is causing the nut-server to die and the restart script doesn't work but stopping and starting it does. > Broadcast message from nut at gw (somewhere) (Mon Jul 23 21:27:05 2018): > > UPS pi_ups at

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,

The message from this sender included one or more files which could not be scanned for virus detection; do not open these files unless you are certain of the sender's intent. ---------------------------------------------------------------------- Hi, I'm seeing the crash below on 6.1 and 6.2 kernels when trying to copy a directory to OCFS2 filesystem. The problem seems to be that

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

Hello, I have a server pfsense in bridge mode to function as transparent FW, the problem is that once I connect the pfsense between my router core and my core switch catalyst a few seconds begin to appear several messages like these: em2: watchdog timeout - resetting em2: watchdog timeout - resetting em2: watchdog timeout - resetting em2: watchdog timeout - resetting And the connection falls

Hi Yonghyeon and All, >From time to time I use a notebook and boot FreeBSD from USB stick. FreeBSD 9.2-i386 works OK. So I tried to use FreeBSD 10.0-i386 BETA2 and the network adapter works for some 10-15 seconds and then stops with diagnostic message "msk0:watchdog timeout". I've found similar case at freebsd-current@ with no workaround. Yes, there is an interrupt storm as well.

Hi, After updating from 7.0-RELEASE to STABLE (around 15/08) my NIC refuses to handle large file transfers. pciconf -lv re0@pci0:4:0:0: class=0x020000 card=0x001a6409 chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8110SB Single-Chip Gigabit LOM Ethernet Controller' class = network subclass = ethernet Log

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

Laine, Thank you for your response. I did use the numa element instead of using qemu commandline and that worked: 16 <cpu mode='custom' match='exact'> ... 34 <numa> 35 <cell id='0' cpus='0-1' memory='1048576' unit='KiB'/> 36 <cell id='1' cpus='2-3' memory='1048576'

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

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, i have a vm which has a poor performance. E.g. top needs seconds to refresh its output on the console. Same with netstat. The guest is hosting a MySQL DB with a webfrontend, its response is poor too. I'm looking for the culprit. Following top in the guest i get these hints: Memory is free enough, system is not swapping. System has 8GB RAM and two cpu's. Cpu 0 is struggling with a

Author: wentaoy Repository: /hg/zfs-crypto/gate Revision: 30bcd690ede94fe16dd95b03178e85b537d48602 Log message: FWARC 2005/367 sun4v watchdog service API FWARC 2006/093 sun4v watchdog API update 6354584 Add watchdog timer support in sun4v Files: create: usr/src/uts/sparc/sys/wdt.h create: usr/src/uts/sun4v/os/wdt.c update: usr/src/uts/common/os/clock.c update: usr/src/uts/sun4/os/cpu_states.c

Hello, Hideaki Goto has written a patch for OpenSSH that adds heartbeat and watchdog functions to OpenSSH: http://www.sc.isc.tohoku.ac.jp/~hgot/sources/openssh-watchdog.html The heartbeat function sends an SSH_MSG_IGNORE packet every <n> seconds to the server, and the watchdog function checks incoming packets only to see if the connection has been interrupted. Where I work, all Internet

CentOS Errata and Bugfix Advisory 2015:2668 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-2668.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: d7a9fb01a178a2dbb1a93d5e5ca7d8744e26ade820da1e95c8250d4a88d7acd2 watchdog-5.6-5.el6.i686.rpm x86_64: