Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265815AbUAKJaa (ORCPT ); Sun, 11 Jan 2004 04:30:30 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265818AbUAKJaa (ORCPT ); Sun, 11 Jan 2004 04:30:30 -0500 Received: from willy.net1.nerim.net ([62.212.114.60]:35589 "EHLO willy.net1.nerim.net") by vger.kernel.org with ESMTP id S265815AbUAKJa3 (ORCPT ); Sun, 11 Jan 2004 04:30:29 -0500 Date: Sun, 11 Jan 2004 10:30:10 +0100 From: Willy Tarreau To: Simon Kirby Cc: Andrew Morton , Marcelo Tosatti , linux-kernel@vger.kernel.org Subject: Re: 2.4.24 SMP lockups Message-ID: <20040111093010.GG545@alpha.home.local> References: <20040109210450.GA31404@netnation.com> <20040110144049.5e195ebd.akpm@osdl.org> <20040111085506.GA6834@netnation.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040111085506.GA6834@netnation.com> User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 820 Lines: 21 On Sun, Jan 11, 2004 at 12:55:06AM -0800, Simon Kirby wrote: > On Sat, Jan 10, 2004 at 02:40:49PM -0800, Andrew Morton wrote: > > > Presumably it's spinning on the lock with interrupts enabled. Make that > > the `NMI' counters in /proc/interrupts are incrementing for all CPUs. > > Actually, on one of the boxes it doesn't seem to be working at all: > > activating NMI Watchdog ... done. > testing NMI watchdog ... CPU#0: NMI appears to be stuck! Could you try with "nmi_watchdog=2" ? This is the only one which works on my ASUS A7M266-D (MPX + dual XP 1800+). Willy - 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/