Abnormal Operator Input/Output Data Addresses

Analysis Result

If the info.txt file provides the following analysis conclusion, the address is invalid.

"**********************Root cause conclusion******************"
Please check addrs. The addr of input/output is used but not alloc, details in "4. Input and output of node"

In the info.txt file, the following information is displayed in 4. Input and output of node:

****************4. Input and output of node*******************
*[ERROR]input[1] is out of range
*[ERROR]input[2] is out of range

input[0] addr: 0x124080042000 end_addr:0x124080042100 size: 0x100
input[1] addr: 0xaaaaaaaa end_addr:0xaaaaaab2 size: 0x8
input[2] addr: 0x0 end_addr:0x4 size: 0x4
output[0] addr: 0x124080052000 end_addr:0x124080052008 size: 0x8
arg[4][0x1240003E5070] cannot found alloc log, if it is not tiling_gm, please check
arg[2][0x0] cannot found alloc log, if it is not tiling_gm, please check
workspace_bytes:0

Fault root causes

The msaicerr tool checks the logs related to the addresses that are successfully applied for and released on the device, and determines the available memory address range by calculating the difference set of the two values. If the input and output addresses are not within the range, an error is reported.

Solution

If the address is invalid, check whether the operator address is valid. The options are:

If the input/output of the offline inference graph or a single operator is called, the address space applied for in the user application is incorrect. In this case, check the application source code.
In other cases, the error occurs generally because the address space requested by the framework is abnormal. You need to prepare the fault information collected by the asys tool and the analysis result files of the msaicerr tool, and then contact technical support for check and locating. After obtaining the logs, click here to contact technical support.

Parent topic: Typical Cases