On Mon, Aug 23, 2010 at 04:07:47AM -0700, Xin LI wrote:
> On Mon, Aug 23, 2010 at 3:34 AM, Jeremy Chadwick
> wrote:
> > PR bin/145183, opened in 2010 (not sure if this is the same):
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/145183
>
> Speaking for this I think we can do it by issuing an
In message <4c725dfc.8000...@icyb.net.ua>, Andriy Gapon writes:
>on 23/08/2010 13:53 Poul-Henning Kamp said the following:
>> In message <20100823103412.ga21...@icarus.home.lan>, Jeremy Chadwick writes:
>Another workaround is to set watchdog timeout large enough for dumping to
>complete, but that
on 23/08/2010 13:53 Poul-Henning Kamp said the following:
> In message <20100823103412.ga21...@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 poss
On Mon, Aug 23, 2010 at 3:34 AM, Jeremy Chadwick
wrote:
> PR bin/145183, opened in 2010 (not sure if this is the same):
> http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/145183
Speaking for this I think we can do it by issuing an explicit
watchdog(8) command on shutdown (like, set the timeout to s
In message <20100823103412.ga21...@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 ha
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 hardwar
