Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261712AbVEQPuW (ORCPT ); Tue, 17 May 2005 11:50:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261648AbVEQPuV (ORCPT ); Tue, 17 May 2005 11:50:21 -0400 Received: from fire.osdl.org ([65.172.181.4]:12708 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S261724AbVEQPrQ (ORCPT ); Tue, 17 May 2005 11:47:16 -0400 Date: Tue, 17 May 2005 08:48:37 -0700 (PDT) From: Linus Torvalds To: Kirill Korotaev cc: "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: <42899797.2090702@sw.ru> 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: 714 Lines: 18 On Tue, 17 May 2005, Kirill Korotaev 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. Linus - 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/