Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261522AbVEQQa7 (ORCPT ); Tue, 17 May 2005 12:30:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261807AbVEQQa7 (ORCPT ); Tue, 17 May 2005 12:30:59 -0400 Received: from fire.osdl.org ([65.172.181.4]:6833 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S261522AbVEQQaw (ORCPT ); Tue, 17 May 2005 12:30:52 -0400 Date: Tue, 17 May 2005 09:32:12 -0700 (PDT) From: Linus Torvalds To: "Maciej W. Rozycki" 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: 1350 Lines: 31 On Tue, 17 May 2005, Maciej W. Rozycki wrote: > > On Tue, 17 May 2005, Linus Torvalds wrote: > > > > 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. I'd love to just blame the BIOS, but we've definitely had our own share of bugs too. NMI makes all the fast system call etc stuff much more "exciting", and we've several times had code that does actually disable interrupts for a long time - which may be exceedingly impolite, but then the NMI watchdog makes it a fatal error rather than something that is just a nuisanse. Of course, our own bugs we can fix (and hopefully we have done so - many people _do_ obviously use the NMI watchdog as-is), so yes, in that sense BIOS (and hardware) bugs end up being a special case. 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/