Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756829Ab1FJMh3 (ORCPT ); Fri, 10 Jun 2011 08:37:29 -0400 Received: from ironport2-out.teksavvy.com ([206.248.154.181]:17176 "EHLO ironport2-out.pppoe.ca" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755273Ab1FJMh1 (ORCPT ); Fri, 10 Jun 2011 08:37:27 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApIBAFkP8k1Ld/sX/2dsb2JhbAAMRoRJ2E6QaIErg26BCgShHg X-IronPort-AV: E=Sophos;i="4.65,347,1304308800"; d="scan'208";a="115999779" Message-ID: <4DF21002.3040708@teksavvy.com> Date: Fri, 10 Jun 2011 08:37:22 -0400 From: Mark Lord User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: Simon Horman CC: Brad Campbell , Eric Dumazet , Patrick McHardy , Bart De Schuymer , kvm@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, netfilter-devel@vger.kernel.org Subject: Re: KVM induced panic on 2.6.38[2367] & 2.6.39 References: <4DED344D.7000005@pandora.be> <4DED9C23.2030408@fnarfbargle.com> <4DEE27DE.7060004@trash.net> <4DEE3859.6070808@fnarfbargle.com> <4DEE4538.1020404@trash.net> <1307471484.3091.43.camel@edumazet-laptop> <4DEEACC3.3030509@trash.net> <4DEEBFC2.4060102@fnarfbargle.com> <1307505541.3102.12.camel@edumazet-laptop> <4DEFAB15.2060905@fnarfbargle.com> <20110610025249.GD643@verge.net.au> In-Reply-To: <20110610025249.GD643@verge.net.au> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 964 Lines: 27 On 11-06-09 10:52 PM, Simon Horman wrote: > On Thu, Jun 09, 2011 at 01:02:13AM +0800, Brad Campbell wrote: >> On 08/06/11 11:59, Eric Dumazet wrote: >> >>> Well, a bisection definitely should help, but needs a lot of time in >>> your case. >> >> Yes. compile, test, crash, walk out to the other building to press >> reset, lather, rinse, repeat. >> >> I need a reset button on the end of a 50M wire, or a hardware watchdog! 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: modprobe i8xx_tco Cheers -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/