Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261806AbVEQQHV (ORCPT ); Tue, 17 May 2005 12:07:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261751AbVEQQFd (ORCPT ); Tue, 17 May 2005 12:05:33 -0400 Received: from pollux.ds.pg.gda.pl ([153.19.208.7]:37386 "EHLO pollux.ds.pg.gda.pl") by vger.kernel.org with ESMTP id S261755AbVEQP7Z (ORCPT ); Tue, 17 May 2005 11:59:25 -0400 Date: Tue, 17 May 2005 16:59:29 +0100 (BST) From: "Maciej W. Rozycki" To: Linus Torvalds Cc: Kirill Korotaev , "Martin J. Bligh" , Andrew Morton , linux-kernel@vger.kernel.org Subject: Re: [PATCH] NMI watchdog config option (was: Re: [PATCH] NMI lockup and AltSysRq-P dumping calltraces on _all_ cpus via NMI IPI) In-Reply-To: Message-ID: References: <42822B5F.8040901@sw.ru> <768860000.1116282855@flay> <42899797.2090702@sw.ru> 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: 919 Lines: 20 On Tue, 17 May 2005, Linus Torvalds wrote: > > BTW, why NMI watchdog is disabled by default? We constantly making it on > > by default in our kernels and had no problems with it. > > I send a patch attached which tunes NMI watchdog by config option... > > I really don't want NMI watchdogs enabled by default. It's historically > been _very_ fragile on some systems. Whether that has been due to harware > or sw bugs, I dunno, but it's definitely been problematic. Mostly or perhaps even exclusively due to BIOS bugs -- you know, that piece of hidden firmware that runs in the SMM under our feet and fiddles randomly with hardware we can do nothing about. 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/