On Wed, May 04, 2005 at 07:46:27AM -0600, Tillman Hodgson wrote:
> On Tue, May 03, 2005 at 09:39:56PM -0600, Tillman Hodgson wrote:
> > I'm working on a friends SS20, which I've added a bit of RAM to
> > (64MB->96MB) and updated it to NetBSD 2.0.2 with the GENERIC-SMP
> > kernel. Everything boots normally and seems fine, except that when I run
> > startx I get:
> > 
> > xcall(cpu1,0xf0287c50): couldn't ping cpus:cpu0
> 
> Following up on this, I left the box over-night and it died with a
> similar error at some point -- I discovered this in the morning, so I'm
> not sure exactly what was happening when it died (though the launch of
> /etc/daily seems a likely time). So it no longer appears to be
> specifically an X issue.

Following up again, I managed to catch the box dying over the serial
console (which I have remote access to):

ares# cpu0: NMI: system interrupts: 40000000<VME=0,SBUS=0,ME>
module0:
        mxcc error 0x0
        mxcc status 0xff1410002
        mxcc reset 0x0
module1:
        mxcc error 0x0
        mxcc status 0xff1402000
        mxcc reset 0x4 (WATCHDOG RESET)
0tore bType  'ogo' to  resuure me
 T0yp01e .  htrelp .. foLevel 15 Interrupt
Type  help  for more information
<#0> ok

Is there anything from here that I could be doing to aid with
debugging?

-T


-- 
A world is supported by four things:  the teaming of the wise, the justice of 
the great, the prayers of the righteous, and the valor of the brave.  But all 
of these are as nothing without a ruler who knows the art of ruling.
	- Prince Raphael Corrino, Discourses on Galactic Leadership