Known Issues
This section describes hardware, firmware, and software issues known to exist at this
release of Oracle’s Sun Flash Accelerator F20 PCIe card.
|
|
|
6868341 |
In some cases,
the server fails to recognize the card after a SATA controller firmware upgrade.
The upgrade fails with an error message similar to the following: MPT BIOS Fault 0Dh encountered at adapter PCI(02h,00h,00h) In addition, the
card does not appear in the server device tree. |
Reboot the server a second
time. The card is recognized after the second reboot. |
6881281 |
FMod support clips may break
if pressed too far during FMod removal. |
Loosen the clip screws when replacing an FMod,
as described in the Sun Flash Accelerator F20 PCIe User’s Guide. |
6809711 |
Under heavy
I/O load in Solaris, a large number of messages may be seen indicating
I/O retries (such as incomplete read- retrying). These messages occur due to a
hardware bug in the LSI SAS controller that may incorrectly detect underrun conditions and
report them to the driver. Overall data integrity is not compromised, but a
performance impact may be observed due to the messages logged and retries required. |
Ignore
the retry messages or use an external means to throttle I/O throughput down
to a level where these messages are not being produced in great numbers.
The method required to throttle I/O will be very configuration and workload specific. |
n/a |
If
there is a significant unexpected drop in card performance, the supercap module on
the ESM should be checked. |
Look at the back panel of the card to determine
if the amber ESM Service Required LED is lit. Service the ESM as
described in the Sun Flash Accelerator F20 PCIe User’s Guide. |
6881856 |
On occasion, the system BIOS may not give the card
firmware enough time to load. When this situation occurs, the card cannot be
seen by host server. |
Reboot the server. |
6951778 |
Repeated power cycling with minimum traffic
causes DOM to zombie. |
Do not run continuous power cycle tests with minimum traffic to
the DOM. If power cycling is needed for qualification either ensure there is
no traffic to the DOM including SMART transactions or allow the SuperCap to
fully charge and run transactions to the DOM. Because the pre-existing state of
a DOM is unknown, it could have been power cycled previously, the number of
power cycles cannot be specified. |
|