Hi, somewhat foolishly, I activated watchdogd and ichwd on a remote box, and while testing it (by suspending watchdogd), apparently the watchdog triggered. But instead of resetting, the machine does not react anymore on the serial console. I will have to wait until Monday to get physical access, so it might be hanging or just switched itself off; I have no way of telling right now. ichwd probes as: ichwd0: <Intel ICH7 watchdog timer> on isa0 ichwd0: Intel ICH7 watchdog timer (ICH7 or equivalent) ppc0: cannot reserve I/O port range (not sure why ppc0 is getting involved at that point.) FreeBSD lokschuppen.zs64.net 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #30: Thu Jul 15 12:58:20 UTC 2010 root@lokschuppen.zs64.net:/usr/obj/usr/src/sys/EISENBOOT amd64 Once the box is up again, is it worthwile trying ichwd again, should I try and use SW_WATCHDOG, or forget about it? Thanks, Stefan -- Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
on 21/08/2010 23:33 Stefan Bethke said the following:> Hi, > > somewhat foolishly, I activated watchdogd and ichwd on a remote box, and > while testing it (by suspending watchdogd), apparently the watchdog > triggered. But instead of resetting, the machine does not react anymore on > the serial console. I will have to wait until Monday to get physical access, > so it might be hanging or just switched itself off; I have no way of telling > right now. > > ichwd probes as: ichwd0: <Intel ICH7 watchdog timer> on isa0 ichwd0: Intel > ICH7 watchdog timer (ICH7 or equivalent) ppc0: cannot reserve I/O port range > > (not sure why ppc0 is getting involved at that point.) > > FreeBSD lokschuppen.zs64.net 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #30: Thu > Jul 15 12:58:20 UTC 2010 > root@lokschuppen.zs64.net:/usr/obj/usr/src/sys/EISENBOOT amd64 > > Once the box is up again, is it worthwile trying ichwd again, should I try > and use SW_WATCHDOG, or forget about it?Just test it more while having physical access before making any conclusions. There could be a number of radically different possibilities ranging from hardware peculiarities to configuration problems to pilot errors to etc. -- Andriy Gapon