At 01:21 PM 12/29/2003, Manuel Kasper wrote:
>It makes perfect sense to me now: at 100.0% CPU load (mostly interrupts),
>that poor watchdogd process starves and doesn't get to tickle the watchdog
>again. After about 30 seconds, the watchdog timer fires, the CPU is reset
You could prove that by having the watchdog process syslog a message before
It =does= make sense. That would be why polling helped--it stopped the
But I'd prefer the watchdog be left in. It guarantees that userland
processes are getting some time to run, which is its whole point.
Actually, at some level, trying to pump tens of megabits through a net45xx
is an academic effort anyway. As I've pointed out, it's way faster than a
T1 even when running a VPN or two in software. If you =really= need more
than that, buy a net48xx. Or build a box around an Athlon motherboard.
Chad R. Larson (CRL22) chad at eldocomp dot com
Eldorado Computing, Inc. 602-604-3100
5353 North 16th Street, Suite 400
Phoenix, Arizona 85016-3228
-- CONFIDENTIALITY NOTICE --
This message is intended for the sole use of the individual and entity to whom it is addressed, and
may contain information that is privileged, confidential and exempt from disclosure under applicable
law. If you are not the intended addressee, nor authorized to receive for the intended addressee,
you are hereby notified that you may not use, copy, disclose or distribute to anyone the message or
any information contained in the message. If you have received this message in error, please
immediately advise the sender by reply email, and delete the message. Thank you.