From owner-freebsd-current  Sun May 25 12:52:12 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id MAA06257
          for current-outgoing; Sun, 25 May 1997 12:52:12 -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 MAA06246
          for <FreeBSD-current@FreeBSD.org>; Sun, 25 May 1997 12:52:05 -0700 (PDT)
Received: (from helbig@localhost)
	by helbig.informatik.ba-stuttgart.de (8.8.5/8.8.5) id VAA00443
	for FreeBSD-current@FreeBSD.org; Sun, 25 May 1997 21:51:22 +0200 (MET DST)
From: Wolfgang Helbig <helbig@MX.BA-Stuttgart.De>
Message-Id: <199705251951.VAA00443@helbig.informatik.ba-stuttgart.de>
Subject: sio1: 64 events for device with no tp
To: FreeBSD-current@FreeBSD.org
Date: Sun, 25 May 1997 21:51:22 +0200 (MET DST)
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

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 ?


Wolfgang