From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 09:22:13 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 84B9F16A539 for ; Mon, 19 Jul 2004 09:22:12 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38AE143D41 for ; Mon, 19 Jul 2004 09:22:12 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from pooker.samsco.org (scottl@localhost [127.0.0.1]) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6J9S8NM053125; Mon, 19 Jul 2004 03:28:08 -0600 (MDT) (envelope-from scottl@freebsd.org) Received: from localhost (scottl@localhost)i6J9S80s053122; Mon, 19 Jul 2004 03:28:08 -0600 (MDT) (envelope-from scottl@freebsd.org) X-Authentication-Warning: pooker.samsco.org: scottl owned process doing -bs Date: Mon, 19 Jul 2004 03:28:08 -0600 (MDT) From: Scott Long Sender: scottl@pooker.samsco.org To: Peter Kostouros In-Reply-To: <40FB8313.5050308@melbpc.org.au> Message-ID: <20040719032535.U32601@pooker.samsco.org> References: <40FB8313.5050308@melbpc.org.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org Subject: Re: [panic] setrunqueue 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, 19 Jul 2004 09:22:13 -0000 On Mon, 19 Jul 2004, Peter Kostouros wrote: > Hi > > I received a fatal error and hope the following is useful: This has been observed often recently. There are some suggestions floating around privately on how to fix this, but probably the easiest work-around for now is to undefine PREEMPTION in /sys/i386/include/param.h I'm expecting to get this resolved in some form in the next 24 hours. Scott