Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1422661AbXBUQ00 (ORCPT ); Wed, 21 Feb 2007 11:26:26 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1422663AbXBUQ00 (ORCPT ); Wed, 21 Feb 2007 11:26:26 -0500 Received: from gateway-1237.mvista.com ([63.81.120.158]:55355 "EHLO gateway-1237.mvista.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1422661AbXBUQ0Y (ORCPT ); Wed, 21 Feb 2007 11:26:24 -0500 Subject: Re: Linux 2.6.21-rc1 From: Daniel Walker To: Linus Torvalds Cc: Linux Kernel Mailing List , tglx@linutronix.de, mingo@elte.hu In-Reply-To: References: Content-Type: text/plain Date: Wed, 21 Feb 2007 08:24:13 -0800 Message-Id: <1172075053.8577.38.camel@imap.mvista.com> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2.1 (2.8.2.1-3.fc6) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1773 Lines: 37 On Tue, 2007-02-20 at 20:53 -0800, Linus Torvalds wrote: > Ok, the merge window for 2.6.21 has closed, and -rc1 is out there. > > There's a lot of changes, as is usual for an -rc1 thing, but at least so > far it would seem that 2.6.20 has been a good base, and I don't think we > have anything *really* scary here. > > The most interesting core change may be the dyntick/nohz one, where timer > ticks will only happen when needed. It's been brewing for a _loong_ time, > but it's in the standard kernel now as an option. On i386 I get the following, TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 Testing NMI watchdog ... CPU#0: NMI appears to be stuck (24->24)! CPU#1: NMI appears to be stuck (0->0)! CPU#2: NMI appears to be stuck (0->0)! CPU#3: NMI appears to be stuck (0->0)! when I add nmi_watchdog=1 to my boot args which worked on prior kernels. On closer inspection it looks like arch/i386/kernel/io_apic.c : check_timer() --> timer_irq_works() depends on IRQ0 incrementing jiffies which is no longer the case AFAIK. I'm not sure exactly how that relates to the NMI, but the check_timer() function disabled the NMI through the io-apic if it can't get the "timer" working through the io-apic. Daniel - 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/