Colin Wood wrote:

>ummm...unfortunately, it's the whole lot of stuff that's important.  that
>last part is actually a bug in ddb that's fixed in -current ;-)  we need
>to know what the machine was doing when it hung, and that's the part of
>the stack trace that immediately follows the prompt when you type 't'...
>

ok, here it all is:

 Panic switch: PC is at 0x37c2
 Stopped at      _Debugger+0x6:	unlk  a6
 db> ps
 PID       PPID       PGRP       UID   S   FLAGS   COMMAND   WAIT
 0          -1          0         0    3 0X20204    swapper   scsipi_
 db> t
 _Debugger(139e4e,37c2,1eae54,358a,0) + 6
 _nmihand(0,ffffffff,0,0,0) + 26
 _lev7intr(?)
 _mi_switch(2004,2200,0,8,6) + 12
 _tsleep(58c000,11,11c690,0) + 162
 _scsipi_execute_xs(58c000) + ac
 _scsi_scsipi_cmd(584ac0,1eaef2,6,0,0) + 9a
 _scsi_prevent(584ac0,1,180) + 44
 _sdopen(409,0,6000,0) + e8
 _sdsize(409,2004,ffff2200,1e84c8,60b00000) + 58
 _cpu_dumpconf(0,0) + 46
 uvmfault(0x15f860,0x1ed000,0,0,0x1)->0x1
   type 8, code[mmu,,ssw]:402074d
 trap type 8, code=0x402074d, v=0x1edffa
 kernel program counter = 0x13022a
 kernel: MMU fault trap
 caught exception in ddb
 _main() + 39c
 _main() + 39c
 db>

(frozen at this point)

______________________________________________________________________________
Got a device you would like to have run on the Mac? Call:
                 Daniel-the-Driver-Maker
      Fast service - accurate work - responsive support

         (Offer void wherever taxed or prohibited!)