Commit 062191ad authored by Chia-Lin Kao (AceLan)'s avatar Chia-Lin Kao (AceLan) Committed by Mika Westerberg
Browse files

thunderbolt: Log path activation failures without WARN backtraces 



tb_path_activate() currently logs failures with tb_WARN(), which triggers
a stack trace. Transient conditions such as lane bonding or Type-C link
hiccups can fail path activation briefly, and the resulting backtraces are
noisy without aiding diagnosis.

Switch to tb_warn() for all path activation failures. The error code is
already returned to callers, and the warning still shows the message
without the backtrace.

Signed-off-by: default avatarChia-Lin Kao (AceLan) <acelan.kao@canonical.com>
Signed-off-by: default avatarMika Westerberg <mika.westerberg@linux.intel.com>
parent 0c90fd37

drivers/thunderbolt/path.c

+1 −1
Original line number Diff line number Diff line
@@ -586,7 +586,7 @@ int tb_path_activate(struct tb_path *path) 
	tb_dbg(path->tb, "%s path activation complete\n", path->name);

	return 0;

err:

	tb_WARN(path->tb, "%s path activation failed\n", path->name);

	tb_warn(path->tb, "%s path activation failed: %d\n", path->name, res);

	return res;

}