Date: Sun, 22 Aug 2010 00:02:40 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: Stefan Bethke <stb@lassitu.de> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: ichwd causes freeze instead of reset Message-ID: <4C703EF0.3010700@icyb.net.ua> In-Reply-To: <2EF737B3-0FC2-425A-9CE6-07129C12D5B5@lassitu.de> References: <2EF737B3-0FC2-425A-9CE6-07129C12D5B5@lassitu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C703EF0.3010700>