Browse Prior Art Database

ANALYSIS OF MULTIPLE FAILURE CODES TO DETERMINE A FIELD REPLACEABLE UNIT

IP.com Disclosure Number: IPCOM000026275D
Original Publication Date: 1991-Feb-28
Included in the Prior Art Database: 2004-Apr-05
Document File: 2 page(s) / 79K

Publishing Venue

Xerox Disclosure Journal

Abstract

After diagnostic software is run in a system containing multiple processors, a number of seemingly unrelated failure codes can be generated for a single fault. Therefor it would be advantageous to be able to match the list of generated fault codes against failure scenarios contained in a table. Each failure scenario has associated with it a code which identifies the Field Replaceable Unit which has failed. As knowledge of possible system failures increases, the failure scenario table is expanded to encompass the new combination of failure codes.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 74% of the total text.

Page 1 of 2

XEROX DISCLOSURE JOURNAL

Any Entries in HST?

Any More FSs In List?

 Log A System ID For Each Entry In The HST

ANALYSIS OF MULTIPLE FAILURE CODES TO DETERMINE A FIELD REPLACEABLE UNIT
Mark
A. Smith

Proposed Classification
U.S. C1.3551206 Int. Cl. G03g 21/00

Table

Any lnline Faults?

Get First Fai I ure Scenario

Does HST Contain the FS?

 Log The System ID That Corresponds To The Failure

[This page contains 1 picture or other non-text object]

Page 2 of 2

ANALYSIS OF MULTIPLE FAILURE CODES TO DETERMINE A FIELD RE PLACE AB LE UNIT( Cont'd)

After diagnostic software is run in a system containing multiple processors, a number of seemingly unrelated failure codes can be generated for a single fault. Therefor it would be advantageous to be able to match the list of generated fault codes against failure scenarios contained in a table. Each failure scenario has associated with it a code which identifies the Field Replaceable Unit which has failed. As knowledge of possible system failures increases, the failure scenario table is expanded to encompass the new combination of failure codes.

Referring now to the flow chart, the Hardware Status Table (HST) is cleared before each Diagnostic Module (DM) is run. Next, the boot time diagnostic is run. If any online faults are generated while the DM is running, the HST is not invoked and only the System Identification (ID) for the inline faults are passed. If the updates to the Status Table match a known failure scenario, then the system...