SunVTS 2.1.3 Test Reference Manual
  Sök endast i den här boken
Ladda ner denna bok i PDF
CHAPTER 21

M64 Video Board Test (m64test)


m64test tests the PCI-based M64 video board by performing the following subtests:
  • Video Memory test
  • RAMDAC test
  • Accelerator Port test

CAUTION Caution - DO NOT run any other application or screen saver program that uses the Pineapple accelerator port while running m64test. Do not run power management software. These programs cause SunVTS to return incorrect errors.


Note - Disable all screen savers before testing any graphics device. Type xset s off at a UNIX prompt to disable the Solaris screen saver. Disable power management software if it is running.


Note - DO NOT run Open Windows across multiple monitors.


Note - To start SunVTS with vtsui, but without vtsk, you must add the host name to xhost as:
xhost + hostname.



m64test Options

By default, all options are enabled except frame buffer locking.

Grafik

FIGURE 21-1 m64test


TABLE 21-1 m64test
m64test OptionsDescription
Video Memory TestThoroughly tests the on-screen video memory (the memory part that is mapped on to the monitor) of the M64 video board in 8-bit, 16-bit, 32-bit, 64-bit, and 64 byte (block) modes. Entire on screen video memory is tested by testing 512 bit blocks at a time (8x8 pixel block). Each block is tested in two passes. Each pass consists of a data write and read. In the first pass user specified data or random data is used and in the second pass one's complement of the data used in the first pass is used so that each on-screen video memory location (bit) is tested with a zero (electrical low state) and one (electrical high state).
TABLE 21-1 m64test
m64test OptionsDescription
RAMDAC TestTests the RAMDAC in three phases. In the first phase the RAMDAC CLUT (Color LookUp Table) is tested using simple write/read patterns to determine if there are any bad bits in CLUT.

The data patterns used are:

· Random data

· Complement of the random data (used as first data pattern) · The data pattern 0101

· The data pattern 10101

In the second phase four different patterns are drawn on the screen. Each pattern stays on the screen for approximately three seconds. The four patterns that are drawn are listed below. For each pattern signature is captured and compared with the signature obtained for the same pattern on a known good board. This test verifies that all the different data paths within the RAMDAC are functioning properly. Patterns drawn on screen:

· Red ramp with cursor at top-left corner of the screen · Blue ramp with cursor at top-right corner of the screen · Green ramp with cursor at bottom-left of the screen · Grey ramp with cursor at bottom-right of the screen In the last (third) phase of the RAMDAC test the Vertical Retrace Interrupt is tested for 300 interrupts.

Accelerator Port TestTests all the data paths (sources: fixed color, host data, blit, fixed pattern), arithmetic and logic unit (ALU), color comparator, primitives (destinations: line, rectangle), and mono to color expansion logic. Primitives are drawn using a combination of different data paths (allowed), ALU functions, and color comparator functions. A checksum is generated for each data combination and is compared with the checksum generated for the same data combination on a known good board.
Frame Buffer LockingThis option is set to disable if the M64 is not the console device. When Sunvts GUI is brought up FB Locking is enabled by default if M64 is console device. If M64 is not console device, FB Locking is disabled by default.

m64test Test Modes

Due to the nature of graphic tests, reading from or writing to the frame buffer during graphic tests will disturb user operation. This test is only available in the Functional Test mode.
TABLE 21-2 m64test
Test ModeDescription
Functional TestThe m64test verifies the M64 video board.

m64test Command Line Syntax

/opt/SUNWvts/bin/m64test standard_arguments -o dev=device_name, S=subtest_number,F=#_of_subtest_loops,B=#_of_test_loops,L=disable,P=test_pattern
TABLE 21-3 m64test
ArgumentExplanation
dev=device_namedevice_name is the relative path name of the device being tested
with respect to /dev/fbs; The default is m640.
S=subtest_numbersubtest_number is the test number of the subtest to be run. Select from the subtests below. You can run multiple subtests by adding the subtest numbers. For example, n=0x00003 runs both test 00001 and test 00002; n=0x00005 runs both test 0x00001 and test 0x00004. Note that you do not need the leading zeros. n - 0x00001 VRAM

n - 0x00002 RAMDAC

n - 0x00004 Accelerator port test (Rendering Pipeline)

