From owner-freebsd-stable Fri Sep 1 11:41:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cgi.sstar.com (cgi.sstar.com [209.205.176.12]) by hub.freebsd.org (Postfix) with ESMTP id 4E46E37B422 for ; Fri, 1 Sep 2000 11:41:26 -0700 (PDT) Received: from bluto.jimking.net (bluto.jimking.net [216.54.255.8]) by cgi.sstar.com (8.9.3/8.9.3) with ESMTP id NAA82781; Fri, 1 Sep 2000 13:41:19 -0500 (CDT) (envelope-from jim@jimking.net) Received: from jking (jking.lgc.com [134.132.75.164]) by bluto.jimking.net (8.9.3/8.9.3) with SMTP id NAA68660; Fri, 1 Sep 2000 13:41:01 -0500 (CDT) (envelope-from jim@jimking.net) Message-ID: <002d01c01444$350c8b00$a44b8486@jking> From: "Jim King" To: "Gary Kline" , "Warner Losh" Cc: References: <200009010501.WAA54972@tao.thought.org> <200009011832.MAA37168@harmony.village.org> Subject: Re: bad 16550A maybe? Date: Fri, 1 Sep 2000 13:41:01 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 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. I think we'd see a lot fewer of these messages on the mailing lists if sio.c set the 16550A trigger level to 8 bytes instead of 14 bytes. That's the first thing I do when I see this problem, and that usually fixes it; much easier than replacing the misbehaving hardware. :-) Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message