Aaeon UP Xtreme i11 Getting Started Manual page 34

Hide thumbs Also See for UP Xtreme i11:

Table of Contents

Ultimately, we're working on improving the performing of the AssetDCI driver, and

behaving more graciously when overflow is encountered. But, in the interim, it is key to

ensure that the trace data collected is relatively "sparse". Focus your debugging in the

specific area of interest. Don't try to collect all Port IN/OUT from reset through to the

UEFI shell. At 750K I/Os per second, you'll swamp the host debugger processing, and

you can't deal with all that data anyway.

Note that this only happens with AET – that is, you can only overflow by collecting too

much AET data. It does not apply to LBR, SW/FW Trace, SVEN, or Intel Processor

Trace. It may take some trial and error to limit the scope of your event data collection.

NOTE: Release 7.12.18 and later enhanced the performance of the ASSET DCI driver.

Except in very rare circumstances, trace buffer overflows should not be seen. We've

preserved this section of the Getting Started Guide in case they are still encountered

out in the wild – please contact our

Support

line directly if you see one.

SourcePoint Getting Started Guide – UP Xtreme i11

Table of Contents