![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Problem Resolution Sure Solution 1001660.1 : Sun Enterprise [TM] E450 OBDiag errors after installing new system board
PreviouslyPublishedAs 202257 Applies to:Sun Enterprise 450 Server - Version All Versions and laterAll Platforms SymptomsDescription: 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 ChangesCauseRead above. Solution{0} ok set-defaults -or - reset the following nvram parameters to their default values diag-level = min diag-script = normal diag-targets = none diag-trigger = power-reset
Attachments This solution has no attachment |
||||||||||||
|