CHAPTER 2

Advanced Frame Buffer Test(afbtest)

---

afbtest can detect and adapt to the video modes of the advanced frame buffer (AFB). Instead of running in one standard graphics mode, all tests can run in any mode. In stereo mode, all tests write into the right and left eyes unless you specify otherwise.

You can interrupt afbtest using Control-C. Turn off all other keyboard input if OPEN LOOK is running on the unit being tested.

Test accuracy is checked using a checksum algorithm. The location of the failing pixels are colored chartreuse to help you visually identify their position.

---

Caution - While running afbtest do not run any other application or screen saver program that uses the AFB accelerator port. This combination causes SunVTS to return incorrect errors.

---

---

Note - Disable all screen savers before testing any graphics device. Type xset s off at a UNIX prompt.

To start SunVTS with vtsui, but without vtsk, you must add the host name to xhost as:

xhost + <hostname>.

---

---

Note - afbtest requires approximately 2-Mbytes of disk space in the /tmp directory to extract its working files. If this space is not available, the diagnostic will fail and report warning and error messages that indicate a lack of disk space.

---

---

afbtest Options

By default, all tests are enabled.

FIGURE 2-1 afbtest

TABLE 2-1afbtest

afbest Options	Description
Texture Processor	Exercises the options (Texture Minification, Texture Magnification, Blend, Decal, and Modulation) selected by the AFB's Texture Pixel Processor Control (TPPC) register. Errors in this subtest are attributed to the FBC.
Decompression	Decompression exercises the decompression unit. This test uncompresses the compressed image data and renders the image to the frame buffer. Checksum is generated for the rendered image and compared with the checksum generated for the same uncompressed image on a known good system. Errors in this test are attributed to the Command chip.
AFB Dots	This test uses the AFB primitive tests developed for the AFB stand alone diagnostics. AFB dots are tested thoroughly with a variety of configurations, such as, dots anti-aliased dots, and big dots. Errors in this test are attributed to the Command chip and FBC.
AFB Triangles	This test uses the AFB primitive tests developed for the AFB stand alone diagnostics. AFB Triangles are tested thoroughly with these configurations: triangles drawn clockwise and counter clockwise, triangles drawn as stripes, independent triangles, triangles drawn as stars, and triangles with facet normals. Errors in this test are attributed to the Command chip and FBC.
Lighting	Lighting test exercises AFB float and lighting microcode. This test lights an object with the maximum number of lights that the AFB can handle in hardware (32). Checksum is generated for the rendered image and compared with the checksum generated for the same image on a known good system. Errors in this test are attributed to the Float and Microcode SRAMS.
Microcode	Microcode test generates the checksum for the microcode and compares it with the checksum generated for the microcode on known good board. Errors in this test are attributed to the Microcode PROMS and SRAMS.

---

afbtest 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 Functional Test and Stress modes.

TABLE 2-2 afbtest

Test Mode	Description
Functional Test	The afbtest verifies the advanced frame buffer boards
Stress mode	The Stress mode exercises the device being tested as much as possible. The Random Test generator, constructed as part of the verification effort, is used. Starting from a known seed, random primitives with random attributes are generated. Then the primitives are checked to ensure that they were rendered the same as on a known good system. The test is repeated ten times, with each random picture overlaying the previous one

---

afbtest Command Line Syntax

/opt/SUNWvts/bin/afbtest standard_arguments -o dev=device_name, S=subtest_number,F=#_of_subtest_loops,B=#_of_test_loops,P=test_pattern

TABLE 2-3 afbtest

Argument	Explanation
dev=device_name	device_name is the full path name of the device being tested; the default is /dev/fbs/afb0.

TABLE 2-3 afbtest

Argument	Explanation (Continued)
S=subtest_number	subtest_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=0x3 runs both test 1 and test 2; n=0x180 runs both test 0x080 and test 0x0100. Note that you do not need the leading zeros. n - 0x00001 3DRAM n - 0x00002 3DRAM Logic n - 0x00004 RAMDAC n - 0x00008 Rendering Pipeline n - 0x00010 FastFill/Vertical Scroll n - 0x00020 Pixel Processor n - 0x00040 Picking n - 0x00080 Arbitration n - 0x00100 Stereo n - 0x00200 Texture Processor n - 0x00400 Decompression n - 0x00800 AFB Dots n - 0x01000 AFB Lines n - 0x02000 AFB Triangles n - 0x04000 Lighting n - 0x08000 Audio n - 0x10000 Micro code More than one test can be selected by ORing subtest numbers. For example: n = 0x00009 means 3DRAM and Rendering Pipeline tests. A hex number must be preceded by 0x,decimal numbers are also acceptable
F=#_of_subtest_loops	Specifies the number of times to repeat each subtest; default is 1.
B=#_of_test_loops	Specifies the number of times to repeat a test loop before passing; default is 1.
P=test_pattern	Specifies 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.

---

afbtest Error Messages

Errors returned by afbtest 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 AFB.

TABLE 2-4 afbtest

	Error Message	Probable Cause(s)	Recommended Action
1	Data compare error		Error messages 1-7 all occur
2	Cannot gain control of mouse: <reason>		during the screen locking procedure where afbtest is interacting with the X window
3	Cannot gain control of keyboard: <reason>		system. The test only supports AFB devices on display 0 -
4	DGA error grabbing window on screen <value>		most machines only have display with multiple screens, but it is possible to have
5	DGA error getting window from token on screen <value>		multiple displays. Make sure you are using OPEN LOOK
6	No AFB device found on display 0		windows from SunSoft - other window systems are not
			supported and may not work.
