Trap 0x34 panic on 5.1 on Blade 100

Hi,

I've recently acquired a Blade 100 and, as usual for my Sparc boxes,
installed NetBSD. I run 5.0.1 on an Ultra 5 with no problems so I was
somewhat surprised when 5.1 on the Blade 100 kept crashing and
rebooting. This appears to be related to network activity, xterm and
FTP both cause almost immediate crashes while NFS lasts a bit longer.
After the reboot, dmesg shows messages like this:

trap type 0x34: cpu 0, pc=1316c60 npc=1316c64 pstate=44800006<PRIV,IE>
panic: mem address not aligned
Begin traceback...
End traceback...
Frame pointer is at 0xe0016c51
Call traceback:
13e9ea8(11, 5, 0, 0, e0017658, 100a054, e0016d11) fp = e0016d11
12d1764(104, 0, fffe, 1637889, 12d14d0, 7, e0016dd1) fp = e0016dd1
13f1334(1631bb0, e00178d0, e001775e, 59, 1c05d18, 7, e0016ea1) fp =
e0016ea1 
1008b0c(e00178d0, 34, 1316c60, 44800006, 2e05d70, 2e05d10,
e0017021) fp = e0017021 
13ed8e8(2e57488, c0be000, 6fd762f8, 2f8, 2000, c6fc000, e0017201) fp =
e0017201 
13170a0(c0c1002, c, e0017bbc, 10, 5, 0, e00172c1) fp = e00172c1 
13152dc (2e46180, c0c1002, 0, 0, 5, 0, e00173d1) fp = e00173d1
1175ee0 (2ed4e00, 100a4d0, c0c1002, 0, 0, c7880f0, e00174a1) fp =
e00174a1 
1176998 (c788000, 2d00010, 2, 1, 1ff00400000, 79, e0017561) fp =
e0017561 
1008f54(0, 0, e0017ed0, 110340, 1176914, 1, e0017621) fp = e0017621
12bcd44(23, 0, 15d4998, 1824180, 1c05d18, cccc, c785491) fp = c785491

Are there any kernel debug options I could set to get a more readable
traceback?

George