search for: watchdog_timeout

...the latest versions of megatec have a new option "battvolts" to let the user specify these values if needed. Anyway, I'm now adding the values for this option in the compatibility list when I have them (i.e. for that model it will be "battvolts=9.6:13.3"). > -static char watchdog_timeout = 1; /* in minutes */ > +static char watchdog_timeout = 5; /* in minutes */ The frequency at which the timer is reset is much higher than once per minute, so it won't slip and accidentaly let the UPS shutdown. However, I guess some UPSes may be innacurate with values <= 1 minute. This...

Hi, I''ve been trying to use E5520 and X5650 together in an heterogeneous pool without success. I know the combination is not on the official XenServer supported list (http://hcl.xensource.com/CPUPoolsList.aspx), but I thought it would be possible to set the mask anyway and see for myself if the combination works… My problem is that the mask doesn''t "stick" after a

...*************** > *** 680,687 **** > } > > if (strcasecmp(cmdname, "reset.watchdog") == 0) { > ! ser_send_pace(upsfd, SEND_PACE, "C%c", ENDCHAR); > ! ser_send_pace(upsfd, SEND_PACE, "S%02dR0001%c", > watchdog_timeout, ENDCHAR); > > if (watchdog_enabled) { > upsdebugx(2, "Resetting the UPS watchdog."); > --- 688,695 ---- > } > > if (strcasecmp(cmdname, "reset.watchdog") == 0) { > ! comm->sen...

...2.rx_abs_int_delay: 66 dev.em.2.tx_abs_int_delay: 66 dev.em.2.rx_processing_limit: 100 dev.em.2.flow_control: 0 dev.em.2.mbuf_alloc_fail: 0 dev.em.2.cluster_alloc_fail: 0 dev.em.2.dropped: 0 dev.em.2.tx_dma_fail: 0 dev.em.2.tx_desc_fail1: 0 dev.em.2.tx_desc_fail2: 0 dev.em.2.rx_overruns: 0 dev.em.2.watchdog_timeouts: 0 dev.em.2.device_control: 1076888137 dev.em.2.rx_control: 32794 dev.em.2.fc_high_water: 47104 dev.em.2.fc_low_water: 45604 dev.em.2.fifo_workaround: 0 dev.em.2.fifo_reset: 0 dev.em.2.txd_head: 243 dev.em.2.txd_tail: 243 dev.em.2.rxd_head: 1374 dev.em.2.rxd_tail: 1373 dev.em.2.mac_stats.excess_co...

Recently our automated testing system has caught a curious assertion while testing Xen 4.1.5 on a HaswellDT system. (XEN) Assertion ''(sp == 0) || (peoi[sp-1].vector < vector)'' failed at irq.c:1030 (XEN) ----[ Xen-4.1.5 x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e008:[<ffff82c48016b2b4>] do_IRQ+0x514/0x750 (XEN) RFLAGS: 0000000000010093 CONTEXT: