SunVTS 2.1 Test Reference Manual
只搜寻这本书
以 PDF 格式下载本书
CHAPTER 19

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 - DO NOT run any other application or screen saver program that uses the Pineapple accelerator port while running m64test. This combination could 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.
To start SunVTS with vtsui, but without vtsk, you must add the host name to xhost as:
xhost + <hostname>.

m64test Options

By default, all tests are enabled.

图形

FIGURE 19-1 m64test


TABLE 19-1
m64test OptionsDescription
Video MemoryTests the on screen video memory (the memory part that is visible on the screen of the M64 video board in 8-bit, 16-bit, 32-bit, 64-bit, and 64 byte (block) modes. The test completes two passes consisting of a write and read to each byte of on-screen video memory. The first pass is made using random data or data specified by the user at the command line. The second pass is made with the one's complement of the data used in the first pass so that each on-screen video memory location (bit) is tested with a zero (electrical low state) and one (electrical high state).
TABLE 19-1
m64test OptionsDescription
RAMDACThe RAMDAC test completes three phases. The first phase tests the RAMDAC memory by writing to and reading from the RAMDAC memory (look up table LUT) with four data patterns. Data patterns written to and read from the RAMDAC memory are compared for consistency. The four data patterns include:

-Random data

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

-The data pattern 10101

The second phase draws four different patterns on the screen. Each pattern stays on the screen for approximately three seconds. The four patterns include:

-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 A signature is captured with each pattern and compared with the signature obtained for the corresponding pattern on a known good board. This test verifies that all the different data paths within the RAMDAC are functioning properly. The third phase tests the Vertical Retrace Interrupt. The Vertical Retrace Interrupt is tested for 300 interrupts.

Accelerator PortTests 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 signature is captured for each data combination and is compared with the signature captured for the same data combination on a known good board.

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 19-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,P=test_pattern
TABLE 19-3 m64test
ArgumentExplanation
dev=device_namedevice_name is the full path name of the device being tested; the default is /dev/fbs/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

TABLE 19-3 m64test
ArgumentExplanation (Continued)
F=#_of_subtest_loopsSpecifies the number of times to repeat each subtest; default is 1.
B=#_of_test_loopsSpecifies the number of times to repeat a test loop before passing; default is 1.
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 19-4 m64test

Error MessageProbable Cause(s)Recommended Action
6002%s error: Misaligned raster.\nSoftware errorIf problem persists, call your authorized Sun service provider
6003Unable to open%s.\nDevice not presentCheck for device presence


Device failureReplace device


Permission restrictionsCheck device permissions
6004 ioctl(2) Error in loading the Frame
IOCTL call to driver failure..Try replacing device
Buffer structure fbtype.\n
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.\n
Device failure
Call your authorized Sun service provider
6006 ioctl(2) Error in Setting the Cursor
IOCTL call to driver failure Try replacing device.
Values .\n
Device failure
Call your authorized Sun service provider
TABLE 19-4 m64test(Continued)
Error MessageProbable Cause(s)Recommended Action
6007 ioctl(2) Error in loading the
IOCTL call to driver failure Try replacing device.
GXInfo Structure fbtype .\n
Device failure
Call your authorized Sun service provider
6008 %s (1-byte access) error:\n x/y (%d,%d) Expected 0x%02x, Actual 0x%0 2x, Xor 0x%02x.\nDevice failureReplace device.

Call your authorized Sun service provider

6009 %s (2-byte access) error: \n x/y (%d,%d) Expected 0x%04x, Actual 0x%0 4x, Xor 0x%04x.\nDevice failureReplace device.

Call your authorized Sun service provider

6010 %s (4-byte access) error:\n x/y (%d,%d) Expected 0x%08x, Actual 0x%0 8x, Xor 0x%08x.\nDevice failureReplace device.

Call your authorized Sun service provider

6011 %s (8-byte access) error:\n x/y (%d,%d) Expected 0x%08x, Actual 0x%0 8x, Xor 0x%08x.\nDevice failureReplace device.

Call your authorized Sun service provider

6012 %s (64-byte access) error:\n x/y (%d,%d) Expected 0x%08x, Actual 0x% 08x, Xor 0x%08x.\nDevice failureReplace device.

Call your authorized Sun service provider

6013 Error in Allocating Memory < mmap call Failure >.\nSystem errorIf problem persists, call your authorized Sun service provider
6014 Error in DeAllocating Memory < unmap call Failure >.\nSystem errorIf problem persists, call your authorized Sun service provider
6015  ioctl(2) failed trying to

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

Call your authorized Sun service provider


Device failure
TABLE 19-4 m64test(Continued)
Error MessageProbable Cause(s)Recommended Action
6017  ioctl(2)   failed trying

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

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

6021 RAMDAC test screen CRC signature error message. Monitor type%d, Cursor Position %d, Expected Signature 0x%x, Actual Signature 0x%xDevice failureCall your authorized Sun service provider
6022 sysinfo(2) failed getting hostname.\nNo system permissionsBecome superuser

If problem persists, call your authorized Sun service provider.

6023 Can't acquire console semaphore\nSystem errorIf problem persists, call your authorized Sun service provider.
6024 Cannot gain control of mouse:%s\nSystem errorIf problem persists, call your authorized Sun service provider.
6025 Cannot gain control of keyboard:%s\nSystem errorIf problem persists, call your authorized Sun service provider.
TABLE 19-4 m64test(Continued)
Error MessageProbable Cause(s)Recommended Action
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 errorIf 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.\n
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.\n
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.\n
Device failure
Call your authorized Sun service provider
6034 mmap(2) failed:%s.\nSystem errorIf problem persists, all your authorized Sun service provider
6035 munmap(2) failed:%s.\nSystem errorIf problem persists, all your authorized Sun service provider
6036 close(2) failed:%s.\nSystem errorIf problem persists, all your authorized Sun service provider
TABLE 19-4 m64test(Continued)
Error MessageProbable Cause(s)Recommended Action
6037 DGA error grabbing window on screen%d.\nSystem errorIf problem persists, all your authorized Sun service provider
6038 DGA error getting window from token on screen%d.\nSystem errorIf problem persists, all your authorized Sun service provider
6039  ioctl(2) failed trying to

IOCTL call to driver failure Replace device.
post cursor.\n
Device failure
Call your authorized Sun service provider
6040  ioctl(2) failed trying to

IOCTL call to driver failure Replace device.
read cursor.\n
Device failure
Call your authorized Sun service provider
6041  No M64 device   found on

IOCTL call to driver failure Replace device.
display 0.\n
Device failure
Call your authorized Sun service provider
6042 There is an inconsistency with the version of the X Window System.\nSystem errorIf problem persists, all your authorized Sun service provider
6043 stat(2) failed trying to get info about Device Under Test.\nSystem errorIf problem persists, all your authorized Sun service provider
6044 stat(2) failed trying to get info about screen 0:%d.\nSystem errorIf problem persists, all your authorized Sun service provider
6045  Can't access XWindows

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:%s\nSystem errorIf problem persists, all your authorized Sun service provider
6047 signal(2) failed:%s\nSystem errorIf problem persists, all your authorized Sun service provider
TABLE 19-4 m64test(Continued)
Error MessageProbable Cause(s)Recommended Action
6048  ioctl(2) Error in

IOCTL call to driver failure Replace device.
vertical retrace test.\n
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, all your authorized Sun service provider