IBM eserver xSeries 350 User Reference Manual page 114

Code Function
201 System memory Failed
202 System cache
206 Diskette drive
102
IBM® xSeries 350: User's Reference
Result
DIMM location n
(where n is the number of the socket that
contains the failing DIMM)
Test setup error: Corrupt BIOS in ROM
Test setup error: Corrupt DMI BIOS, information
in BIOS is not as expected
Stopped Test setup error: BIOS cannot access VPD
information
Test setup error: Corrupt DMI BIOS. Information
in BIOS is not as expected
Test setup error: No L2 cache detected on
microprocessor socket id xyz or BIOS setup
problem
(where xyz identifies the microprocessor that is
causing the error message)
Test setup error: Unknown hardware problem
associated with microprocessor in socket id xyz.
(where xyz identifies the microprocessor that is
causing the error message)
Failed Microprocessor in socket ID xyz
(where xyz identifies the microprocessor that is
causing the error message)
Note: The indicated microprocessor LED will
be on.
Warning Test setup error: Cache is disabled. Use system
setup to enable before retrying the test
Failed Internal diskette drive bay
Text message Action
1. Reseat the failing
DIMM.
2. If the problem
persists, replace the
DIMM.
If the problem
persists, call for
service.
If your server does not
have the latest level BIOS
installed, update the BIOS
to the latest level.
If the problem persists,
call for service.
If your server does not
have the latest level BIOS
installed, update the BIOS
to the latest level and run
the diagnostic program
again.
If the problem persists,
call for service.
1. If your server does
not have the latest
level BIOS installed,
update the BIOS to
the latest level
2. Run the diagnostic
program again.
3. If the problem
remains, replace the
failing processor.
If the problem persists,
call for service.
1. Reseat the identified
microprocessor.
2. If the problem
persists, replace the
microprocessor.
If the problem persists,
call for service.
Use the Cache Control
choice from the
Advanced Setup menu to
enable the cache.
If the problem persists,
call for service.
Call for service.