From 07f801a431ce07e6615ef692ebe2acfe53705931 Mon Sep 17 00:00:00 2001
From: David du Colombier <0intro@gmail.com>
Date: Tue, 27 Oct 1998 00:00:00 +0000
Subject: [PATCH] Plan 9 from Bell Labs 1998-10-27

---
 pc/etherelnk3.c | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/pc/etherelnk3.c b/pc/etherelnk3.c
index 79c12d923232ab8acbbe2b941566d44d0136f981..6eff56e4644fe6b8466f6cc260c27d4426f7aaf2 100644
--- a/pc/etherelnk3.c
+++ b/pc/etherelnk3.c
@@ -1045,6 +1045,9 @@ interrupt(Ureg*, void* arg)
 			 * According to the manual, maxCollisions does not require
 			 * a TxReset, merely a TxEnable. However, evidence points to
 			 * it being necessary on the 3C905. The jury is still out.
+			 * On busy or badly configured networks maxCollisions can
+			 * happen frequently enough for messages to be annoying so
+			 * keep quiet about them by popular request.
 			 */
 			if(s & (txJabber|txUnderrun|maxCollisions)){
 				if(ctlr->busmaster == 0)
@@ -1060,8 +1063,9 @@ interrupt(Ureg*, void* arg)
 					status |= dnComplete;
 			}
 
-			print("#l%d: txstatus 0x%uX, threshold %d\n",
-			    	ether->ctlrno, s, ctlr->txthreshold);
+			if(s & ~(txStatusComplete|maxCollisions))
+				print("#l%d: txstatus 0x%uX, threshold %d\n",
+			    		ether->ctlrno, s, ctlr->txthreshold);
 			COMMAND(port, TxEnable, 0);
 			ether->oerrs++;
 			status &= ~txComplete;