smurfd I do get kernel panics with this sometimes apparently.
I should've mentioned, it's riscv, 64 bit, on a Star64.
Here's one with the trapframes omitted (by me)
Nov 5 18:20:14 starkeeper /netbsd: [ 202709.1399809] 31.0299744] trace fp ffffffc17f800690
Nov 5 18:20:14 starkeeper /netbsd: f7b73608 t1 =0xfffffffffffc17f8006d0 vpanic() at ffffffc00033d5e0 netbsd:vpanic+0x13c
Nov 5 18:20:14 starkeeper /netbsd: [ 266031.0499777] fp ffffffc17f8006f0 panic() at ffffffc00033d682 netbsd:panic+0x24
Nov 5 18:20:14 starkeeper /netbsd: [ 266031.0599769] fp ffffffc17f8007d0 heartbeat() at ffffffc0002ee6ee netbsd:heartbeat+0x30c
Nov 5 18:20:14 starkeeper /netbsd: [ 266031.0699747] fp ffffffc17f800810 hardclock() at ffffffc0002da270 netbsd:hardclock+0x6c
Nov 5 18:20:14 starkeeper /netbsd: [ 266031.0799744] fp ffffffc17f800830 riscv_timer_intr() at ffffffc00000fea4 netbsd:riscv_timer_intr+0x4c
So at least that leads me further. It would be nice to know why this happens before reporting it though, and that's frankly more than I know. I may post this on the riscv mailing list.