irsaudit(1)
irsaudit - InfiniteReality System Diagnostics
As shipped in IRIX 6.5.19. Unchanged since IRIX 6.5.
NAME irsaudit - InfiniteReality System Diagnostics SYNOPSIS irsaudit [ options ...] DESCRIPTION The irsaudit program is the diagnostic software for InfiniteReality manufacturing verification and burn-in, field service hardware diagnosis, and component fault isolation. Unlike previous graphics hardware diagnostics, irsaudit does not use the IDE harness and does not have a ``prompting'' interface. Instead, irsaudit is driven purely via command-line options. The output of irsaudit is in a standardized format to allow easy parsing of results. See the OUTPUT section. IRIX must be running in order to run irsaudit. The X server should not be running, as irsaudit takes direct control of the graphics hardware. If the X server is running, use /usr/gfx/stopgfx to disable the X server before running irsaudit. The user must have root privilege to run irsaudit. irsaudit cannot be run from the graphics console being tested. It should be run from either a remote shell or the diagnostic terminal. EXAMPLE To run all standard RM, DG, and GE tests: irsaudit To run only the RM tests on the second pipe (pipe #1) of multi-pipe system: irsaudit -rm PIPE=1 After running irsaudit (assuming no hardware failures that would preclude the window system from running), run /usr/gfx/startgfx as root to restart the window system. OPTIONS irsaudit options are selected with one of four syntaxes: ``minus'' options select tests to execute and access to other common options (examples: -ge_intbist, -forever); ``equal'' options assign values to a irsaudit parameter (example: PIPE=1); ``plus'' options which provide access to generally undocumented options; and ''minus minus'' options remove tests from the selected list of tests to execute. Generic options. -help Print help message explaining all options and sample usage. The test options are printed in the order they would be executed relative to each other. -continue Continue testing when a failure occurs. Normal behavior is to stop on first failure. The -cont and -c also work. -forever Loop over the specified tests until interrupted by ctrl-C or until a failure occurs (see -continue ). PIPE=# Selects which InfiniteReality graphics pipe in a multi- pipe system is to be tested. Default is pipe 0. -goldfile <file> Use named gold file for CRC expected data. Default file is irsaudit.gold. -writecrc <file> Write CRCs collected from the hardware to the named file instead of comparing them against gold data. -info Enable output of INFO messages (the default). -noinfo Suppress output of INFO messages. -notime Suppress output of TIME messages (the default). -time Enable output of TIME messages. -trace Enable output of TRCE messages. -notrace Suppress output of TRCE messages. -code Enable output of CODE messages (the default). -nocode Suppress output of CODE messages. -color Colorize RSLT messages (default). Red for FAIL, Green for PASS and Yellow for UNRESOLVED. -nocolor Don't colorize RSLT messages. DEBUG=# or -debug # Enable output of DBUG messages at less than or equal to # (where # is between 0 and 9 inclusive). -gemask # # is a bitwise enable mask to select which GE11s will be used during the tests. Default value of the mask is 0xff, which enables all GE11s. Mask bit zero refers to GE 0, and so on. -meta Show META lines when testing is completed. META lines display accumulated pass/fail statistics. META=# Interval of full test loops between META reporting. REPEAT=# Number of repetitions through all selected tests. TRACE=filename Trace file messages logged to named file. LOG=filename Standard output logged to named file. TDEBUG=# Enable trace file output of DBUG messages at less than or equal to # (where # is between 0 and 9 inclusive). This can be set higher (more debugging) than the DEBUG=# option to capture more debugging without obscuring the standard output stream. Board test suites. -all Run all tests in the appropriate order (the default if nothing else is specified). -ge Run all GE12 board tests. -rm Run all RM6 board tests. -dg Run all DG4 board tests. -pab Run all PAB2 board tests (the Sirius DG option board for InfiniteReality). -gvo Run all GVO board tests (the 601 video DG option board for InfiniteReality2). Individual tests. Multiple options can be specified. The union of tests for all specified options will be run. For a complete list of the current tests run: irsaudit -help OUTPUT The output format is line based. Lines are no more than 80 characters in length. Each line is tagged by one of the following four-character identifiers: TEST Test start markers, generated at the beginning of a test. Indicates the test's symbolic name and description. All following lines up to the next TEST line are associated with the named test. Columns 1- 4: "TEST" Columns 6-19: test symbolic name Columns 21-80: test description RSLT Test result, generated at the end of a test. Indicates the test's symbolic name and the test result. The result will be one of pass, fail, unresolved, or untested. Columns 1- 4: "RSLT" Columns 6-19: test symbolic name Columns 21-30: "PASS" | "FAIL" | "UNRESOLVED" | "UNTESTED" Columns 41-80: optional short explanation DIAG Diagnosis message. One or more of these lines will preceed any fail or unresolved message. The message should indicate what components or wires are possible causes of the failed test. Columns 1- 4: "DIAG" Columns 21-80: diagnosis message INFO Information which is useful to an advanced user of the diagnostic. This can include test progress reports, exp/rcv pairs, etc. INFO messages are enabled by the -info command line option. Columns 1- 4: "INFO" Columns 21-80: informational message DBUG Debugging information, only generated when debugging output is turned on (not the default); not intended for field or manufacturing use but may be useful to diagnostic programmers. DBUG messages are enabled by the -debug command line option. Columns 1- 4: "DBUG" Column 6: debugging level, one through nine Columns 21-80: debugging message TIME Time stamp, generated at important time boundaries such as the beginning and end of irsaudit. Columns 1- 4: "TIME" Columns 6-33: Unix style date META Summarizes information over several tests. A table is generated providing the pass and fail counts of each test (and totals over all tests) across multiple full test loops. Columns 1- 4: "META" Columns 21-80: summary statistics NSHP Indicates the hardware has down-rev parts, an unsupported configuration, or is otherwise not fit for shipping to customers. Columns 1- 4: "NSHP" Columns 21-80: explanation ABRT Reports an exceptional error condition leading to the abortion of the diagnostics. Probably caused by a malloc failure, unexpected system call failure, or assertion failure. Should not happen under normal circumstances. Columns 1- 4: "ABRT" Columns 21-80: abort explanation CODE Encodes board and ASIC failures for easy parsing. CODE messages are enabled with the -code command line option. There are several sub-options based on columns 21-24. Each of these is listed below. Columns 1- 4: "CODE" Columns 6-19: test symbolic name either Columns 21-24: "BF" - indicates board failure for a given test Column 25: "R" | "Y" | "G" - board status (Red, Yellow, or Green) Columns 27- : <Part Number>":"<Serial Number>"("<NIC Number>")@"<ASIC list> or Columns 21-24: "SUM" - overall execution summary Columns 25-80: "No error" | "Hardware error" or Columns 21-24: "BSUM" - error summary for a board Columns 26-28: Number of tests showing "R"ed status Column 29: "R" Columns 30-33: Number of tests showing "Y"ellow status Column 34: "Y" Columns 35-38: Number of tests showing "G"reen status Column 39: "G" Columns 41- : <Part Number>":"<Serial Number>"("<NIC Number>")" or Columns 21-24: "CSUM" - always follows "BSUM" and indicates chip failures on the given board. Columns 26-28: Number of tests showing "R"ed status Column 29: "R" Columns 30-33: Number of tests showing "Y"ellow status Column 34: "Y" Columns 35-38: Number of tests showing "G"reen status Column 39: "G" Columns 41- : Name of Chip FILES /usr/diags/IR/bin/irsaudit executable for InfiniteReality Diagnostics, /usr/diags/IR/ucode directory of InfiniteReality Diagnostic microcode. /usr/diags/IR/data directory of data files for InfiniteReality diagnostics. BUGS Rarely -geconn , -minigeconn and -bpconn can cause system panics or hangs due to undefined (uninitialized) hardware state that results in unexpected DMA activity.