|Skip Navigation Links|
|Exit Print View|
|Oracle® VM Server for SPARC 184.108.40.206, 3.1.1, and 3.1 Release Notes|
Bug ID 18323562: An Oracle Solaris 10 root domain might panic when rebooting. The Oracle Solaris 10 root domain has at least two PCIe buses and the virtual functions from the physical functions in different buses are assigned to guest domains. That is, if events from different buses on guest domains are received in parallel, the root domain might panic. This panic occurs rarely.
panic[cpu3]/thread=2a100365c80: BAD TRAP: type=31 rp=2a1003652b0 addr=2000 mmu_fsr=0 occurred in module "pcie" due to an illegal access to a user address
Bug ID 18323370: An Oracle Solaris 10 root domain might panic if you destroy virtual functions and then run the prtdiag command.
The prtdiag command might cause a panic when attempting to access virtual function device nodes that were just destroyed:
panic[cpu31]/thread=2a10140bc80: Fatal error has occured in: PCIe fabric.(0x1)(0x43)
And the prtdiag command prints messages such as the following:
DEV_GET failed -1 Invalid argument 4.0.2 offset 0xff /SYS/PCI-EM4 PCIE fibre-channel-pciex10df,e200 -- /pci@600/pci@1/pci@0/pci@4/fibre-channel@0,2
These messages occur because the prtdiag command attempts to access virtual function device nodes that have been destroyed. The nodes still appear in the picl tree, but not in the actual device tree.
Workaround: To avoid the panic, add the following line to the /etc/system file on the Oracle Solaris 10 root domain:
Also refresh the picl daemon to avoid the Invalid argument messages:
# svcadm refresh picl
Bug ID 18030411: The primary domain might hang if you stop and start I/O domains frequently and in rapid succession. As a result of this behavior, the InfiniBand HCA stops responding and causes the primary domain to hang.
If you experience this problem, you might see messages on the console or in the messages file that are similar to the following:
VF3: PF has failed Mcxnex: HW2SW_MPT command @ failed: 0000ffff Hermon: MAD_IFC (port 01) command failed: 0000ffff WARNING: mcxnex0: Device Error: HCR Timeout waiting for command go bit
Recovery: To avoid this problem, do not perform unnecessary stop and start operations of the I/O domains. Instead, perform an orderly shutdown of the I/O domain.
Workaround: If the primary domain hangs for this reason, reset the system in one of the following ways:
Perform a reboot of the domain
primary# ldm stop -r domain-name
Perform a reset in the SP
-> reset /SYS
Bug ID 17623156: When you create Fibre Channel virtual functions, you might see the following warnings:
WARNING: kmem_cache_destroy: 'px0_emlxs3_3_cache2' (3000383e030) not empty WARNING: vmem_destroy('px0_emlxs3_3_vmem_top'): leaked 262144 identifiers
These messages do not affect the normal operation of the system and you can ignore them.
Bug ID 16397888: After you add or destroy virtual functions, it might take up to five minutes before you can attempt to add or destroy more virtual functions from the Fibre Channel physical function.
If you attempt to perform these operations before five minutes elapse, the operations fail with a message similar to the following:
The attempt to offline the pf /SYS/PCI-EM4/IOVFC.PF0 in domain primary failed. Error message from svc:/ldoms/agents in domain primary: CMD_OFFLINE Failed. ERROR: devices or resources are busy.
Workaround: Wait five minutes before you attempt another IOV operation on the Fibre Channel physical function.
To perform all necessary configuration options in a single command, use the ldm create-vf -n max or ldm destroy-vf -n max command.
On a Fujitsu M10 system you can assign PCIe endpoint devices and SR-IOV virtual functions from a particular PCIe bus to a maximum of 24 domains. While on SPARC T-Series and SPARC M-Series platforms, you can assign PCIe endpoint devices and SR-IOV virtual functions from a particular PCIe bus to a maximum of 15 domains.
Caution - Review this section before you deploy InfiniBand SR-IOV in your Oracle VM Server for SPARC 3.1 environment.
This section describes the known issues for the InfiniBand SR-IOV feature in the initial release of Oracle VM Server for SPARC 3.1.
The reboot of an Oracle Solaris 220.127.116.11.0 I/O domain that has InfiniBand virtual functions assigned to it occasionally panics the corresponding root domain. See bug ID 17336355.
An Oracle Solaris 10 1/13 I/O domain that has InfiniBand virtual functions assigned to it sometimes panics during reboot. The I/O domain runs the Oracle Solaris 10 1/13 OS plus the required patches. See bug IDs 17382933, 17361763, 17329218, and 17336035.
Bug ID 16979993: An attempt to use dynamic SR-IOV operations on an InfiniBand device results in confusing and inappropriate error messages.
Dynamic SR-IOV is not supported for InfiniBand devices.
Workaround: Manage InfiniBand virtual functions by performing the one of the following procedures: