On Sun, 6 Apr 1997 04:30:30 +0200 (MDT) 
 Michael Joosten <joost@c-lab.de> wrote:

 > Apr  6 00:52:15 hp400 /netbsd: apkbd0: cfcr 1b div 81a0
 > Apr  6 00:52:22 hp400 /netbsd: apkbd0:  rxrdy 6d
 > apkbd0:  rxrdy 6d
 > Apr  6 00:52:22 hp400 /netbsd: apkbd0:  rxrdy 6d
 > Apr  6 00:52:22 hp400 /netbsd: apkbd0:  rxrdy 6d
 > panic: dmago: count > MAXPHYS                       <------ very mystic....

...wow... that isn't supposed to happen... A stack trace here would
have been nice... If this happens again (I really hope it doens't,
but if it does...), I'd really like to know where this was called
from...

 > INCORRECT BLOCK COUNT I=1289 (96 should be 32)
 > CORRECT? [yn] y
 > <and so on....>
 > PARTIALLY ALLOCATED INODE I=3879
 > CLEAR? [yn] y
 > 
 > PARTIALLY ALLOCATED INODE I=3889
 > CLEAR? [yn] y
 > 
 > <and so on>
 > 
 > Next attempt:
 > root on sd0a swap on sd0b
 > root file system type: ffs
 > init: not found
 > panic: no init
 > Stopped at      _Debugger+0x6:  unlk    a6
 > db> 

Ugh, so looks like you panic'd when some file system update was happening
and it screwed it up pretty badly ... :-/

 > Halleluja! And now I've to dig out the SLC with netbsd on it to boot and
 > reinstall..... @%$^%@$#^%

Blech.  I can't help but wonder if the frodo/apci code is doing something
to trash the stack... (Note the previous panic posted here...)

Jason R. Thorpe                                       thorpej@nas.nasa.gov
NASA Ames Research Center                               Home: 408.866.1912
NAS: M/S 258-6                                          Work: 415.604.0935
Moffett Field, CA 94035                                Pager: 415.428.6939