More than one test can be selected by ORing subtest numbers. For example: n = 0x00005 means VRAM and Rendering Pipeline tests. A hex number must be preceded by 0x, decimal numbers are also acceptable.

F=#_of_subtest_loopsSpecifies the number of times to repeat each subtest; the default is 1.
TABLE 21-3 m64test
ArgumentExplanation (Continued)
B=#_of_test_loopsSpecifies the number of times to repeat a test loop before passing; default is 1.
L=disableDisables the frame buffer lock.Disable the lock when the m64 is not the console or when the server is not running on the m64 under test.
P=test_patternSpecifies the test pattern number. The default is r, for random
patterns. You may also choose 0 for 0x0000000, 3 for
0x3333333, 5 for 0x5555555, or 9 for 0x9999999.

m64test Error Messages

Errors returned by m64test are nonspecific. It is not possible to determine which component caused a failure. In all error conditions, the field replaceable unit (FRU) is the entire M64 video board. The errors messages are listed below, along with probable causes and recommended actions.
TABLE 21-4 m64test
Error MessageProbable Cause(s)Recommended Action
6000 Out of memorySystem error.If problem persists, call your authorized Sun service provider.
6002 string error: Misaligned raster.Software error.If problem persists, call your authorized Sun service provider.
6003 Unable to open string.Device not present.Check for device presence.

Device failure.Replace device.

Permission restrictions.Check device permissions.
6004  ioctl(2) Error in loading

IOCTL call to driver failure...Try replacing device.
the Frame Buffer
Device failure.
Call your authorized Sun service provider.
IOCTL call to driver failure. Try replacing device.
6005  ioctl(2) Error in loading
      the Original Color Map

Values.
Device failure.
Call your authorized Sun service provider.
TABLE 21-4 m64test(Continued)
Error MessageProbable Cause(s)Recommended Action
6006  ioctl(2) Error in Setting

IOCTL call to driver failure. Try replacing device.
the Cursor Values.
Device failure.
Call your authorized Sun service provider.
IOCTL call to driver failure. Try replacing device.
6007  ioctl(2) Error in loading
      the GXInfo Structure

fbtype.
Device failure.
Call your authorized Sun service provider.
6008 string (1-byte access) error: x/y (data) Expected 0x%02x, Actual 0x%0 2x, Xor 0x%02x.Device failure.Replace device.

Call your authorized Sun service provider.

6009 string (2-byte access) error:

x/y (data,data) Expected 0x%04x, Actual 0x%0 4x, Xor 0x%04x.

Device failure.Replace device.

Call your authorized Sun service provider

6010 string (4-byte access) error: x/y (data,data) Expected 0x%08x, Actual 0x%0 8x, Xor 0x%08x.Device failureReplace device.

Call your authorized Sun service provider.

6011 string (8-byte access) error: x/y (data,data) Expected 0x%08x, Actual 0x%0 8x, Xor 0x%08x.Device failureReplace device.

Call your authorized Sun service provider.

6012 string (64-byte access) error: x/y (data,data) Expected 0x%08x, Actual 0x% 08x, Xor 0x%08x.Device failure.Replace device.

Call your authorized Sun service provider.

6013 Error in Allocating Memory mmap call Failure.System error.If problem persists, call your authorized Sun service provider.
6014 Error in DeAllocating Memory unmap call Failure.System error.If problem persists, call your authorized Sun service provider.
TABLE 21-4 m64test(Continued)
Error MessageProbable Cause(s)Recommended Action
6015  ioctl(2) failed trying to

IOCTL call to driver failure. Replace device.
turn on M64 video.
Device failure.
Call your authorized Sun service provider.
6016 ioctl(2) failed trying to post CLUT.IOCTL call to driver failure.Replace device.

Call your authorized Sun service provider.


Device failure.
6017  ioctl(2)   failed trying

IOCTL call to driver failure. Replace device.
to read CLUT.
Device failure.
Call your authorized Sun service provider.
RAMDAC failure.Replace device.
6018Call your authorized Sun service provider.0x%02x.Miscompare found in Red
RAMDAC failureReplace device.
6019Call your authorized Sun service provider.0x%02x.Miscompare found in Green
RAMDAC failure.Replace device.
6020  Miscompare found in Blue
      channel of CLUT entry
      data. Expected 0x%02x, O
      served 0x%02x, XOR

