Specifications

Form factor1U rack-mount, single socket, assemble-to-order
Processor1× SPARC64 X or SPARC64 X+ (see below); 16-core, or 8-core on the 3.7 GHz X+ part; 2 threads per core
Instruction setSPARC V9, ECC-protected
L1 cache64 KB instruction + 64 KB data, per core
L2 cache22 MB (16-core X or X+); 24 MB (8-core X+)
Memory16 DIMM slots, populated 4/8/12/16; up to 512 GB with 32 GB DIMMs, up to 1 TB with 64 GB DIMMs
Internal storageUp to 8× 2.5" SAS-2 HDD or SSD; one SAS-2 RAID controller (RAID 0/1/1E/10)
Onboard I/O4× 1000BASE-T GbE; 3× PCIe 3.0 x8 low-profile slots; 2× USB 2.0
Service processorXSCF (eXtended System Control Facility), one per unit; dedicated 2× 1000BASE-T + serial (RJ-45) + USB
VirtualizationOracle VM Server for SPARC + Solaris Zones; up to 32 virtual systems
CPU ActivationCores licensed in pairs, minimum 2 up to the physical maximum
OS supportOracle Solaris 11.1+ and Solaris 10 1/13+; Solaris 8/9 via legacy branded zones
Dimensions42.5 mm H × 431 mm W × 721 mm D (1.67 × 17.0 × 28.4 in)
Weight18 kg (~40 lb)
Acoustic noise7.4 B / 58 dB (SPARC64 X+, one CPU); 6.8 B / 50 dB (SPARC64 X)
Operating temperature5–35°C at 0–500 m altitude, derating to 5–29°C at 1,501–3,000 m

Which processor generation

The M10-1 chassis carried two processor generations under one product name, and the vendor literature does not settle which is which at one point. The original 2013 part is the 16-core SPARC64 X. A later SPARC64 X+ option added on-chip SIMD, decimal floating point, and crypto instructions, offered as a 16-core/3.2 GHz, a 16-core/2.8 GHz, or an 8-core/3.7 GHz part.

The conflict is over the 16-core 2.8 GHz SKU. Fujitsu’s 2015 data sheet assigns 2.8 GHz to plain SPARC64 X and reserves the X+ label for the 3.2 GHz (16-core) and 3.7 GHz (8-core) parts. Oracle’s 2016 FAQ and its Oracle-branded data sheet instead describe “the 8-core 3.7 GHz, the 16-core 3.2 GHz or the 16-core 2.8 GHz SPARC64 X+ processor” — folding the same 2.8 GHz part into the X+ generation. I am not picking a side here. The machine in the lab is the 16-core 2.8 GHz configuration — exactly the SKU the two vendors label differently — bought secondhand as an Oracle-badged M10-1 (the listing’s X1109A is a bundled dual-port 10GbE SFP+ adapter per Oracle’s PCI-card documentation, not a system part number). Its own CPU FRU or part number settles which generation name applies, independent of the disagreement, and that check is still outstanding. The Processor row above therefore names both generations rather than committing to one.

Memory population

The 16 DIMM slots are filled in fixed steps, not one at a time: supported install counts are 4, 8, 12, or 16 modules (quarter, half, three-quarter, or full). Registered DIMMs come in 8/16/32 GB and load-reduced DIMMs at 64 GB; a full set of 32 GB R-DIMMs reaches 512 GB and a full set of 64 GB LR-DIMMs reaches 1 TB. The 512 GB / 1 TB ceilings and the 4/8/12/16 rule agree across the Oracle 2020 data sheet and the M10-1 service manual (C120-E681-19EN, §2.2.1). The earlier 2015 Fujitsu sheet predates 64 GB DIMM qualification and states only the 512 GB figure, which is a snapshot in time rather than a conflict.

The unit in the lab is populated with eight 16 GB DIMMs — 128 GB, a half fill of the sixteen slots — and two 600 GB SAS drives, per the eBay listing it came from.

Single-source and unresolved figures

These come from one document each and are recorded as unverified pending a second source:

Two figures genuinely conflict between vendor documents and are left unresolved. The 16-core 2.8 GHz generation label (X vs X+), covered above; and maximum power draw for SPARC64 X+, where the 2015 Fujitsu sheet says 805 W and the Oracle 2020 sheet says 849 W (100 V) / 824 W (200 V) — possibly different configuration assumptions between editions, but not reconciled by either. The SPARC64 X (original) figure is 763 W, from the 2015 Fujitsu sheet only.

Sources

Per the Fujitsu M10-1 data sheet (2015-04-07), the Oracle-branded M10-1 data sheet (copyright 2020) and FAQ (copyright 2016), and the M10-1 service manual (C120-E681-19EN) for the memory-population rules. All Fujitsu documents were recovered from the Internet Archive; the live and archived links are on the overview page. Rows carrying a single source or an unresolved conflict are called out in the notes above rather than presented as settled.