  Copyright(c) 1999 Sun Microsystems, Inc.
  All rights reserved.

  "@(#)cpudatatest.txt  1.4  99/06/04  SMI"



CPU Data Test (cpudatatest) [for SUNWvts 3.0]
---------------------------

cpudatatest checks specific aspects of a processor's 
datapath functionality. It implements two subtests:

1) CUC - tests a processors ability to correctly 
execute a Compress/Uncompress/Compare(cmp)
command sequence on machines with the SPARC V9 
based architecture.

2) g0 - tests a processors's g0 register functionality.
              
cpudatatest was developed to augment the existing sunvts
test suite in response to:

(CUC)	Service Order:		5146606
	Escalation:		515948
	BugId:			4159925

(g0)   	Service Order:          
	Escalation:             517291
	BugId:                  4183870

Related documentation: 
	patch README file:	README.107543-01

cpudatatest Test Parameter Options 
----------------------------------

	The Iterations, Test List, File Retention Mode, and File Size parameters may
be changed from the Test Options dialogue window for cpudatatest in the UI. See Command 
Line Syntax below.

cpudatatest Test Modes
---------------------- 

	Test Mode	# of Iterations
	------------    --------------
	Connectivity 		    50
	Online      		    10
	Offline     		   200
 

cpudatatest Command Line Syntax
-------------------------------

general syntax:	/opt/SUNWvts/bin/cpudatatest [standard arguments] -o dev=
			cpu-unit<n>[,count=<n>][test=<testlist>][,size=<n>]
			[,retain=<mode>]

	dev	Device Name: 'cpu-unit<n>'	n={0..63}
	count	Iterations			n={1..8192}
	test	Test List			testlist={CUC,g0,CUC+g0}
	retain	File Retention Mode		mode={Purge,Save,OnError}
	size	File Size (KB)			n={1..8192}

example:	/opt/SUNWvts/bin/cpudatatest -o dev=cpu-unit5

	runs/binds cpudatatest to processor 5. Note: it will
	exit with an error if processor 5 is not active or non-
	existent OR if the user is not superuser.

notes:  a) dev is a required option because it specifies the processor to which
	the test will be bound. The remaining options are optional.
        b) The user must be root(superuser) inorder to run this test.

cpudatatest Error Messages
--------------------------

Error Message			Probable Cause		Recommended Action
-----------------------------  ----------------------   ------------------
6001	Data Test failed	Faulty CPU Module	Contact your Sun 
	iteration value;				service provider.
	          ----- 
	Processor  cpu-unitN 
			   - 
	is suspected cause.
 
8000	Illegal options passed 	An incorrect value	Enter correct value.
	to cpudatatest 		             -----
	option=value.		was entered for 
	------ -----	 	parameter option.
				          ------

8002	unable to bind to 	value cpu may be offline 
	cpu=value: string	-----
	    -----  ------	or non-existent. string
					         ------
				may offer addtional
				explanation.

8004	system call string 	
	           -------
	failed with : string
		      ------

8005	exec'd program string	
		       ------
	failed with code value
			 -----

8007	bin_probe: argument 	An internal program	
	error			error.

8008	bin_probe() string	Required command not 	Make sure that compress,
		    ------	in /usr/bin or access	uncompress, cmp, and rm
	unavailable because: 	permission issue.	are in /usr/bin. Also,
	string						Check permissions.
	------

8010	Unable to create file	/tmp is full or access	Check that /tmp is
	string			permission issue.	not full and that
	------						it is writeable.

8011	Unable to allocate 	A memory resource issue.
	value byte buffer for 
	-----
	string
	------

8012	Unable to write value	A disk resource or	See 8010 above.
			-----	access issue.
	bytes to string
		 ------

8013	NOT Superuser; MUST be 				Become superuser.
	superuser to run this 
	program"


Note: If error message 6001 occurs then cpudatatest has detected a
      faulty module with the kind of failure which cpudatatest was
      designed to detect. All of the 80xx failures are fatal to 
      cpudatatest operation, but are not necessarily indicative of
      of a faulty module.


