From owner-freebsd-current@FreeBSD.ORG Sat Jul 10 03:46:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C43BF16A4CE; Sat, 10 Jul 2004 03:46:16 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78D6F43D31; Sat, 10 Jul 2004 03:46:16 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6A3kB0p077972; Fri, 9 Jul 2004 23:46:11 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6A3k93f077969; Fri, 9 Jul 2004 23:46:10 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 9 Jul 2004 23:46:09 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Marc G. Fournier" In-Reply-To: <20040709144251.X728@ganymede.hub.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Taku YAMAMOTO cc: freebsd-current@freebsd.org cc: Steve Kargl Subject: Re: Native preemption is the culprit [was Re: today's CURRENT lockups] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jul 2004 03:46:16 -0000 On Fri, 9 Jul 2004, Marc G. Fournier wrote: > On Fri, 9 Jul 2004, Steve Kargl wrote: > > > I've tested it on a UP kernel (HTT enabled, ACPI disabled, > > APIC enabled, ULE). Appears to work fine. > > 'k, I just upgraded my machine to latest, running ULE, P4, SMP kernel > (but doesn't find or start up a second CPU) ... just locked solid here > too ... unfortunately, was running X at the time, so don't know if it > locked or panic'd to DDB :( Running non-X right now to see if it happens > again ... I'm now experiencing extremely hard hangs in the following configurations: SMP kernel running SCHED_ULE with hyperthreads SMP kernel running SCHED_4BSD with hyperthreads To generate the load, I'm using the "supersmack" benchark with the select-key.smack query set with 30 client workers and 10,000 transactions. I am able to reliable hang the system with one or two runs. By disabling the "#define PREEMPTION" entry in param.h with SCHED_4BSD, I'm able to complete the benchmark several times in a row without apparent problems. However, I'll leave it running for a few more hours and see if I didn't just "get lucky". I'll then try SCHED_ULE w/o PREEMPTION. By "extremely hard" I mean that I am unable to break into the debugger using a serial break on the serial console. I have not yet been able to run the test on a system with easily accessible NMI but will attempt to do so in the next few days. I'll give UP a spin with various combinations next. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research