From owner-freebsd-current@FreeBSD.ORG  Tue Jul  8 12:57:43 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 C919637B401
	for <current@freebsd.org>; Tue,  8 Jul 2003 12:57:43 -0700 (PDT)
Received: from postal1.es.net (postal1.es.net [198.128.3.205])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2B77543FB1
	for <current@freebsd.org>; Tue,  8 Jul 2003 12:57:41 -0700 (PDT)
	(envelope-from oberman@es.net)
Received: from ptavv.es.net ([198.128.4.29])
        by postal1.es.net (Postal Node 1) with ESMTP (SSL) id MUA74016;
        Tue, 08 Jul 2003 12:57:39 -0700
Received: from ptavv (localhost [127.0.0.1])
	by ptavv.es.net (Tachyon Server) with ESMTP
	id CD03D5D07; Tue,  8 Jul 2003 12:57:38 -0700 (PDT)
To: Thierry Herbelot <thierry@herbelot.com>
In-Reply-To: Message from Thierry Herbelot <thierry@herbelot.com> 
	<200307082147.23042.thierry@herbelot.com> 
Date: Tue, 08 Jul 2003 12:57:38 -0700
From: "Kevin Oberman" <oberman@es.net>
Message-Id: <20030708195738.CD03D5D07@ptavv.es.net>
cc: current ML <current@freebsd.org>
cc: Steve Kargl <sgk@troutmask.apl.washington.edu>
Subject: Re: systematic panic on an SMP machine for 5.1-Release 
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: Tue, 08 Jul 2003 19:57:44 -0000

> From: Thierry Herbelot <thierry@herbelot.com>
> Date: Tue, 8 Jul 2003 21:47:23 +0200
> Sender: owner-freebsd-current@freebsd.org
> 
> PS : is this an indication of bug in the p-III or in the chipset ?
> (ISTR these options could be used to get around unnamed errata of
> the p-IV)

Terry has never been specific (due to non-disclosure), but adding
options DISABLE_PSE to the kernel of my P4 system results in a solid
crash when the apm driver probes. (This could be an apm(4) problem, as
well.)

I wish I knew just when this option might be needed as I run on a wide
variety of platforms including P2, K6-3, P3, and P4 with an Athlon
coming soon. I'd just as soon only use this option where it's really
required. I'm twice shy about it after adding it to the P4 and
watching it crash.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634