When installing Oracle Solaris 11 11/11 onto a 3-TB hard disk drive (HDD), the Oracle Solaris 11 11/11 text installer presents this misleading default to the installer: “Use the whole disk.” This default setting seems to be acceptable because other user messages in the installation program indicate that only 2-TB of the HDD will be used.

If this default setting is accepted, the installation program mistakenly loads Oracle Solaris 11 11/11 onto the entire 3-TB HDD, instead of a 2-TB partition, and the installation fails.

• Oracle Solaris 11 11/11

• Releases 1.0, 1.1, 1.1.1, and 1.2

For text installs, in the Fdisk Partition screen, when prompted, select Use a partition of the disk, instead of Use the whole disk.

Systems containing SR-IOV capable devices in certain configurations might encounter problems with the X11 Xorg graphical user interface (GUI) not starting on startup. Systems running the Oracle Solaris 11 11/11 preinstalled operating system software will already contain the workaround for this issue. However, if you do a new installation using the Oracle Solaris 11 11/11 distribution media and observe the X11 GUI failing to start, you will have to perform the workaround described below.

• Oracle Solaris 11 11/11

• Releases 1.0, 1.1, 1.1.1, and 1.2

If you are doing a GUI-based install of Oracle Solaris 11 11/11, then you need to perform steps 1-3 below to allow the GUI to start for the install, then perform all of the steps (that is, steps 1-4) on the first boot after the install.

If you log in to the system without using the graphical console (by using the text or serial console or Ethernet login), then perform step 4 after the first boot after the install.

1. Edit the GRUB line displayed when booting and change the default graphics console to either ttya for a serial console, or text for VGA text, depending on your preference. Add -kd as kernel flags as well.

   For example:

   kernel /platform/i86pc/kernel/amd64/unix

   becomes:

   kernel /platform/i86pc/kernel/amd64/unix -kd -Bconsole=text

   or

   kernel /platform/i86pc/kernel/amd64/unix -kd -Bconsole=ttya

   To edit the GRUB line, do the following:

   Press ‘e' to edit the grub entry.

   Press ‘e' to edit the selected line.

   Type the changes.

   Press <esc> to finish.

   Press b to boot.

2. When the Oracle Solaris OS drops into the debugger, enter the following to set a breakpoint at pcie'_init:

   [0]> ::bp pcie'_init

   :c

3. When the Oracle Solaris OS hits the breakpoint, enter the following to set the variable 0> pcie_br_flags/W 0:

   pcie'pcie_br_flags: 0x1 = 0x0

   [0]>:c

4. After the system has booted and you can log in, you can avoid the need for setting the variable using the debugger by appending this line: set pcie:pcie_br_flags=0 to /etc/system.

   #echo 'set pcie:pcie_br_flags=0' >> /etc/system

On the server, Fault Management Architecture (FMA) topology does not include USB controllers. If an FMA ereport is generated for a EHCI USB controller, the fmadm faulty command will generate an unexpected_telemetry fault and the Service Required LED will be illuminated.

• Oracle Solaris 11 11/11

• Releases 1.0, 1.1, 1.1.1 and 1.2

Consult /var/adm/messages for more information about the source of the error.

To clear the fault(s) and extinguish the Service Required LED, perform the following steps:

1. On the Solaris host, log in as root and type: fmadm faulty.

   Record the uuid of the fault.

2. To clear the fault, type: fmadm acquit <uuid>.

   This command will clear the fault from both the Oracle Solaris Operating System and the service processor.

3. Log in to the service processor as root and restart the service processor. Type: -> reset /SP

During system boot, WARNING: npel: no ranges property might appear on the console.

• Oracle Solaris 10 8/11 and Oracle Solaris 11 11/11

• Releases 1.0, 1.1, 1.1.1, and 1.2

This message is benign and can be ignored.

Customers using the Oracle Solaris 11 11/11 Preinstall option might encounter a five-minute delay during first boot. During this delay, the system is configuring the ilomconfig-interconnect service. This only occurs on first boot; the system will boot normally on subsequent restarts.Customers monitoring the system's first boot from the system console will observe the system reaching this stage in the boot-up and pause for approximately five minutes and display the following warning:

SunOS Release 5.11 Version 11.0 64-bit Copyright (c) 1983, 2011, Oracle and/or its affiliates. All right reserved. WARNING: npel: no ranges property

Please note that this issue is not related to the WARNING: npel: no ranges property message, which is a separate issue that is documented in Bug ID 15777292 (formerly CR 7151581).

• Oracle Solaris 11 11/11 Preinstall

• Releases 1.0, 1.1, 1.1.1, and 1.2

Wait for the ilomconfig-interconnect service to complete its configuration.

Oracle Integrated Lights Out Manager (ILOM) might not be able to repair or clear a fault diagnosed by the Oracle Solaris Operating System.

• Oracle ILOM 3.1

• Oracle Solaris 10 8/11 and 11 11/11

• Releases 1.0, 1.1, 1.1.1, and 1.2

Do either of the following:

• Use the Oracle Solaris Operating System to repair or clear the fault.

• Run the following procedure from the faultmgmt shell of the Oracle ILOM command-line interface (CLI).

1. Find the uuid of the faults in the output of fmadm faulty.

2. Clear the faults using fmadm acquit <uuid>

Oracle Integrated Lights Out Manager (ILOM) Hard Cap power setting fails to set maximum power limit on the server with Oracle Solaris Operating Systems if the Hard Cap power setting is enabled before the hand off to the operating system.

• Oracle ILOM 3.1

• Oracle Solaris 10 8/11 and 11 11/11

• Releases 1.0, 1.1, 1.1.1, and 1.2

None.

In single-processor systems, /usr/lib/fm/fmd/fmtopo enumerates PCIe devices incorrectly. /usr/sbin/prtdiag and /usr/sbin/smbios report inaccurate status information for PCIe slot 1, which is nonfunctional in single-processor systems.

• Oracle Solaris 10 8/11 and 11 11/11

• Releases 1.1, 1.1.1, and 1.2

For the PCIe slot label output by fmdump, fmadm, and fmtopo, use the following information to correctly identify the physical slot information.

• fmtopo - PCIE2 / Physical slot - PCIE2 / Device path - /pci@0,0/pci8086,3c06@2,2

• fmtopo - PCIE1 / Physical slot - PCIE3 / Device path - /pci@0,0/pci8086,3c08@3

• fmtopo - PCIE4 / Physical slot - PCIE4 / Device path - /pci@0,0/pci8086,3c0@3,2

• Oracle Solaris 11.1

• Oracle VTS 7.0ps14

• Release 1.2

None.

The Oracle Solaris Operating System panics during a system power off or during a system reboot when either the SG-XPCIEFCOE2-Q-SR or SG-XPCIEFCOE2-Q-TA PCIe cards are installed in the system.

• Sun Storage 10 GbE PCIe FCoE Converged Network Adapter: QLogic Low Profile, Dual Port and SR Optics (SG-XPCIEFCOE2-Q-SR)

• Sun Storage 10 GbE PCIe FCoE Converged Network Adapter: QLogic Low Profile, Dual Port and Twin-Ax (SG-XPCIEFCOE2-Q-TA)

• Oracle Solaris 11 11/11 and 11.1

• Release 1.2

There is currently no workaround for this issue. This issue is scheduled to be fixed in a later release of the Oracle Solaris OS.

The Oracle Solaris 11.1 Operating System installation process might fail at the following point during the OS installation if you are using an ISO image to install the OS.Enter user name for system maintenance (control-d tobypass):

• Oracle Solaris 11.1

• Release 1.2

If this issue occurs during the Oracle Solaris 11.1 Operating System installation, disable the Intel Virtualization Technology for Directed I/O (VT-d) setting in the system BIOS settings. This setting can be disabled in the BIOS Setup Utility IO > I/O Virtualization menu.

For information on entering the BIOS Setup Utility and disabling the VT-d setting, see “Accessing the BIOS Setup Utility” in the Sun Server X3-2 Administration Guide.