From owner-freebsd-current Sun May 25 15:46:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA13147 for current-outgoing; Sun, 25 May 1997 15:46:15 -0700 (PDT) Received: from helbig.informatik.ba-stuttgart.de (helbig.informatik.ba-stuttgart.de [141.31.166.22]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA13137 for ; Sun, 25 May 1997 15:46:11 -0700 (PDT) Received: (from helbig@localhost) by helbig.informatik.ba-stuttgart.de (8.8.5/8.8.5) id AAA00220; Mon, 26 May 1997 00:45:59 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199705252245.AAA00220@helbig.informatik.ba-stuttgart.de> Subject: Re: sio1: 64 events for device with no tp In-Reply-To: <19970525161640.02033@cola47.scsn.net> from "Donald J. Maddox" at "May 25, 97 04:16:40 pm" To: dmaddox@scsn.net Date: Mon, 26 May 1997 00:45:59 +0200 (MET DST) Cc: FreeBSD-current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > On Sun, May 25, 1997 at 09:51:22PM +0200, Wolfgang Helbig wrote: > > Hi, > > > > The above kernel message shows up during booting for both sio0 and sio1. > > Up to now its just annoying -- the messages are repeated once > > syslogd is started. > > > > This behaviour seems buggy to me. These messages were not > > by the release 1.164 sio driver. The kernel is pretty current, > > using release 1.169 of sio.c. (FreeBSD-current) > > > > Only the serial interface 0 is used on this system, connected to > > a mouse. It still works. > > > > Maybe there is some bug in sio.c to be fixed ? > > The following is a patch from phk that will stop the messages... If you > want to enable the COM_BIGFIFO stuff, set FLAGS=0x20000 in the sio lines in > your config file (COM_BIGFIFO doesn't work for my Motorola ModemSurfer Modem. > YMMV). [patch omitted ...] Thank you! The patch works fine for me. Question: Why isn't it committed? Wolfgang