From owner-freebsd-smp Sun Feb 1 00:20:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07578 for freebsd-smp-outgoing; Sun, 1 Feb 1998 00:20:20 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07569 for ; Sun, 1 Feb 1998 00:20:17 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA03148; Sun, 1 Feb 1998 19:17:44 +1100 Date: Sun, 1 Feb 1998 19:17:44 +1100 From: Bruce Evans Message-Id: <199802010817.TAA03148@godzilla.zeta.org.au> To: ben@stuyts.nl, freebsd-smp@FreeBSD.ORG Subject: Re: Trouble with high-speed sio Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe freebsd-smp" >I've just added an additional (isa) uart board with two quad-speed 16550's to >my system. (Gigabyte 586DX with dual 166MMX). They are recognized by the >kernel: > >sio2 at 0x3e8-0x3ef irq 10 on isa >sio2: type 16550A >sio3 at 0x2e8-0x2ef irq 9 on isa >sio3: type 16550A > >and they seem to work fine, but I get a few disturbing console messages: > >sio3: 64 events for device with no tp This is harmless, but shouldn't happen. >sio2: 124 more interrupt-level buffer overflows (total 124) >sio2: 125 more interrupt-level buffer overflows (total 249) >sio2: 125 more interrupt-level buffer overflows (total 374) > >sio2 runs at 460 KBaud. (Kernel thinks 115 KB) >sio3 is unused / not-connected. 460000 bps is not supported. There is only enough interrupt-level buffering for 256000 bps at best. crtscts should reduce the flow to at most about 192000 bps if it works. Bruce