Manuel Bouyer wrote:
> 
> Please use 'tr' to show where it's hung at this point.
> Also, as I suspect it's hung somewhere in wdc code, use ps to get status of
> the atabus0 and atabus1 threads, and use 'trace/t 0t<pid>' to see the
> stack trace of both processes.

The following was hand copied...

db> tr
kernel: page fault trap, code=0
Faulted in DDB; continuing

db> ps
PID PPID PGRP UID S FLAFS    LWPS COMMAND    WAIT
14  0    0    0   2 0x20200  1    atapibus0  sccomp
3   0    0    0   2 0x20200  1    atabus0    wdccmd

db> trace/t 0t14
trace pid 14 at 0xe5ff3f3c
(c1aac1dc, 10, c03ff0f1, 0, 0) at 0xc022d623
(c1aac15c, 981000, 98a000, 0, c010030c) at 0xc0294336

db> trace/t 0t3
trace pid 3 at 0xe5fc6914
(e5126974, 10, c03f97ad, 0, 0) at 0xc022d623
(c1aac124, e5fc6974, a1, 0, 90000) at 0xc01b85e6
[there's a lot more after this]

Martti