From owner-freebsd-current  Fri Aug 29 15:28:27 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id PAA02619
          for current-outgoing; Fri, 29 Aug 1997 15:28:27 -0700 (PDT)
Received: from pluto.plutotech.com (ken@mail.plutotech.com [206.168.67.137])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA02612
          for <current@FreeBSD.ORG>; Fri, 29 Aug 1997 15:28:21 -0700 (PDT)
Received: (from ken@localhost)
	by pluto.plutotech.com (8.8.5/8.8.5) id QAA25512;
	Fri, 29 Aug 1997 16:28:11 -0600 (MDT)
From: Kenneth Merry <ken@plutotech.com>
Message-Id: <199708292228.QAA25512@pluto.plutotech.com>
Subject: Re: Fatal trap 12 during boot with -current
In-Reply-To: <199708292110.GAA00357@peace.calm.imasy.or.jp> from Hajimu UMEMOTO at "Aug 30, 97 06:10:14 am"
To: ume@calm.imasy.or.jp (Hajimu UMEMOTO)
Date: Fri, 29 Aug 1997 16:28:11 -0600 (MDT)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL28s (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Hajimu UMEMOTO wrote...
> Hi,
> 
> The very recent -current kernel causes fatal trap 12 during boot.
> 
> 			. . . 
> 	Starting final network daemons: moused
> 
> 	Fatal trap 12: page fault while in kernel mode
> 	cpuid = 1
> 	lapic.id = 16777216
> 	fault virtual address	= 0xeffd6dac
> 	fault code		= super visor read, page not present
> 	instruction pointer	= 0x8:0xf019eb23
> 	stack pointer		= 0x10:0xff803e0c
> 	frame pointer		= 0x10:0xff803e2c
> 	code segment		= base 0x0, limit 0xfffff, type 0x16
> 				= DPL 0, pres 1, def32 1, gran 1
> 	processor eflags	= interrupt enabled, resume, IOPL = 0
> 	current process		= Idle
> 	mp_lock			= 01000003
> 	interrupt mask		=  <- SMP: XXX
> 	kernel: type 12 trap, code=0
> 
> 	CPU1 stopping CPUs: 0x00000001
> 	 stopped
> 	Stopped at	_pmap_enter+0xb3:	movl	0(%ecx),%ecx
> 	db>

	Just for the record, I compiled a -current SMP kernel a few days
ago, and got a similar (possibly the same) panic.  Unfortunately, I didn't
have a serial console or remote gdb enabled, so I couldn't get any error
output for it.  (thus the reason I didn't send in a bug report...*sigh*)

	Out of curiosity, what motherboard do you have in your machine?  
I've got an ASUS P/I-P65UP5 w/ C-P6ND CPU card.


Ken
-- 
Kenneth Merry
ken@plutotech.com