Return-Path: <linux-kernel-owner+willy=40w.ods.org-S1030284AbWJSMcV@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1030284AbWJSMcV (ORCPT <rfc822;willy@w.ods.org>);
	Thu, 19 Oct 2006 08:32:21 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030366AbWJSMcV
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Thu, 19 Oct 2006 08:32:21 -0400
Received: from mx2.suse.de ([195.135.220.15]:53640 "EHLO mx2.suse.de")
	by vger.kernel.org with ESMTP id S1030284AbWJSMcU (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Thu, 19 Oct 2006 08:32:20 -0400
To: Andrew Morton <akpm@osdl.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.19-rc2-mm1
References: <20061016230645.fed53c5b.akpm@osdl.org>
	<1161185599.18117.1.camel@dyn9047017100.beaverton.ibm.com>
	<45364CE9.7050002@yahoo.com.au>
	<1161191747.18117.9.camel@dyn9047017100.beaverton.ibm.com>
	<45366515.4050308@yahoo.com.au>
	<1161194303.18117.17.camel@dyn9047017100.beaverton.ibm.com>
	<20061018154402.ef49874a.akpm@osdl.org>
	<1161212465.18117.35.camel@dyn9047017100.beaverton.ibm.com>
	<20061018162507.efa7b91a.akpm@osdl.org>
From: Andi Kleen <ak@suse.de>
Date: 19 Oct 2006 14:32:11 +0200
In-Reply-To: <20061018162507.efa7b91a.akpm@osdl.org>
Message-ID: <p73r6x4bi5w.fsf@verdi.suse.de>
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1236
Lines: 32

Andrew Morton <akpm@osdl.org> writes:

> On Wed, 18 Oct 2006 16:01:05 -0700
> Badari Pulavarty <pbadari@us.ibm.com> wrote:
> 
> > > Is the NMI watchdog ticking over?
> > 
> > I think so.
> > 
> > # dmesg | grep NMI
> > ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
> > ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
> > ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
> > ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
> > testing NMI watchdog ... OK.
> 
> 
> What does it say in /proc/interrupts?
> 
> The x86_64 nmi watchdog handling looks rather complex.
> 
> <checks a couple of x86-64 machines>
> 
> The /proc/interrutps NMI count seems to be going up by about
> one-per-minute.  How odd.   Maybe you just need to wait longer.

That's consistent with a idle machine. The perfctr used by the nmi
watchdog only increases when the CPU isn't halted and when it's idle
it's not doing very much.  When something actually loops it should
increase much faster though.

-Andi
-
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/