On Thu, Apr 12, 2001 at 06:16:19PM +0200, Pierre Tardy wrote:
> so I transcribe the 't' cmd. (note that I cant type anymore after 
> typing "t\rhe" for help

OK.

> >db t
> _cpu_Debugger (should i really trancribe these hexa numbers)

(the hex numbers are useful in some cases, yes, but not right now)
> _panic
> _coredump
> _sigexit
> _sendsig
> _postsig
> _trap(2,0,0)+60a
> fault(?)
> _VOP_BALLOC(1f6c37,20dc68,512780,10,0,2,283f74)+c
> _ffs_write(2) +37e
> uvm_fault(0x1ddb84,0x286000,0,0x1) ->0xe
>     type 8, code[mmu,,ssw]:505trap type 8, code =0x505
> kernel pc=0x1a6bc8
> kernel: MMU fault trap
> Caught exeption in ddb
> _main() +3a6
> _main() +3a6
> db> he (and nothing else can be typed)

This trace does not make any sense for something that is happening during
a boot.  Does the memory information look correct (how much memory it
thinks you have compared to your actual physical RAM)?  Are you running
this machine in MacOS much?  Do you know that the RAM is good?

-allen