> On May 13, 2019, at 11:13 AM, Michael van Elst <mlel...@serpens.de> wrote: > > There is a backtrace command, like (the 0t means 'decimal number'): > > bt/t 0t$PID
Thanks. Here is the output: crash> bt/t 0t4904 trace: pid 4904 lid 1 at 0xffff801202736b20 sleepq_block() at sleepq_block+0x97 turnstile_block() at turnstile_block+0x24f mutex_vector_enter() at mutex_vector_enter+0x34a dk_open() at dk_open+0x45 spec_open() at spec_open+0x276 VOP_OPEN() at VOP_OPEN+0x4c vn_open() at vn_open+0x1ed do_open() at do_open+0x112 do_sys_openat() at do_sys_openat+0x68 sys_open() at sys_open+0x24 syscall() at syscall+0x1ec --- syscall (number 5) --- 7365dce3e2ca: Now I suppose the next step is to wade through the source to figure out what is happening? Cheers, Brook
