From cf4ed3a761468f7e6adc1bfad07bbb34fd7882ad Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bojan=20Ro=C5=A1ko?=
 <156314064+broskoTT@users.noreply.github.com>
Date: Tue, 29 Oct 2024 10:12:28 +0100
Subject: [PATCH] Fix l1 membar log (#218)

Related tt_metal CI issue:
https://github.com/tenstorrent/tt-metal/issues/14225
This was accidentally checked in #64

This filled up logs on CI machines that tt_metal uses and started
crashing them. This is non-deterministic behavior and also some later
jobs might fail due to this issue, not exactly the job responsible for
it -> which both made it hard to find the cause of the issue.

Hopefully this is the only issue, if there is an additional issue with
UMD being stuck we will investigate further.
---
 device/tt_silicon_driver.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/device/tt_silicon_driver.cpp b/device/tt_silicon_driver.cpp
index f432ef4c..98de517e 100644
--- a/device/tt_silicon_driver.cpp
+++ b/device/tt_silicon_driver.cpp
@@ -2537,7 +2537,7 @@ void tt_SiliconDevice::set_membar_flag(const chip_id_t chip, const std::unordere
                     cores_synced.insert(core);
                 }
                 else {
-                    log_info(LogSiliconDriver, "Waiting for core {} to recieve mem bar flag {} in function", core.str(), barrier_value);
+                    log_trace(LogSiliconDriver, "Waiting for core {} to recieve mem bar flag {} in function", core.str(), barrier_value);
                 }
             }
         }