Known Direct I/O Issues - SPARC M5-32 and SPARC M6-32 Servers Product Notes

SPARC M5-32 and SPARC M6-32 Servers Product Notes

Exit Print View

» ...Documentation Home » SPARC M5-32 and SPARC M6-32 Servers ... » SPARC M5-32 and SPARC M6-32 Servers Product Notes » Known Issues » Known Direct I/O Issues

Updated: March 2016

SPARC M5-32 and SPARC M6-32 Servers Product Notes

Document Information

Using This Documentation

Late-Breaking Information

Known General Issues

Known Direct I/O Issues

Known Oracle ILOM Issues

Known Oracle Solaris Issues

Known Firmware Issue: SP Failover During Upgrading System Firmware From 9.2.1.c or Older to 9.3.0.c or Later (21051993)

Known Hardware Issue: EMS RJ45 Ethernet Speed and Activity LEDs Are Dim (16340264)

Known Documentation Issue: SPARC M5/M6-32 Service Manual Uses Inconsistent Hot-Plug-Swap Terminology (20238762)

Issues Resolved With Firmware Update

Language:

Known Direct I/O Issues

The issues described in this topic are resolved in Oracle VM Server for SPARC 3.0.0.3. Upgrade your software to avoid these issues.

Note - The term "Static Direct I/O (SDIO)" refers to Direct I/O functionality. More information about Direct I/O is provided in the Oracle VM Server for SPARC Administration Guide.

If you do not upgrade to system firmware 9.0.2 or newer, only single-DCU PDomain configurations support SDIO.

This is the known Direct I/O issue for the SPARC M6-32 and SPARC M5-32 servers:

System Sends Sigabrt Explicitly From Hypervisor Calls (16198869)

Copyright © 2013, 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices