[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110610164341.GA784@khazad-dum.debian.net>
Date: Fri, 10 Jun 2011 13:43:41 -0300
From: Henrique de Moraes Holschuh <hmh@....eng.br>
To: Mark Lord <kernel@...savvy.com>
Cc: Simon Horman <horms@...ge.net.au>,
Brad Campbell <brad@...rfbargle.com>,
Eric Dumazet <eric.dumazet@...il.com>,
Patrick McHardy <kaber@...sh.net>,
Bart De Schuymer <bdschuym@...dora.be>, kvm@...r.kernel.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, netfilter-devel@...r.kernel.org
Subject: Re: KVM induced panic on 2.6.38[2367] & 2.6.39
On Fri, 10 Jun 2011, Mark Lord wrote:
> Something many of us don't realize is that nearly all Intel chipsets
> have a built-in hardware watchdog timer. This includes chipset for
> consumer desktop boards as well as the big iron server stuff.
>
> It's the "i8xx_tco" driver in the kernel enables use of them:
That's the old module name, but yes, it is very useful in desktops and
laptops (when it works). Server-class hardware will have a baseboard
management unit that can really power-cycle the system instead of just
rebooting.
And test it first before you depend on it triggering at a remote location,
as the firmware might cause the Intel chipset watchdog to actually hang the
box instead of causing a proper reboot (happens on the IBM thinkpad T43, for
example).
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists