From owner-freebsd-stable Fri Sep 1 11:32:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5C95037B42C for ; Fri, 1 Sep 2000 11:32:44 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA08968; Fri, 1 Sep 2000 12:32:43 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA37168; Fri, 1 Sep 2000 12:32:14 -0600 (MDT) Message-Id: <200009011832.MAA37168@harmony.village.org> To: Gary Kline Subject: Re: bad 16550A maybe? Cc: freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Thu, 31 Aug 2000 22:01:56 PDT." <200009010501.WAA54972@tao.thought.org> References: <200009010501.WAA54972@tao.thought.org> Date: Fri, 01 Sep 2000 12:32:14 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009010501.WAA54972@tao.thought.org> Gary Kline writes: : This just showed up on my console (and dmesg) from my new 4.1 system: : sio0: 1 more silo overflow (total 1) : Could this be why moused is having trouble with recognizing my : COM1 mouse? Bad 16550A? Maybe. silo overflows happen because the machine is too slow to service the interrupt before the buffer overflows (but unless it is a 386SX25 you should have enough CPU power). It can also be caused by baud rate mismatches, but that's fairly rare and unusual (you usually get framing errors from a 16550A in this case). This can also be caused by other hardware misbehaving and blocking interrupts. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message