From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 27 Feb 2003 12:11:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 27 Feb 2003 12:11:32 -0500 Received: from air-2.osdl.org ([65.172.181.6]:56005 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id ; Thu, 27 Feb 2003 12:11:31 -0500 Subject: Re: 2.5.62-mjb3 (scalability / NUMA patchset) From: Mark Haverkamp To: "Martin J. Bligh" Cc: linux-kernel , lse-tech In-Reply-To: <4790000.1046300707@[10.10.2.4]> References: <6490000.1045713212@[10.10.2.4]> <16170000.1046110132@[10.10.2.4]> <1046273777.1913.6.camel@markh1.pdx.osdl.net> <3090000.1046274931@[10.10.2.4]> <1046299742.3375.3.camel@markh1.pdx.osdl.net> <4140000.1046300025@[10.10.2.4]> <1046300601.3375.13.camel@markh1.pdx.osdl.net> <4790000.1046300707@[10.10.2.4]> Content-Type: text/plain Organization: Message-Id: <1046366533.13890.4.camel@markh1.pdx.osdl.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 27 Feb 2003 09:22:13 -0800 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2003-02-26 at 15:05, Martin J. Bligh wrote: > >> > I turned on NMI watchdogs and when the system hung, I saw no output. > >> > My serial console is through a terminal server that isn't set up to > >> > pass along the sysrq, so I need to get this fixed. In any case I > >> > backed out the patch that you suggested and I have had no system hangs > >> > since. > >> > >> OK, I'll back out that patch for now, but it seems to indicate underlying > >> crud. What parameter did you set for NMI watchdog? > > > > I set it to 1. In Documentation/nmi_watchdog.txt this looked like the > > only option. Now that I look at apic.h, I see that I could set it to 2 > > also. If you like I can try this also. > > 2 is what we used sucessfully last time, but I can't remember the > difference off the top of my head ... if you could try that, would be most > useful. Still no luck getting a stack trace. With nmi_watchdog=2, I get these kind of messages on occasion: Uhhuh. NMI received for unknown reason 35 on CPU 11. Dazed and confused, but trying to continue Do you have a strange power saving mode enabled? But when the system finally froze, there was nothing. Mark. -- Mark Haverkamp