Brett Lymn wrote:
  > Yes, please build a debug kernel and do a back trace of the crash.
> That will be the fastest way to get this resolved.  If you can, get a
> kernel core dump too as that may be useful.

I can't get a crashdump in my current configuration (RAIDFrame, and I 
don't like the 'overlapping partitions' dance), but I was able to get a 
backtrace:

[snip]
Updating motd.
Starting ntpd.
Starting powerd.
Starting sshd.
Restoring mixer settings: mixer0kernel: protection fault trap, code=0
Stopped in pid 756.1 (raidctl) at 
netbsd:specificdata_getspecific+0x12:   c
mpq     0(%rax),%rdx
db> bt
specificdata_getspecific() at netbsd:specificdata_getspecific+0x12
fileassoc_file_lookup() at netbsd:fileassoc_file_lookup+0x1c
fileassoc_lookup() at netbsd:fileassoc_lookup+0x13
veriexec_purge() at netbsd:veriexec_purge+0x9
fileassoc_table_run() at netbsd:fileassoc_table_run+0x66
veriexec_raw_cb() at netbsd:veriexec_raw_cb+0x155
kauth_authorize_action() at netbsd:kauth_authorize_action+0xa0
kauth_authorize_device_spec() at netbsd:kauth_authorize_device_spec+0x2f
spec_open() at netbsd:spec_open+0x16f
VOP_OPEN() at netbsd:VOP_OPEN+0x2a
vn_open() at netbsd:vn_open+0x264
sys_open() at netbsd:sys_open+0xeb
syscall_plain() at netbsd:syscall_plain+0x112
--- syscall (number 0) ---
0:
db>