>Number:         10186
>Category:       port-sparc
>Synopsis:       Some TMS390Z50 cpu module core dumps
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-sparc-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue May 23 18:40:01 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     Brad Spencer
>Release:        1.4Y supped mid May
>Organization:
	Sitting at home
>Environment:
	
System: NetBSD frodo.eldar.org 1.4Y NetBSD 1.4Y (GENERIC) #5: Mon May  8 02:30:19 EDT 2000     mycroft@lop-nor.ihack.net:/u2/src/sys/arch/sparc/compile/GENERIC sparc


>Description:

I could not find a PR on this...


I have a brand new, old, Sparc 10 with a CPU module that identifies
itself on boot as:

SPARCstation 10  (1 X 390Z50), No Keyboard
ROM Rev. 2.12, 32 MB memory installed,

... and in the boot up messages ...

cpu0 at mainbus0: TMS390Z50 v1 @ 36 MHz, on-chip FPU
cpu0: physical 20K instruction (64 b/l), 16K data (32 b/l): cache enabled

This particular module does not have a SuperCache controller on it.

With this module installed, certain programs will drop core at times
in pretty predictable ways.  In particular, running 'ifconfig -a' a
couple of times will produce bus errors, seg faults, or complains
about invalid command line arguments.  Note that the command is simply
repeated over and over and was not changing.

The following shell script, call it Y, will usually start to act up:

#!/bin/sh

echo $@
exit 0

running stuff like './Y -a' over and over in a row will usually
produce buss errors in a short time, may be 2 out of 5 times it is
run.

I'v tried a couple of different modules of the same type and they all
act the same.


Running with a module that identifies itself as:

SPARCstation 10  (1 X 390Z55), No Keyboard
ROM Rev. 2.12, 32 MB memory installed,

cpu0 at mainbus0: TMS390Z50 v1 @ 40.300 MHz, on-chip FPU
cpu0: physical 20K instruction (64 b/l), 16K data (32 b/l), 1024K external (32 b/l): cache enabled

This is a TMS390 with a SuperCache controller onboard.  This CPU
module appears to work fine.  I have no reason to believe that there
is anything wrong with the hardware in the SS10.

>How-To-Repeat:

Have a TMS390Z50 without a SuperCache controller and run 'ifconfig -a'
a couple of times.  Watch for core dumps.

>Fix:

Unknown.  Some sort of cache flushing problem??  Maybe timeing??


>Release-Note:
>Audit-Trail:
>Unformatted: