Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267926AbUI1VIc (ORCPT ); Tue, 28 Sep 2004 17:08:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267936AbUI1VIc (ORCPT ); Tue, 28 Sep 2004 17:08:32 -0400 Received: from pollux.ds.pg.gda.pl ([153.19.208.7]:12044 "EHLO pollux.ds.pg.gda.pl") by vger.kernel.org with ESMTP id S267926AbUI1VIY (ORCPT ); Tue, 28 Sep 2004 17:08:24 -0400 Date: Tue, 28 Sep 2004 22:08:21 +0100 (BST) From: "Maciej W. Rozycki" To: Joerg Sommrey Cc: Linux kernel mailing list Subject: Re: nmi watchdog failure on dual Athlon box In-Reply-To: <20040928183103.GA10593@sommrey.de> Message-ID: References: <20040928163324.GA5759@sommrey.de> <20040928183103.GA10593@sommrey.de> 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: 789 Lines: 24 On Tue, 28 Sep 2004, Joerg Sommrey wrote: > |--- lockupcli.c > | > |main () > |{ > | iopl(3); > | for (;;) asm("cli"); > |} > > Does this mean there is a good reason for further investigations on why > the IO-APIC NMI watchdog doesn't work? Until now I thought it would > be ok as long as the local APIC NMI watchdog is set up. Since this program does busy looping, the local APIC NMI watchdog should trigger indeed. It's "cli; hlt" that causes a problem with this watchdog. Something wrong is happening in your system, indeed. Maciej - 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/