From owner-freebsd-current@FreeBSD.ORG Mon Jul 12 19:27:17 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 BEAA216A4CE for ; Mon, 12 Jul 2004 19:27:17 +0000 (GMT) Received: from winston.piwebs.com (217-19-20-186.dsl.cambrium.nl [217.19.20.186]) by mx1.FreeBSD.org (Postfix) with SMTP id C87CF43D3F for ; Mon, 12 Jul 2004 19:27:16 +0000 (GMT) (envelope-from avleeuwen@piwebs.com) Received: (qmail 54828 invoked from network); 12 Jul 2004 19:27:15 -0000 Received: from vincent.piwebs.com (HELO localhost) (192.168.0.84) by winston.piwebs.com with SMTP; 12 Jul 2004 19:27:15 -0000 To: "Ulrich Spoerlein" , "Ariff Abdullah" References: <20040710150620.7595b207.skywizard@MyBSD.org.my> <20040712190716.GA787@galgenberg.net> Message-ID: From: "Arjan van Leeuwen" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Date: Mon, 12 Jul 2004 21:27:48 +0200 In-Reply-To: <20040712190716.GA787@galgenberg.net> User-Agent: Opera M2/7.52 (FreeBSD, build 727) cc: "freebsd-current@freebsd.org" cc: Robert Watson 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: Mon, 12 Jul 2004 19:27:17 -0000 On Mon, 12 Jul 2004 21:07:16 +0200, Ulrich Spoerlein wrote: > On Sat, 10.07.2004 at 15:06:20 +0800, Ariff Abdullah wrote: >> I'm suspecting bad combination between threaded apps and current >> native preemption, either the preemption itself, or threads. Running >> current kernel without any threaded apps turns up nothing suspicious. >> Once the threaded apps started, it's like sending the entire system to >> the death row. >> >> I'm reverting following files to pre-July 2 to achive solid stability: >> >> sys/sys/interrupt.h - v1.27 >> sys/kern/kern_intr.c - v1.110 >> sys/i386/i386/intr_machdep.c - v1.6 >> sys/kern/sched_ule.c - v1.109 > > I tried to upgrade my kernel from 5.2.1 to -CURRENT and cvsupped > post-preemption. Running a UP-Kernel on a UP-Machine with either > SCHED_ULE or SCHED_BSD froze the machine under heavy load. It doesn't > survive a buildworld or a medium port-build. Same here. > > I tried the revisions above and the machine no longer freezes under > load, but does an instant reboot :( > > Is the machine expected to crash/freeze when running a -CURRENT kernel > on a 5.2R userland? I don't wanna installworld unless I get a rock-solid > kernel, that's in sync with it. This is with an up-to-date world. Arjan -- Using Opera's revolutionary e-mail client: http://www.opera.com/m2/