I see the same crime errors, but do not get the crash.
Are you netbooting?

-Jaime Fournier
ober@NetBSD.org

On Sun, 15 Apr 2007, david l goodrich wrote:

> Date: Sun, 15 Apr 2007 17:22:33 -0500
> From: david l goodrich <dlg@dsrw.org>
> To: Jared D. McNeill <jmcneill@invisible.ca>
> Cc: port-sgimips@NetBSD.org
> Subject: R10k errors (was: Re: R10k O2 won't boot)
> 
> On Sun, Apr 15, 2007 at 04:02:10PM -0400, Jared D. McNeill wrote:
>>
>> Please grab the file again (built this time w/ mec debugging
>> disabled). MD5: d717a0131ceb5482001ccfad4086184c
>>
>
> alright, we're booted, thanks for the updated kernel.
>
> I'm downloading pkgsrc now from cvs.
>
> or, I was.
>
> i see these errors on the console:
> crime: cpu error 4 at address 4519850
> crime: cpu error 4 at address 4519858
> crime: cpu error 4 at address 4569da4
> crime: cpu error 4 at address 4569da8
>
> and the checkout stops (i was doing this from an ssh connection)
> here:
> ...
> cvs checkout: Updating pkgsrc/archivers/star/patches
> U pkgsrc/archivers/star/patches/patch-aa
> U pkgsrc/archivers/star/patches/patch-ab
> cvs checkout: Updating pkgsrc/archivers/stuffit
> U pkgsrc/archivers/stuffit/DESCR
> U pkgsrc/archivers/stuffit/Makefile
> U pkgsrc/archivers/stuffit/PLIST
> U pkgsrc/archivers/stuffit/distinfo
> cvs checkout: Updating pkgsrc/archivers/stuffit/pkg
> cvs checkout: Updating pkgsrc/archivers/szdd
>
> and the machine is not responding at the serial console.
>
> It seems likely that the R10k is still not supported.
>  --david
>