On SPARC T5-2, removing bus with usbecm device (pci_1 / pci@340) from primary/control domain can impact FMA and ldmd processing (Doc ID 1948940.1)

Last updated on AUGUST 26, 2016

Applies to:

Solaris Operating System - Version 10 3/05 and later
SPARC T5-2 - Version All Versions and later
Oracle Solaris on SPARC (64-bit)

Symptoms

If a SPARC T5-2 is configured with multiple root domains, and bus pci_1 (pci@340) is removed from the control domain, the control domain will not have access to the usbecm device. The logical domain daemon uses this device to access the proxy to receive CPU and memory FMA events from the Service Processor. This note is specific to the SPARC T5-2 system, but similar considerations apply to SPARC M5-32 and M6-32 servers. Please see DocID 1942045.1.for details on those servers. Note that this pertains to T5-2 servers with two CPU sockets. The T5-2 single socket server has two buses (pci@340/pci_1, pci@300/pci_0) which are both needed by the control domain, so a separate root domain cannot be created.

Changes

This situation occurs if the bus containing usbecm device is removed from the control domain. The available buses, and the bus used for this device, should be determined before making bus assignments by issuing the following commands. The first command lists the names of the buses and their pseudonyms. All of the commands shown here are run from the control domain.

The output from these commands indicates that the usbecm device is on bus pci@340, which has the pseudonym pci_1.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms