From owner-freebsd-hackers  Thu Feb  6 01:14:09 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id BAA24277
          for hackers-outgoing; Thu, 6 Feb 1997 01:14:09 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA24268
          for <freebsd-hackers@freebsd.org>; Thu, 6 Feb 1997 01:14:05 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id UAA15588; Thu, 6 Feb 1997 20:06:47 +1100
Date: Thu, 6 Feb 1997 20:06:47 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702060906.UAA15588@godzilla.zeta.org.au>
To: alexis@ww.net, joerg_wunsch@uriah.heep.sax.de
Subject: Re: sio11 64 events for device without tp related problem?
Cc: freebsd-hackers@freebsd.org
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>>> two messages 'sio11 64 events for device without tp' is generated.
>
>	Well, it is master port for 8 ports multiport and no, it uses
>irq 5. Could you elaborate and explain what tp and entire message
>means?

It means that some sio events, probably modem status changes
(actually only one), were detected before the port was first opened.
This shouldn't happen.  Events on sio11 aren't checked for until the
end of the call to the device attach routine for sio11, and they should
not occur afterwards (until the port is opened) because the port is
fully initialized before it is attached.  There is probably a h/w or
s/w bug in the COM_MULTIPORT case.  This is probably harmless.

Bruce