7	There is an inconsistency with the version of the X Window System
8	Can't access XWindows - may need to run xhost(1).	The afbtest process must have write access to the X Windows display on the AFB. To grant access, run 'xhost +'
9	<test name> error: 3DRAM Memory error <plane group> Plane at (<x>,<y>) Expected = <value>, actual = <value>, xor = <value>.	The value written to the frame buffer was not the same as the value read back. This usually indicates a faulty 3DRAM chip. The u-number (AFB board position) of the failing chip is indicated in the error message. This message may be reported by the 3DRAM test or the arbitration test.

TABLE 2-4 afbtest(Continued)

	Error Message	Probable Cause(s)	Recommended Action
10	<test name>: Down-revved 3DRAM single bit failure detected <plane group> Plane at (<x>,<y>) Expected = <value>, actual = <value>, xor = <value>.	Early production 3DRAM chips exhibited single-bit read back errors on this test. This warning message indicates that your FFB has one of these chips, and the error was detected. The u-number (FFB board position) of the failing chip is indicated in the error message. This message may be reported by the 3DRAM test or the arbitration test.
11	<test name> error. Miscompares, starting at %s, are colored chartreuse.	The image generated by the test does not match the image generated on a known good FFB. The pixels which are colored chartreuse are where the images don't agree. Because of the checksum algorithm used for image comparison, some of the colored pixels may actually have been correct, but incorrect pixels obscured the comparison.
12	Installed FFB has downrev RAMDAC - skipping RAMDAC test	Early versions of the FFB RAMDAC chip had faulty signature analysis and therefore could not be used for the RAMDAC test. These chips are not necessarily bad, but they cannot be tested with ffbtest.
13	Unsupported screen resolution -skipping RAMDAC test	Almost all screen resolutions are supported by the RAMDAC test, but a few are not.
14	Miscompare found in <Red Green Blue> channel of CLUT entry <value>. Expected = <value>, Observed = <value>, XOR = <value>

TABLE 2-4 afbtest(Continued)

	Error Message	Probable Cause(s)	Recommended Action
15	Miscompare found in WID LUT entry <value>. Expected = <value>, Observed = <value>, XOR = <value>	The RAMDAC test writes values to each entry of the lookup tables and then reads back the values. These error messages indicate that the readback value was different from the written value. This could indicate a faulty RAMDAC.
16	RAMDAC test failed. The on-screen image is incorrect	The RAMDAC test puts up squares of data using all of its different output modes. It then gets a "signature" from the RAMDAC, which is a checksum of the pixels actually being written to the screen. This message indicates that the checksum is different from the checksum generated on a known good AFB. This could indicate a faulty RAMDAC.
17	Picking test error. Got a pick hit with picking disabled	Error messages 17-19 indicate a failure in the picking test. On the AFB, picking is done by the
18	Picking test error. Got a pick hit outside the picking area	3DRAM chips, so the u-number (AFB board position) of the failing chip is indicated in the error message.
19	Picking test error. Should have detected a pick hit

TABLE 2-4 afbtest(Continued)

	Error Message	Probable Cause(s)	Recommended Action
20	Stereo image incorrect	The Stereo test uses the RAMDAC signature analysis feature to verify that the pixels going to the screen are correct. This message indicates a failure of the test, which probably indicates a faulty RAMDAC.	Error messages 20-22 indicate incorrectly installed or corrupted software installation. Try reinstalling SunVTS
21	Stereo not supported on current monitor type: <value>	Only certain kinds on monitors support Stereo output mode. Only the P4 monitors will work with the afbtest Stereo test. File not found Could not open file <file name>.	Reinstall software
22	Could not open file <filename>: <reason>. Keyword not Found, line <value>	Suspect data file corruption
23	Out of memory	A call to mailloc(3c) or new( ) failed	Increase swap space
24	/usr/bin/tar failed		Check for existence and/or permissions on <file name>. Also check for available space in /tmp
25	/usr/bin/uncompress failed		Error messages 25-35 indicate that there is a permissions problem. You must be root to run afbtest. These messages may also indicate some other kind of corruption. Try rebooting, and if that fails, reinstall.
26	fork1(2) failed: <reason>
27	execl(2) failed: <reason>
28	sysinfo(2) failed getting hostname. Must be superuser
29	mmap(2) failed: <reason>
30	munmap(2) failed: <reason>
31	close(2) failed: <reason>
32	wait(2) failed: <reason>

TABLE 2-4 afbtest(Continued)

	Error Message	Probable Cause(s)	Recommended Action
33	signal(2) failed: <reason>
34	thr_kill(2) failed
35	thr_join(2) failed: <reason>
36	ioctl(2) failed trying to read CLUT		Error messages 36-51 indicate either that the AFB was installed incorrectly or that you do not have permission to use it. Check that the AFB packages were installed correctly and that you have the latest version of the driver patches. Also make sure you are running afbtest as root.
37	ioctl(2) failed trying to turn on AFB video
38	ioctl(2) failed trying to post CLUT
39	ioctl(2) failed trying to read WID LUT
40	ioctl(2) failed trying to post WID LUT	A downrev FFB driver or a bad electron board
41	ioctl(2) failed trying to get RAMDAC signature analysis
42	ioctl(2) failed trying to get current video mode
43	ioctl(2) failed trying to set current video mode
44	ioctl(2) failed trying to get AFB system info
45	ioctl(2) failed trying to go into Diagnostic mode
46	ioctl(2) failed trying to read Transparent Overlay registers

TABLE 2-4 afbtest(Continued)

	Error Message	Probable Cause(s)	Recommended Action
47	ioctl(2) failed trying to post Transparent Overlay registers
48	ioctl(2) failed trying to post cursor
49	ioctl(2) failed trying to read cursor
50	stat(2) failed trying to get info about Device Under Test
51	stat(2) failed trying to get info about screen 0:<value>