See PR 7174.  It still happens in -current.

Darrin

der Mouse  <mouse@Rodents.Montreal.QC.CA> writes:

> As I mentioned in my previous note, I've finally started playing with
> the next68k port.  I just now had occasion to reboot the box (same
> kernel as last time I booted), and...it died.  Here's what I see
> (ten-finger transcription, but I don't *think* there are any typos):
> 
> NetBSD 1.4 (GENERIC) #0: Fri Aug 13 17:59:97 PDT 1999
>     root@NeXT.Rodents.Montreal.QC.CA:/usr/src/sys/arch/next68k/compile/GENERIC
> NeXT/MC68040 CPU+MMU+FPU, 4k on-chip physical I/D caches
> real mem  = 16769024
> panic: pmap_enter_ptpage: PT page not entered
> Stopped in  at  _Debugger+0x6:  unlk    a6
> db> trace
> _Debugger(2704,1,419f000,0,157c84) + 6
> _panic(c9cd5,1000,0,fffffffe,1) + 52
> _pmap_enter_ptpage(100708,1400000) + 50c
> _pmap_enter(100708,1400000,42c8000,3,1) + b8
> _cpu_startup(17d54,e63b4,4001000,0,d952c) + 16e
> _main(2663e,15b000,0,1000,1000) + 38
> db> 
> 
> Two successive reboot attempts failed with the same panic at apparently
> the same place (I didn't check the stack trace).  But when I did the
> ctl-alt-* hard-reset, let it try to boot and fail because it tries to
> boot en() instead of en()/netbsd, and then type en()/netbsd at the
> boot: prompt, it came up normally.
> 
> Worth investigating, or should I ignore this until/unless it happens
> again with -current?  I'm preparing to move to -current....
> 
> 					der Mouse
> 
> 			       mouse@rodents.montreal.qc.ca
> 		     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B