Date: Tue, 1 Feb 2005 15:21:01 -0500 From: Vivek Khera <vivek@khera.org> To: freebsd-stable@freebsd.org Subject: Re: watchdogd panic when shutdown -p Message-ID: <61570cf864c7224268e103baab780fcf@khera.org> In-Reply-To: <826E7D69-6E39-11D9-802F-000A9578CFCC@khera.org> References: <200501240911.31608.emanuel.strobl@gmx.net> <E7912ED6-6E35-11D9-802F-000A9578CFCC@khera.org> <200501241944.13307.emanuel.strobl@gmx.net> <826E7D69-6E39-11D9-802F-000A9578CFCC@khera.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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_WATCHDOG and see if that stops > the problem on my boxes. Out of sheer luck, the two that have the > problem are at my office, and the two that do not are at my co-lo. > None of the dozen 4.x boxes ever fail to reboot at the co-lo, either, > the once or twice a year I upgrade them. > Verified on one machine that removing SW_WATCHDOG from kernel config gets rid of the endless interrupt errors on reboot. Other machine is primary office server, so will take some coordination to test this.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?61570cf864c7224268e103baab780fcf>