From owner-freebsd-current@FreeBSD.ORG Sun Jul 4 17:59:10 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 D7B7916A4D0 for ; Sun, 4 Jul 2004 17:59:10 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A07B43D1F for ; Sun, 4 Jul 2004 17:59:10 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from samsco.org (junior-wifi.samsco.home [192.168.0.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i64I3bLD086580; Sun, 4 Jul 2004 12:03:37 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <40E8455D.2000001@samsco.org> Date: Sun, 04 Jul 2004 11:58:53 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kim Culhan References: <20040704174806.66274.qmail@web50703.mail.yahoo.com> In-Reply-To: <20040704174806.66274.qmail@web50703.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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: -current boot fails on htt smp 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: Sun, 04 Jul 2004 17:59:11 -0000 Kim Culhan wrote: > P4 HTT on Supermicro P4SCT+ > > Current of ~1600 utc console output: > > SMP: AP CPU #1 Launched! > > then: > > kernel trap 12 with interrupts disabled > Fatal trap 12: page fault which in kernel mode > cpuid=1; apic id=01 > fault virtual address = 0x30 > fault code =supervisor write, page not present > > Please let me know how I might help further. > > -kim > There was a change on Friday that seems to have broken many systems with SCHED_ULE. Until the author comes back online, I'd recommend switching your kernel config to SCHED_4BSD. Scott