From: Mark Lord <kernel@teksavvy.com>
To: Simon Horman <horms@verge.net.au>
Cc: Brad Campbell <brad@fnarfbargle.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
Patrick McHardy <kaber@trash.net>,
Bart De Schuymer <bdschuym@pandora.be>,
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
Date: Fri, 10 Jun 2011 08:37:22 -0400 [thread overview]
Message-ID: <4DF21002.3040708@teksavvy.com> (raw)
In-Reply-To: <20110610025249.GD643@verge.net.au>
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
next prev parent reply other threads:[~2011-06-10 12:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110601011527.GN19505@random.random>
[not found] ` <alpine.LSU.2.00.1105312120530.22808@sister.anvils>
[not found] ` <4DE5DCA8.7070704@fnarfbargle.com>
[not found] ` <4DE5E29E.7080009@redhat.com>
[not found] ` <4DE60669.9050606@fnarfbargle.com>
[not found] ` <4DE60918.3010008@redhat.com>
[not found] ` <4DE60940.1070107@redhat.com>
[not found] ` <4DE61A2B.7000008@fnarfbargle.com>
[not found] ` <20110601111841.GB3956@zip.com.au>
[not found] ` <4DE62801.9080804@fnarfbargle.com>
[not found] ` <20110601230342.GC3956@zip.com.au>
[not found] ` <4DE8E3ED.7080004@fnarfbargle.com>
[not found] ` <isavsg$3or$1@dough.gmane.org>
2011-06-03 16:07 ` KVM induced panic on 2.6.38[2367] & 2.6.39 Brad Campbell
2011-06-06 20:10 ` Bart De Schuymer
2011-06-06 20:23 ` Eric Dumazet
2011-06-07 3:33 ` Brad Campbell
2011-06-07 13:30 ` Patrick McHardy
2011-06-07 14:40 ` Brad Campbell
2011-06-07 15:35 ` Patrick McHardy
2011-06-07 18:31 ` Eric Dumazet
2011-06-07 22:57 ` Patrick McHardy
2011-06-08 0:18 ` Brad Campbell
2011-06-08 3:59 ` Eric Dumazet
2011-06-08 17:02 ` Brad Campbell
2011-06-08 21:22 ` Eric Dumazet
2011-06-10 2:52 ` Simon Horman
2011-06-10 12:37 ` Mark Lord [this message]
2011-06-10 16:43 ` Henrique de Moraes Holschuh
2011-06-12 15:38 ` Avi Kivity
2011-06-07 23:43 ` Brad Campbell
2011-06-07 18:04 ` Bart De Schuymer
2011-06-08 0:15 ` Brad Campbell
[not found] ` <4DEB3AE4.8040700@redhat.com>
[not found] ` <4DEB8872.2060801@fnarfbargle.com>
2011-06-05 13:58 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DF21002.3040708@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=bdschuym@pandora.be \
--cc=brad@fnarfbargle.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@verge.net.au \
--cc=kaber@trash.net \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).