frecon: dbus: Move "normal" error messages to DEBUG
It is normal for dbus initialization to take a number of attempts
to connect, so let's not print those messages by default.
We will still get an error if DBUS initialization times out in
dbus_init_wait.
BUG=b:183336123
TEST=emerge-asurada -v frecon && cros deploy dut9999 frecon
dmesg | grep frecon => less messages
Change-Id: Ic2cb6d67c6721a7ea69037ce5547b1b45580095d
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/frecon/+/2777713
Reviewed-by: Dominik Behr <dbehr@chromium.org>
Tested-by: Nicolas Boichat <drinkcat@chromium.org>
Commit-Queue: Nicolas Boichat <drinkcat@chromium.org>
diff --git a/dbus_full.c b/dbus_full.c
index d2a89d9..9028ae2 100644
--- a/dbus_full.c
+++ b/dbus_full.c
@@ -133,7 +133,7 @@
new_dbus->conn = dbus_bus_get(DBUS_BUS_SYSTEM, &err);
if (dbus_error_is_set(&err)) {
if (!dbus_connect_fail) {
- LOG(ERROR, "Cannot get DBUS connection");
+ LOG(DEBUG, "Cannot get DBUS connection");
dbus_connect_fail = true;
dbus_connect_fail_time = get_monotonic_time_ms();
}
@@ -143,7 +143,7 @@
if (dbus_connect_fail) {
int64_t t = get_monotonic_time_ms() - dbus_connect_fail_time;
- LOG(INFO, "DBUS connected after %.1f seconds", (float)t / 1000.0f);
+ LOG(DEBUG, "DBUS connected after %.1f seconds", (float)t / 1000.0f);
}
result = dbus_bus_request_name(new_dbus->conn, kFreconDbusInterface,