Device failure
Call your authorized Sun service provider.
0x%02x.

6021 RAMDAC test screen CRC signature error message. Monitor type data, Cursor Position data, Expected Signature 0xvalue, Actual Signature 0xvalueDevice failure.Call your authorized Sun service provider.
6022 sysinfo(2) failed getting hostname.No system permissions.Become superuser.

If problem persists, call your authorized Sun service provider.

6023 Can't acquire console semaphoreSystem error.If problem persists, call your authorized Sun service provider.
TABLE 21-4 m64test(Continued)
Error MessageProbable Cause(s)Recommended Action
6024 Cannot gain control of mouse:stringSystem error.If problem persists, call your authorized Sun service provider.
6025 Cannot gain control of keyboard:stringSystem error.If problem persists, call your authorized Sun service provider.
6026 Already grabbed by another client
Try stopping other similar actions.

If problem persists, call your authorized Sun service provider.

6027 grabbed at invalid timeSystem error.If problem persists, call your authorized Sun service provider.
6028 grab window is not viewable
If problem persists, call your authorized Sun service provider.
6029 pointer/keyboard is frozen
If problem persists, call your authorized Sun service provider.
6030 Unknown cause
If problem persists, all your authorized Sun service provider.
6031  ioctl(2) failed trying to

IOCTL call to driver failure Replace device.
get current video mode.
Device failure.
Call your authorized Sun service provider.
6032  ioctl(2) failed trying to

IOCTL call to driver failure. Replace device.
set current video mode.
Device failure.
Call your authorized Sun service provider.
6033  ioctl(2) failed trying to

IOCTL call to driver failure. Replace device.
get M64 system info.
Device failure.
Call your authorized Sun service provider.
6034 mmap(2) failed:string.System error.If problem persists, all your authorized Sun service provider.
6035 munmap(2) failed:string.System errorIf problem persists, all your authorized Sun service provider.
TABLE 21-4 m64test(Continued)
Error MessageProbable Cause(s)Recommended Action
6036 close(2) failed:string.System error.If problem persists, all your authorized Sun service provider.
6045  Can't access X Windows

Permission denial from Host. Run xhost(1).
System error.
If X server is not running, run
X Server is not running.
X server.
If problem persists, all your authorized Sun service provider.
6046 wait(2) failed:stringSystem error.If problem persists, all your authorized Sun service provider.
6047 signal(2) failed:stringSystem error.If problem persists, all your authorized Sun service provider.
6048  ioctl(2) Error in

IOCTL call to driver failure. Replace device.
vertical retrace test.
Device failure.
Call your authorized Sun service provider.
6049  Can't open display

Permission denial from Host. Run xhost(1).
System error.
If X server is not running, run
X Server is not running.
X server.
If problem persists, call your authorized Sun service provider.
6050 m64 open file failed Could not open the signature file string: stringNo file permission or file does not exist.Check the file permissions.

If problem persists, call your authorized Sun service provider.

6051 m64 FTRUNCATE failed in checker.

Accelerator could not extend or truncate the signature file.

Insufficient disk space.Create more space by deleting unnecessary files.

If problem persists, call your authorized Sun service provider.

TABLE 21-4 m64test(Continued)
Error MessageProbable Cause(s)Recommended Action
6052 m64 close failed in checker.

Accelerator could not close signature file.

System error.If problem persists, call your authorized Sun service provider.
6053 m64 check error in checkerDevice failure.Replace device.

If problem persists, call your authorized Sun service provider.

6054 m64 ROP test failedDevice failure.Replace device.

If problem persists, call your authorized Sun service provider.

6055 m64 IOCTL fails FBIOPUTCMAP Error while putting color map.Device failure.Check software installation.

Replace device.

If problem persists, call your authorized Sun service provider.

6056 m64 IOCTL fail FBIOGETCMAP. Error while getting colorDevice failure.Check software installation.

Replace device.

map.

IOCTL call to deriver failure

If problem persists, call your authorized Sun service provider.
6057 Internal error Mon XLATOR Internal error occurred while translating monitor type to index into signature fileMonitor types are modified.If problem persists, call your authorized Sun service provider.