Sun Enterprise [TM] E450 OBDiag errors after installing new system board (Doc ID 1001660.1)

Last updated on FEBRUARY 01, 2017

Applies to:

Sun Enterprise 450 Server - Version All Versions and later
All Platforms

Symptoms

 Description:

After installing a new system board and using the NVRAM chip that came with the new system board,

the nvram values used to test system boards will probably not be set to their default values.

Thus, OBDiag may output error messages (see below) but the system will otherwise boot and operate normally.

If diag-script normal = mfg-5

diag-targets = dev+loopback

(FYI, the above nvram setting are for testing ttya, ttyb, ppp, hme and floppy. These tests require loopback

plugs installed and scratch floppy loaded.)

===== OBDiag Error messages ===================================================

###OBDIAG_START###

ERROR : Timeout no character received, UART Port B, Baud Rate = 4800

DEVICE : /pci@1f,4000/ebus@1/se@14,400000

FRU : motherboard

TIME : 11/23/2002 06:20:02 GMT

CALLER : )warning (f00a4050) (f00a42c0) ...

 

ERROR : KeyBoard timeout receiving a character

DEVICE : /pci@1f,4000/ebus@1/su@14,3083f8

FRU : motherboard

TIME : 11/23/2002 06:20:04 GMT

CALLER : )warning port-key port-loopback ...

 

ERROR : Mouse timeout receiving a character

DEVICE : /pci@1f,4000/ebus@1/su@14,3062f8

FRU : motherboard

TIME : 11/23/2002 06:20:04 GMT

CALLER : )warning port-key port-loopback ...

 

ERROR : One of 8 Data Bits Stuck High

DEVICE : /pci@1f,4000/ebus@1/ecpp@14,3043bc

FRU : motherboard

TIME : 11/23/2002 06:20:04 GMT

CALLER : )warning sio-passive-lb $vexecute  ...

 

ERROR : No diskette, or incorrect format

DEVICE : /pci@1f,4000/ebus@1/fdthree@14,3023f0

FRU : motherboard

TIME : 11/23/2002 06:20:08 GMT

CALLER : )warning floppy-test catch ...

###OBDIAG_STOP###

% Device /pci@1f,4000/ebus@1/se@14,400000 being marked with 'status' == fail

% Device /pci@1f,4000/ebus@1/su@14,3083f8 being marked with 'status' == fail

% Device /pci@1f,4000/ebus@1/su@14,3062f8 being marked with 'status' == fail

% Device /pci@1f,4000/ebus@1/ecpp@14,3043bc being marked with 'status' == fail

% Device /pci@1f,4000/ebus@1/fdthree@14,3023f0 being marked with 'status' == fail

Changes


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms