| Problem Document
|
Synopsis
|
Last Modified Date
|
| 2295466.1 |
Fujitsu M10-1/M10-4/M10-4S Server Panic: Fatal error has occurred in: PCIe fabric.(0x1)(0x41) / SUNOS-8000-0G |
2017-08-14
|
| 2280973.1 |
Fujitsu M10 Server: Panic: System May Experience a "BAD TRAP: type=28" with "callout_list_expire" if Solaris Kernel Zones are Used |
2017-06-27
|
| 2276327.1 |
Nvmeadm Getlog -s Command For F320 Causes OS Panic. |
2017-06-13
|
| 2274620.1 |
Fujitsu M10-1 / M10-4 / M10-4S Server: Domains May Panic After 1101 Days of Uptime |
2017-09-06
|
| 2259169.1 |
Fujitsu M10-1 / M10-4 / M10-4S Disk ( SSD ): Solid State Disks Experiencing "Disconnected command timeout" |
2017-04-25
|
| 2245358.1 |
Solaris sun4v domains may panic after 1101 days of uptime |
2018-01-18
|
| 2238724.1 |
Domain time may drift after an abrupt system down |
2017-03-23
|
| 2211342.1 |
Fujitsu M10-1/M10-4/M10-4S Error: 'PCI access error' (12bb0000) message is reported on Fujitsu M10 systems |
2018-04-05
|
| 2209101.1 |
Fujitsu M10-4/M10-4S: Two DIMMs marked Faulted, replacing DIMMs does not fix the issue |
2017-10-05
|
| 2203942.1 |
Fujitsu M10-x: Uploading XSCF snapshot data file to MOS results in "Please remove all executable files from your upload bundle and resubmit" |
2017-10-05
|
| 2192454.1 |
M10 XCP2250 - XCP2271 does not treat a specific PSU failure as fault |
2018-04-05
|
| 2182960.1 |
Using the Ethernet Virtual Functionality causes "panic[cpu0]/thread=2a10009bb80: Fatal error has occurred in: PCIe fabric.(0x1)(0x43)" |
2018-03-01
|
| 2163890.1 |
M10-4: PPAR Cannot Power On / CMUL Faulted after ALARM critical high temperature |
2017-10-05
|
| 2146945.1 |
Fujitsu M10-1/M10-4/M10-4S: Graphic Card Problems |
2016-06-08
|
| 2142944.1 |
Fujitsu M10-4/M10-4S: XSCF does not Identify M10 PCI Expansion Unit |
2016-05-26
|
| 2140061.1 |
SAS Disk Becomes Inaccessible After a Reset |
2016-07-21
|
| 2136834.1 |
M10-x, Mx-32,T4-x, T5-x Servers: ldmd_start Fails with Error "timeout waiting for op HVctl_op_hello" |
2018-02-12
|
| 2135472.1 |
Fujitsu M10-1/M10-4/M10-4S Servers: XSCF Control Package (XCP) Firmware mismatch message appears |
2017-10-05
|
| 2102018.1 |
M10-1 Cannot Locate HDD with cfgadm -x locator=on c0::dsk/c0t5000039668222832d0 |
2017-10-11
|
| 2087880.1 |
M10-1/M10-4/M10-4S Error: XSCF Displays SDRAM Correctable Error During Boot |
2016-06-09
|
| 2071864.1 |
Fujitsu M10-4S: Error: 01e40001 - XSCF self diagnosis warning detection |
2015-10-29
|
| 2062123.1 |
Fujitsu M10-1/M10-4/M10-4S: Error: fwupdate Fails with Message "ERROR: Could not identify host type" |
2018-05-08
|
| 2056911.1 |
Fujitsu M10-1/M10-4/M10-4S: Error: Get Device ID command failed: Unknown (0x7E) is displayed when running fwupdate |
2018-04-05
|
| 2035857.1 |
Fujitsu M10-1, M10-4 and M10-4S High FAN Rotation Speeds Causes Noisy Systems |
2017-07-25
|
| 1992858.1 |
Fujitsu M10-1/M10-4/M10-4S Servers: When Updating to Oracle Solaris 11.2 from Oracle Solaris 11.1 MPXIO may change disk path names |
2015-03-30
|
| 1982137.1 |
Fujitsu M10-1/M10-4/4S Error: Time of Day clock error: reason [XXXX by YYYY]. -- Stopped tracking Time Of Day clock. |
2018-03-01
|
| 1944793.1 |
Fujitsu M10-1/M10-4/M10-4S XCP2230: Hypervisor Regression Causing Guest Domains not to Boot |
2014-11-20
|
| 1941641.1 |
Fujitsu M10-4S: XSCF "BB-ID is illegal" with 01a10010 |
2017-08-28
|
| 1924028.1 |
Fujitsu M10-4/M10-4S: PCI access errors (12bb0000) on both CMUL and CMUU |
2017-09-21
|
| 1922054.1 |
Solaris 11.1 M10-4S or T4-1 guest domain can panic in numaio_constraint_add_core_cpu |
2014-09-01
|
| 1920627.1 |
M10 XSCF Hangs With REBOOT: COUNTER ERROR (reason=0x00 Counter=4 Threshold=3) |
2017-03-27
|
| 1916946.1 |
Fujitsu M10-1/M10-4/M10-4S; Hot-replacement of FANs/PSUs on M10 PCI Expansion Unit Cannot be Performed |
2018-03-01
|
| 1904125.1 |
CMUL Faulted with Power Issues ( Error Messages 01910d00, 01919220, 018f0001 ) |
2017-09-19
|
| 1901433.1 |
Fujitsu M10-4/M10-4S Power Supply Interlocking Issue |
2014-06-26
|
| 1677542.1 |
Fujitsu M10-1/M10-4/M10-4S XSCF Panic/Hang: XSCF with XCP < 2090 may Reboot or Perform Poorly After Being Up For More Than 30 Days |
2018-03-01
|
| 1677413.1 |
Fujitsu M10-4S Error: Using PPAR Dynamic Reconfiguration ( DR ) on Multi Building Block Configuration May Cause Memory Corruption, OS Panic or PPAR Reset. |
2018-05-08
|
| 1664253.1 |
M10 IOX AC power failure cause guest domain PCIe device in "ldom ls-io" output show status in "UNK" |
2017-10-11
|
| 1624376.1 |
After Inadvertent Flash Card Removal, 2 PCI Slots And Flash Card No Longer Visible |
2017-09-19
|
| 1614738.1 |
[SPARC T4/T5/M5 and M6] FMA I/O retirement : PCI devices can be seen from OBP but disappear when System Boots up into Solaris |
2018-05-01
|
| 1599957.1 |
Fujitsu SPARC M12-1/M12-2/M12-2S, Fujitsu M10-1/M10-4/M10-4S COD CPU Activation Key fails |
2017-12-07
|
| 1591393.1 |
Fujitsu M10-1/M10-4/M10-4S/M12-1/M12-2/M12-2S Servers: CoD in general and issue 'poweron': Not powering on : Poweron canceled due to missing component. |
2018-05-09
|
| 1589131.1 |
Fujitsu M10-1/M10-4/M10-4S Server: FCode checksum error; expected: 7484 result: 74e2 |
2013-10-08
|
| 1587590.1 |
Fujitsu M10-1/M10-4/M10-4S Servers: CPU Panic On Server Build |
2018-03-01
|
| 1570216.1 |
Fujitsu M10-1/M10-4/M10-4S: System Backup Memory Access Error on Power Supply Backplane |
2018-05-17
|
| 1560945.1 |
missing XB80 and BB00 on a newly configured M10-4S |
2014-06-30
|
