Well as I suspected I don't think it had anything to do with the missing
/dev nodes.  Everything is in place now and still it does the same
thing.

The kernel giving this panic is of course a DIAGNOSTIC kernel, whereas I
was able to successfully complete a CD-ROM sysinst install with the
INSTALL kernel that doesn't have DIAGNOSTIC defined (once I had a SCSI
CD-ROM attached in order to avoid the IDE/USB/whatever interrupt
problems.

I've been running kernels with DIAGNOSTIC defined on my AS4000 all along
without ever seeing this problem.

root on sd1a
readclock: 4/9/27/4/35/29=>1096259729 (1096253740)
init: copying out path `/sbin/init' 11
panic: pmap_remove: managed page without PG_PVLIST for 0xfffffe003dc86000
Stopped in pid 1 (init) at      cpu_Debugger+0x4:       ret     zero,(ra)
db> trace
cpu_Debugger() at cpu_Debugger+0x4
panic() at panic+0x160
pmap_do_remove() at pmap_do_remove+0x380
pmap_remove() at pmap_remove+0x78
uvm_unmap_remove() at uvm_unmap_remove+0x200
uvm_km_free_wakeup() at uvm_km_free_wakeup+0x128
sys_execve() at sys_execve+0x8dc
start_init() at start_init+0x310
esigcode() at esigcode
--- root of call graph ---
db> show map
MAP 0xfffffc0000674e18: [0xfffffe0000000000->0xffffffffffffe000]
        #ent=9, sz=1049862144, ref=1, version=27, flags=0x1
        pmap=0xfffffc000080f3a0(resident=111670)
db> show map 0xfffffe003dc86000
MAP 0xfffffe003dc86000: [0x0->0x0]
        #ent=0, sz=0, ref=0, version=0, flags=0x0

CPU 0: fatal kernel trap:

CPU 0    trap entry = 0x2 (memory management fault)
CPU 0    a0         = 0x74696e89
CPU 0    a1         = 0x1
CPU 0    a2         = 0x0
CPU 0    pc         = 0xfffffc00004e39e4
CPU 0    ra         = 0xfffffc00004e39d0
CPU 0    pv         = 0xfffffc0000441360
CPU 0    curproc    = 0xfffffc007aec4000
CPU 0        pid = 1, comm = init

Caught exception in ddb.
db> 

-- 
						Greg A. Woods

+1 416 218-0098                  VE3TCP            RoboHack <woods@robohack.ca>
Planix, Inc. <woods@planix.com>          Secrets of the Weird <woods@weird.com>