From owner-freebsd-current@FreeBSD.ORG  Thu Aug 14 15:29:36 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 1319537B401
	for <current@freebsd.org>; Thu, 14 Aug 2003 15:29:36 -0700 (PDT)
Received: from hysteria.spc.org (hysteria.spc.org [195.206.69.234])
	by mx1.FreeBSD.org (Postfix) with SMTP id C73EE43FCB
	for <current@freebsd.org>; Thu, 14 Aug 2003 15:29:34 -0700 (PDT)
	(envelope-from bms@hysteria.spc.org)
Received: (qmail 2326 invoked by uid 5013); 14 Aug 2003 22:26:45 -0000
Date: Thu, 14 Aug 2003 23:26:45 +0100
From: Bruce M Simpson <bms@spc.org>
To: Adam Migus <adam@migus.org>
Message-ID: <20030814222645.GU1409@spc.org>
References: <52019.192.168.4.2.1060657784.squirrel@mail.migus.org>
	<20030814204531.GB1417@spc.org>
	<40495.204.254.155.100.1060897528.squirrel@mail.migus.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <40495.204.254.155.100.1060897528.squirrel@mail.migus.org>
User-Agent: Mutt/1.4.1i
Organization: SPC
cc: current@freebsd.org
Subject: Re: make buildkernel hang with SCHED_ULE
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Aug 2003 22:29:36 -0000

On Thu, Aug 14, 2003 at 05:45:28PM -0400, Adam Migus wrote:
> I also do testing on a dual Althon and honestly didn't bother to
> research whether they'd have any affect.  Could/would they be
> causing a problem?  I'll recompile without them and try again at any
> rate.

They are old options for enabling hardware cache on machines which have had
a processor upgrade installed, or for enabling Cyrix 5x86 FPU handler options.

They are documented in NOTES. I could find scant documentation on
the FASTFPE bit. http://www.sandpile.org/ia32/ccr.htm#ccr4 suggests that
it was only ever used on the old 486 pin-compatible Cyrix 5x86.

It is possible setting these bits has an undefined effect on your more
recent machines. Try compiling a kernel without them and see if your
scheduler problem manifests itself.

BMS