init can't start with -current on old(ish) userland

[Simon Burge <simonb%NetBSD.org@localhost>]

Hi folks,

When I boot a -current sbmips kernel with today's (June 13 2010)
sources, I get about half a dozen of the following errors:

pid 1(init): ABI set to O32 (e_flags=0x1007)
trap: pid 1(init): sig 11: cause=0x1c epc=0x7dfa5e10 va=0x7dda094f
registers:
[ 0]=00000000 [ 1]=00000000 [ 2]=ffffffff [ 3]=7dda094e
[ 4]=00401054 [ 5]=7dda094e [ 6]=7dd901f4 [ 7]=00000000
[ 8]=00000000 [ 9]=00000000 [10]=004460f0 [11]=2f6c6962
[12]=00000001 [13]=000007de [14]=000007d1 [15]=8fd405e0
[16]=000006fa [17]=7dd9bfd8 [18]=0000005f [19]=7dda08f8
[20]=7dd95038 [21]=7dff8600 [22]=00401054 [23]=7fffddec
[24]=7000000a [25]=7dfab980 [26]=00000000 [27]=00000000
[28]=7dff6fe0 [29]=7fffdd54 [30]=7fffdf90 [31]=7dfa5f08

and then the board wedges.  The last message was:

Process (pid 1) got sig 11    <- cursor stuck here

This userland works with an August 13 2009 kernel.

Before I start digging, is this still known -current lossage?  There's
a couple of similar references to init dieing back in March and April
of this year, but nothing recent.

Cheers,
Simon.