FUJITSU SPARC ENTERPRISE T5120 - Manual (Page 32)

22 SPARC Enterprise T5120 and T5220 Servers Product Notes • October 2007
The following is an example of dumping the event:
These events are harmless and can be ignored.
USB Device Causes Panic on DMA to Address 0 (CR 6555956)
Very rarely a panic could occur during reboot with the following message:
The panic only occurs on reboot and has never been observed on the reboot that
follows the panic. (If an endless panic/reboot cycle does occur call a sales
representative or a certified service engineer for service.)
Workaround: Ensure that the system is set to automatically reboot after a panic. At
the ALOM CMT compatibility CLI enter the following command:
VBSC Did Not Detect Memory One Time: ERROR:
MB/CMP0/BR3/CH0/D0 must be populated
(CR 6604305)
Very rarely, the Virtual Blade Server Control (VBSC) probing of DIMMs could fail
due to ILOM simultaneously updating DIMM information. When the DIMM
probing fails, the host either boots with a reduced memory configuration, or fails to
boot. This situation is not likely to happen when the service processor (SP) is reset
because VBSC will have already probed them DIMMs before ILOM would start the
dynamic fruid updates, but it can happen when the host is being repeatedly
powered on/off without resetting the SP.
Workaround: Power off the host, reset the SP, and power on the host again.
# fmdump -eV -u dd9a4415-9be4-cb55-d061-8804b8009d3c
TIME CLASS
Aug 27 2007 10:06:15.496599680 ereport.fm.ferg.invalid
nvlist version: 0
class = ereport.fm.ferg.invalid
ena = 0xd4e233fe480002
info = DMU Core and Block Error Status(0): No bits set
raw-data = 0x2 0x1a62441a01d844 0x30000000000005 0x4b63c07df9ff
0x3e002421030607 0x
3e 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
__ttl = 0x0
__tod = 0x46d2da57 0x1d998280
"Fatal error has occurred in: PCIe root complex."
sc> bootmode bootscript="setenv auto-boot? true"