Skip to contentSkip to conversation

osm_sa_path_record.c: Fix misleading error messages during sweep

PATCH New Hal Rosenstock 1 participant 1 message Jun 1, 2014 InfiniBand

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 osm_sa_path_record.c: Fix misleading error messages during sweep

From: Tomer Cohen <tomerco-VPRAkNaXOzVWk0Htik3J/[email protected]>

PathQuery is received during heavy-sweep caused by just rebooted node. The PathQuery is received for the new node during discovery stage when no LID is still assigned to the node.

Fix: change from using OSM_LOG_ERROR to OSM_LOG_DEBUG for ERR 1F20 and 1F21

---
 opensm/osm_sa_path_record.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
opensm/osm_sa_path_record.c +2 -2
index aaf2f2f..a915636 100644
@@ -1113,7 +1113,7 @@ static void pr_rcv_get_port_pair_paths(IN osm_sa_t * sa,
 					  &src_lid_min_ho, &src_lid_max_ho);
 
 	if (src_lid_min_ho == 0) {
-		OSM_LOG(sa->p_log, OSM_LOG_ERROR, "ERR 1F20:"
+		OSM_LOG(sa->p_log, OSM_LOG_DEBUG,
 			"Obtained source LID of 0. No such LID possible "
 			"(%s port %d)\n",
 			p_src_alias_guid->p_base_port->p_node->print_desc,
@@ -1122,7 +1122,7 @@ static void pr_rcv_get_port_pair_paths(IN osm_sa_t * sa,
 	}
 
 	if (dest_lid_min_ho == 0) {
-		OSM_LOG(sa->p_log, OSM_LOG_ERROR, "ERR 1F21:"
+		OSM_LOG(sa->p_log, OSM_LOG_DEBUG,
 			"Obtained destination LID of 0. No such LID possible "
 			"(%s port %d)\n",
 			p_dest_alias_guid->p_base_port->p_node->print_desc,
Signature · 6 lines
1.7.8.2

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html