I have a lot of experience tinkering with O2s and they are really bad
when it comes to reliability. Usually though they only have problems
with connectors, the only real problem with them was the Ethernet 
interface
on the first revisions, it was horrible and died all the time. I used
to manage about 50 of them so motherboard replacements were a frequent 
task
for a me...

Try this:

1) Remove all modules and clean connectors. (CPU, sound, disk)

2) Remove all memory modules from motherboard and clean connectors.
   (Remember to always put the largest memory modules in the first bank
    and then smaller and smaller. Otherwise you may experience odd 
problems.)

3) Remove CPU from motherboard and clean connectors. (This silly design
   creates problems when the machine have moved.)

4) Run IDE

Good luck!

Regards

/Christian


> I'm sorry. I mistook and replied to only Mr.Manuel Bouyer. I want to 
> share information, so I will resend it.
> 
> If you have ide on the volume header, you can check memory and cpu 
> using it.
> Select Check Hardware option in the System Maintenance menu.
> 
> On 2004/10/14, at 6:52, Manuel Bouyer wrote:
> 
> > Hi,
> > I rescued a R10000 O2, and I'm installing NetBSD on it.
> > Got lots of lines like:
> > crime: memory error address 36e94680 status 2040000
> > crime: memory error address 36e94880 status 2040000
> > crime: memory error address 36e94880 status 2040000
> > crime: memory error address 36e94880 status 2040000
> >
> > and also 2 lines:
> > crime: cpu error 4 at address 48c09dc
> > crime: cpu error 4 at address 48c11bc
> >
> > Looks like a bad memory module, isn't it ? Could the CPU errors come
> > from memory too ?