> fatal kernel trap:
> 
>     trap entry = 0x4 (unaligned access fault)
>     a0         = 0xfffffe004a5f472c
>     a1         = 0x2d
>     a2         = 0x4
>     pc         = 0xfffffc0000351ad4
>     ra         = 0xfffffc00003507dc
>     curproc    = 0xfffffe004a5eae00
>         pid = 144, comm = httpd
> 
> panic: trap

"oh cool!"  I've not seen an unaligned access fault in the kernel for
... a long time.  8-S


could you run gdb on the kernel binary with debugging symbols that
corresponds to the kernel you're running?  (When your kernel was
built, a 'netbsd.gdb' was built at the same time as your 'netbsd'.)

In gdb, 'list *0xfffffc0000351ad4' and 'list *0xfffffc00003507dc', and
reply to this message with the results.



This is probably pretty repeatable, so you can probably cause the same
result on a new kernel if you need to build one from scratch to get a
'reasonable' (i.e. fitting your sources and kernel binary) netbsd.gdb.

If you have to build a new kernel and make it crash (so you have an
up-to-date netbsd.gdb), use the pc and ra values reported by the fatal
trap in those 'list' commands.



chris