On Jan 24, 2005, at 1:55 PM, Vivek Khera wrote:
On Jan 24, 2005, at 1:44 PM, Emanuel Strobl wrote:
Maybe Sean Kelly can tell us how SW_WATCHDOG interacts with ACPI,
since I
think the problem occurs when the kernel disables ACPI, right? (just
my
"feeling")
Next chance I get I'll play with the SW_
On Jan 24, 2005, at 1:44 PM, Emanuel Strobl wrote:
Maybe Sean Kelly can tell us how SW_WATCHDOG interacts with ACPI,
since I
think the problem occurs when the kernel disables ACPI, right? (just my
"feeling")
Next chance I get I'll play with the SW_WATCHDOG and see if that stops
the problem on my
Am Montag, 24. Januar 2005 19:29 schrieb Vivek Khera:
> On Jan 24, 2005, at 3:11 AM, Emanuel Strobl wrote:
> > kernel will reset the machine. Best would be if I never see watchdog in
> > action but I'm seeing a panic message after some interrupt statistics
> > (see
> > below) and the machine doesn'
On Jan 24, 2005, at 3:11 AM, Emanuel Strobl wrote:
kernel will reset the machine. Best would be if I never see watchdog in
action but I'm seeing a panic message after some interrupt statistics
(see
below) and the machine doesn't power off (like it does without
watchdogd
enabled).
Interesting...
Hello,
I have a kernel with SW_WATCHDOG and simply enabled watchdog in rc.conf.
I haven't found much info on that topic but I guess when the machine hangs
(watchdogd doesn't get a result from the trivial fsck (what's that btw?)) the
kernel will reset the machine. Best would be if I never see wat
