From owner-freebsd-stable@FreeBSD.ORG Mon Oct 20 09:10:58 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9F0816A4B3 for ; Mon, 20 Oct 2003 09:10:58 -0700 (PDT) Received: from smtp3.sentex.ca (smtp3.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9C2743FB1 for ; Mon, 20 Oct 2003 09:10:57 -0700 (PDT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smtp3.sentex.ca (8.12.9p2/8.12.9) with ESMTP id h9KGApeW075714; Mon, 20 Oct 2003 12:10:51 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.12.9p2/8.12.9) with ESMTP id h9KGAqYI020100; Mon, 20 Oct 2003 12:10:53 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.0.0.22.0.20031020121053.07e575c0@209.112.4.2> X-Sender: mdtpop@209.112.4.2 (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Mon, 20 Oct 2003 12:15:01 -0400 To: Jan Grant , stable@freebsd.org From: Mike Tancsa In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new Subject: Re: Expert input required: P4 odd signals, no apparent memory fault, DISABLE_PSE? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Oct 2003 16:10:59 -0000 How recent is your copy of RELENG_4 ? The PSE disable code was committed to the tree already as well as a fix so it would work with APM on the 17th. By default it is disabled. If you look at your dmesg.boot you should see Warning: Pentium 4 CPU: PSE disabled ---Mike At 11:38 AM 20/10/2003, Jan Grant wrote: >I'm tracking -STABLE on a 1.8GHz P4 with 512MB of memory. Roughly since >the PAE changes were MFCed, I've been seeing memory-corruption-related >errors under specific circumstances: for example, a run of > portsdb -fUu >can be guaranteed to generate SIGBUS, SIGILL and SIGSEGVs in a handful >of sh, sed, etc. processes.