From: Farah Kassabri <fkassa...@habana.ai>
In order to have better debuggability upon encountering FW issues,
We are adding additional info once CPU packet timeout expires.
Signed-off-by: Farah Kassabri <fkassa...@habana.ai>
Reviewed-by: Ofir Bitton <obit...@habana.ai>
---
drivers/accel/habanalabs/common/firmware_if.c | 14 +++++++++++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/drivers/accel/habanalabs/common/firmware_if.c
b/drivers/accel/habanalabs/common/firmware_if.c
index 6f0c40b12072..3cd8a1f69980 100644
--- a/drivers/accel/habanalabs/common/firmware_if.c
+++ b/drivers/accel/habanalabs/common/firmware_if.c
@@ -460,11 +460,19 @@ int hl_fw_send_cpu_message(struct hl_device *hdev, u32
hw_queue_id, u32 *msg,
/* If FW performed reset just before sending it a packet, we
will get a timeout.
* This is expected behavior, hence no need for error message.
*/
- if (!hl_device_operational(hdev, NULL) &&
!hdev->reset_info.in_compute_reset)
+ if (!hl_device_operational(hdev, NULL) &&
!hdev->reset_info.in_compute_reset) {
dev_dbg(hdev->dev, "Device CPU packet timeout (0x%x)
due to FW reset\n",
tmp);
- else
- dev_err(hdev->dev, "Device CPU packet timeout (status =
0x%x)\n", tmp);
+ } else {
+ struct hl_bd *bd = queue->kernel_address;
+
+ bd += hl_pi_2_offset(queue->pi);
+
+ dev_err(hdev->dev, "Device CPU packet timeout (status =
0x%x)\n"
+ "Pkt info: dma_addr: 0x%llx,
kernel_addr: %p, len:0x%x, ctl: 0x%x, ptr:0x%llx, dram_bd:%u\n",
+ tmp, pkt_dma_addr, (void *)pkt,
bd->len, bd->ctl, bd->ptr,
+ queue->dram_bd);
+ }
hdev->device_cpu_disabled = true;
goto out;
}
--
2.34.1
