From owner-freebsd-current@FreeBSD.ORG Wed Jul 9 01:13:34 2003 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 3558E37B401 for ; Wed, 9 Jul 2003 01:13:34 -0700 (PDT) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C4F243F93 for ; Wed, 9 Jul 2003 01:13:33 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38ldtos.dialup.mindspring.com ([209.86.247.28] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19aA2z-0003p8-00; Wed, 09 Jul 2003 01:11:30 -0700 Message-ID: <3F0BCDE2.C829AD37@mindspring.com> Date: Wed, 09 Jul 2003 01:10:10 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kevin Oberman References: <20030708195738.CD03D5D07@ptavv.es.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4ad810e32c5eb59fc34684cde18afc5efa2d4e88014a4647c350badd9bab72f9c350badd9bab72f9c cc: current ML cc: Steve Kargl cc: Thierry Herbelot 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2003 08:13:34 -0000 Kevin Oberman wrote: > > 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.) This is really strange; I'd like to try and help debug this one (off-list, so we don't bother anyone else with a lot of back and forth). There's actually nothing I could think of that could cause this, unless it's the BIOS accessing what it thinks is a linear access to low-core memory, and it not having a page mapping without the 4M page mapped. If this is happening, it's most likely spamming something on you without DISABLE_PSE, and you just don't know it because it's not important. I could give you a snippet of code, or walk you through writing one, that would make sure to establish 4K page mappings for the whole area that's normally covered by a 4M mapping; if this was able to fix the problem, then it's likely you are being spammed and that your BIOS is doing Very Bad Things(tm). My gut feeling on this is that the APM is spamming memory, though, and you won't be happy with a workaround that doesn't save you from this. Is there any way you could try ACPI on this board, instead of using APM? Or see if the vendor has a BIOS update (making sure you keep an old copy, just in case you want to go back)? -- Terry