Sun and OracleChannel SunHow to BuyLog InРусский

SunDiag User's Guide: Addendum for SMCC Hardware
  Искать только в названиях книг
Помощь для поиска
Содержащиеся в
Найти другие документы
Ресурсы поддержки
 Загрузить это руководство в формате PDF

Overview

1

1.1 About This Book

This manual accompanies the SunDiag User's Guide and contains information about individual SunDiag tests that are specific to SMCC hardware. For more basic information about the SunDiag(TM) system exerciser, refer to the SunDiag User's Guide.

1.2 What's New in Version 4.4

If you're familiar with earlier versions of SunDiag system exerciser, here's a quick summary of the tests that have been added with this release:
tcxtest (S24 Frame Buffer Test)page 2-80
pcmiatest (PCMCIA Modem Card Test)page 3-57
irtest (Infrared Interface Test)page 3-59
plntest (SPARCstorage Array Controller Test)page 3-61
These teste were added with the SunDiag 4.3 release:
cg14test (Color Graphics Frame Buffer Test)page 2-46
sxtest (Pixel Processor Test)page 2-63
spdtest (SPARCprinter Test)page 3-45
rtvctest (SunVideo Test)page 3-48
These tests were added with the SunDiag 4.2 release:
leotest (SBus Printer Test)page 3-30
pstest (Prestoserve NFS Accelerator Test)page 3-18
spiftest (Serial Parallel Interface Test)page 3-20

1.3 Solaris Issues

Here is a list of Solaris operating environment issues that relate to the operation of the SunDiag system exerciser.
New Device Drivers When adding a new device driver in the Solaris operating environment, you must reboot the machine with the following command before SunDiag kernel will recognize the new driver:

  ok boot -r
When you use the boot -r command, the system will probe all attached hardware devices and assign nodes in the filesystem to represent only those devices actually found. It will also configure the logical namespace in /dev as well as the physical namespace in /devices. If you have removed a device from the system, then you also need to reboot the system with boot -r command before the SunDiag kernel sees the correct devices.
See the kernel(1M) man page for more information.
Dual Frame Buffers The frame buffer (FB) locking feature needs to be enabled if, and only if, the frame buffer to be tested is running OpenWindows(TM) software.
Running OpenWindows software on more than one frame buffer is not supported by the SunDiag system exerciser.
The -w Option The -w option to the sundiag command tells SunDiag to write the system hardware configuration to the /var/adm/sundiaglog/sundiag.conf file.

1.4 Displaying the POST Log File on Sun-4m Systems

On Sun-4m systems (for example, the SPARCserver(TM) 1000 and the SPARCcenter(TM) 2000 series systems), you can display the most recent power-on self test (POST) report from the SunDiag Log Files Menu.
When running the SunDiag software on a Sun-4m system, the Log Files Menu will add a POST Msgs option. By selecting this option and clicking on the Display button, you will display the most recent POST system report created from information on the system's OpenBoot(TM) PROM.

Графика

Figure 1-1

Графика

Figure 1-2

The System report messages will be saved in the /var/adm/sundiaglog/sundiag.prp log file. From the Log Files Menu, you can print or remove (remove all but the most recent report) this log file.
Follow the instructions below to print this system report from the command line:
  1. As root, change directories to the SunDiag bin directory. This directory is /opt/SUNWdiag/bin by default.

  2. Type the prp command to print the POST status report. 


  # ./prp  
  System report:  
  System board 0:  
       Dynabus 0 Group 1:  missing SIMM  
       Dynabus 0 Group 3:  missing SIMM  
  System board 1:  
       passed  
  System board 2:  
       not present  
  System board 3:  
       not present

1.5 Overrun/Underrun Diskette Test Errors

Diskette overrun/underrun error messages will appear in your test system's console window if you test the diskette drive while the system is very heavily loaded.
The SunDiag software is designed to stress test a system, so testing the diskette drive while running many other SunDiag tests may cause overrun/underrun errors. These overrun/underrun errors will cause the diskette tests to fail.
If an error occurs, you may see a messages similar to the ones below in the SunDiag Console window:

  09/22/94 11:53:34 diskette rawtest.2 ERROR: Big read failed on disk, in-between blocks 1386  
  and 1512: I/O error.  
  09/22/94 11:53:40 lostagain SunDiag INFO: *Failed test* (diskette)rawtest.2 passes: 0  
  errors: 1
Also, one of the following messages may be printed in the console after an overrun/underrun error:

  fd0: write failed (sr1 sr2 sr3)  
  fd0: overrun/underrun
or:

  fd0: read failed (sr1 sr2 sr3)  
  fd0: overrun/underrun
sr1, sr2, and sr3 represent the values of the floppy disk controller's status registers. Please refer to the fd(7) manpage for more details about these messages.
Note - These overrun/underrun errors are caused by a hardware limitation and cannot be fixed in the software.

1.6 Running cdtest with an Operating System CD-ROM

The SunDiag User's Guide mistakenly states that you cannot use an operating system CD-ROM when testing your CD-ROM drive with cdtest. You can use cdtest with the Solaris operating environment CD-ROM.
To run the cdtest with an Operating System CD-ROM:
  1. Insert the Solaris CD-ROM into the drive under test.

  2. Start the SunDiag software.

  3. Display the cdtest Option Menu.

  4. Select SunOS from the CD Type menu.

    See Figure 1-3.

Графика

Figure 1-3 cdtest

  1. Click the Apply button on the option menu.