CPU1 Threading 140 Panic

[comtec17]

Has anyone seen this before? Am I assuming correctly that when I rebooted my machine and received the above error that CPU1 is bad?

I have tried the following:

Stop-a

OK? setenv upa-port-skip-list CPU1
OK? boot

No change and I tried this will all CPU's.

I also re-enabled them with:

OK? setenv upa-port-skip-list none

Please help....

 

[cndcadams]

what model of system. does it reboot when trying to boot or can you login and get to the messages file.

the problem with info you gave is that when a system crashes it is almost always going to show a panic on a cpu. This does not mean that the cpu was the problem all it is saying is that at the time of the panic it was processing info on that cpu. You need to look at /var/adm/messages and extract 15 to 20 lines before the cpu{thread}panic, this is where the actual problems are called out.

post messages info if you can get to it.

thanks

CA

 

[comtec17]

The system is a E450. The system does not even boot up so no way to get the logs.

I spoke with Sun support and they confirmed that it is a bad CPU.

Thanks for the reply!!

 

[siscokid1]

We had this problem running on our E250's, and have
replaced many cpus (some thrice). Sun will not admit it,
but there is a caching problem with the 400mhz
processors.

Here is a link:

http://www.gleezorp.com/scoreboard.html