Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 23 Aug 2010 10:53:46 +0000
From:      "Poul-Henning Kamp" <phk@phk.freebsd.dk>
To:        Jeremy Chadwick <freebsd@jdc.parodius.com>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: Watchdog not being disabled while dumping core 
Message-ID:  <85637.1282560826@critter.freebsd.dk>
In-Reply-To: Your message of "Mon, 23 Aug 2010 03:34:12 MST." <20100823103412.GA21044@icarus.home.lan> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <20100823103412.GA21044@icarus.home.lan>, Jeremy Chadwick writes:

>It was brought to my attention that on FreeBSD with a hardware watchdog
>in use (e.g. ichwd(4) + watchdogd(8)), once the kernel panics, it's
>quite possible for the watchdog to fire (reboot the system) once the
>panic has happened.  This issue basically inhibits the ability for a
>system with a hardware watchdog in place to be able to successfully
>complete doadump().

The good news is that the watchdog hopefully gets your system back
on the air, even if the dumping hangs.

If it is decided to reset/disarm the watchdog before a dump, please
make that a sysctl tunable.



-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?85637.1282560826>