PANIC (watchdog)

[Emanuel Strobl]

Am Donnerstag, 20. Oktober 2005 21:37 CEST schrieb Bill Paul:
> > Hello,
> >
> > after I had switched into single user mode I ran installworld where my
> > box paniced. I have ZERO_COPY_SOCKETS with two not committed patches
> > but I think this is unrelated.
> >
> > Thanks,
> >
> > -Harry
>
> I'm waiting for the part where you explain why you have software
> watchdog support in kern_clock.c turned on. As far as I know, it's
> not enabled by default in the GENERIC kernel config, and even if
> it is, you have to twiddle debug.watchdog_enable in order to make
> it trigger.

All I twiddle is watchdogd_enable in /etc/rc.conf... ;)

> I can only conclude that you turned on watchdog support for some
> reason, set up a watchdog app to reset the watchdog timeout every
> so often, and then forgot about it (or else it was enabled as part
> of some other change you made and you weren't aware of it -- maybe one
> of those unrelated things you foolishly chose not to tell us about).
> Presumeably the watchdog app crashed while you were doing your
> installworkd. If that's the case, you shouldn't be surprised when
> the watchdog expiration occurs and dumps you into ddb.

Ok, then this panic is intended if I understood you correctly. I thought it 
would trigger any kind of CPU reset, not a panic.
Everything is fine then...

Thanks,

-Harry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20051020/a49993cd/attachment.bin