Thanks for sending an issue! Please fill in the following template to help quickly solve your problem.

Describe the current behavior / 问题描述 (Mandatory / 必填)

以下上报点根据 评审建议整改
[PID: 292193] 2026-06-04-19:55:17.298.603 Not_Supported(EE1006): StreamAbort execution failed because abort model stream is not supported.
TraceBack (most recent call last):
rtStreamAbort execution failed, reason=stream invalid[FUNC:FuncErrorReason][FILE:error_message_manage.cc][LINE:65]
1、有ACL的打印acl，没有的打印完整rt接口或者语义解释
2、stream等对象打印具体id值，model stream描述不合适，列出具体不支持的场景（设置为下沉流或者绑定模型)，列出可查接口，参考对外接口资料说明说明，写具体，指导客户修复问题

[PID: 292844] 2026-06-04-19:56:44.265.173 Resource_Error_Bind_Stream(EE1007): Failed to bind stream with ID 46. Reason: The stream is already bound.
Solution: Unbind the stream from the already bound model and then rebind it to the current model.
TraceBack (most recent call last):
Failed to bind the stream to the model, model_id=49, stream_id=46, retCode=0x7030005.[FUNC:ModelBindStream][FILE:context.cc][LINE:1460]
rtModelBindStream execution failed, reason=the relationship between the model and stream is incorrect.[FUNC:FuncErrorReason][FILE:error_message_manage.cc][LINE:65]
1、在reason中打出modelid，已绑定的model以及想要绑定的model
2、stream with id描述确认一下，对比原始中文描述

[PID: 218319] 2026-06-04-16:10:07.347.473 Execution_Error_Invalid_Context(EE1010): StreamDestroy execution failed because stream 45 does not belong to the current context.
TraceBack (most recent call last):
rtStreamDestroy execution failed, reason=stream not in current context[FUNC:FuncErrorReason][FILE:error_message_manage.cc][LINE:65]
1、按照翻译优化stream id的打印
2、核实是否可以打出context指针

[PID: 1162081] 2026-06-06-14:32:03.492.509 Resource_Error_Insufficient_Host_Memory(EE1013): Failed to allocate 280 bytes host memory for Runtime.
Possible Cause: Allocation failed due to insufficient host memory.
Solution: Stop unnecessary processes and ensure that the required memory is available.
TraceBack (most recent call last):
Check param failed, dev can not be NULL![FUNC:DeviceRetain][FILE:runtime.cc][LINE:2774]
Check param failed, dev can not be NULL![FUNC:PrimaryContextRetain][FILE:runtime.cc][LINE:2384]
Check param failed, ctx can not be NULL![FUNC:PrimaryContextRetain][FILE:runtime.cc][LINE:2415]
Check param failed, context can not be null.[FUNC:SetDevice][FILE:api_impl.cc][LINE:3282]
rtSetDeviceEx execution failed, reason=device retain error[FUNC:FuncErrorReason][FILE:error_message_manage.cc][LINE:65]
1、solution需要修改，ensure that the required memory is available提前
2、核实是否可以打出具体的内存申请的操作（打出最原始的申请内存接口（new\map\malloc））

RTS_ACL_ACLGRAPH_0009:(tid=[563758],line=[0811])
[PID: 563758] 2026-06-01-22:55:01.636.915 Invalid_Argument(EE1017): UpdateKernelParams failed. Parameter task is invalid. Reason: The input task must be a compute task on Cube Core or Vector Core. You can call the aclmdlRITaskGetType API to obtain the task type.
TraceBack (most recent call last):
task set params failed[FUNC:TaskSetParams][FILE:api_impl.cc][LINE:9102]
The argument is invalid. Reason: rtModelTaskSetParams execution failed.
Set kernel params failed, runtime result = 107000[FUNC:ReportCallError][FILE:log_inner.cpp][LINE:148]

1、结合资料优化reason表达，表达出setparam之前先通过aclmdlRITaskGetType获取task类型，以及出错后可以通过aclmdlRITaskGetType接口确认task类型

RTS_ACL_ACLGRAPH_0009:(tid=[563758],line=[0811])
[PID: 563758] 2026-06-01-22:55:01.636.915 Invalid_Argument(EE1017): UpdateKernelParams failed. Parameter task is invalid. Reason: The input task must be a compute task on Cube Core or Vector Core. You can call the aclmdlRITaskGetType API to obtain the task type.
TraceBack (most recent call last):
task set params failed[FUNC:TaskSetParams][FILE:api_impl.cc][LINE:9102]
The argument is invalid. Reason: rtModelTaskSetParams execution failed.
Set kernel params failed, runtime result = 107000[FUNC:ReportCallError][FILE:log_inner.cpp][LINE:148]
1、solution需要修改，ensure that the required memory is available提前
2、核实是否可以打出具体的内存申请的操作（打出最原始的申请内存接口（new\map\malloc）

[PID: 354222] 2026-06-01-06:39:28.232.280 Invalid_Argument(EE1012): NotifyWait failed. Value 1 for current deviceId is invalid. Reason: The current device cannot deliver Notify Wait, the corresponding Notify Wait must be delivered on the device that creates the IPC Notify.
TraceBack (most recent call last):
The argument is invalid. Reason: rtNotifyWaitWithTimeOut execution failed.

1、NotifyWait failed：改为接口名称或者语义化内部接口函数
2、reason内容需要进行完善，补充指导客户修复问题的方法
解决如下：
当前设备无法发送 Notify Wait 消息。为解决此问题，请确保 Notify Wait 由创建 IPC Notify 的同一设备发送。
The current device cannot deliver the Notify Wait message. To resolve this issue, please ensure that the Notify Wait is sent from the same device that created the IPC Notify.

补充两条翻译:
Aborting stream (stream_id=10) that is already bound to a model (model_id=10) is not supported.
The current stream (stream_id) has been bound to a model (model_id=%d) and cannot be bound to the input model (model_id=%d).

枚举值表达：
错误码日志中枚举值打印规范

规则1：用户传入枚举值的打印

用户传入的枚举参数，使用枚举转字符串函数打印，格式为 枚举名(数值)：

• 合法值：GLOBAL(0)、THREAD_LOCAL(1)、RELAXED(2)
• 非法值（不在枚举定义中）：UNKNOWN(100)，必须同时打印数值

规则2：期望值（合法取值范围）的描述

期望值描述分两种情况：

期望值类型	描述方式	示例
连续区间 [a, b) 或 [a, b]	保留原始区间描述
离散枚举值（1个或多个具体枚举值）	用 枚举名(数值) 格式，与规则1保持一致	RELAXED(2) 或 GLOBAL(0) THREAD_LOCAL(1)

Environment / 环境信息 (Mandatory / 必填)

A3

Steps to reproduce the issue / 重现步骤 (Mandatory / 必填)

调用rt接口构造异常场景

Describe the expected behavior / 预期结果 (Mandatory / 必填)

errmessage描述清晰

Related log / screenshot / 日志 / 截图 (Mandatory / 必填)

已提供

Special notes for this issue/备注 (Optional / 选填)