From owner-freebsd-current  Thu Apr  4 14:37:19 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA09950
          for current-outgoing; Thu, 4 Apr 1996 14:37:19 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA09942
          for <current@FreeBSD.org>; Thu, 4 Apr 1996 14:37:12 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.6.12/8.6.6) with SMTP id PAA13374; Thu, 4 Apr 1996 15:34:56 -0700
Message-Id: <199604042234.PAA13374@rover.village.org>
To: root@deadline.snafu.de (Andreas S. Wetzel)
Subject: Re: tty-level buffer overflows - what to do? 
Cc: nate@sri.MT.net (Nate Williams), jgreco@brasil.moneng.mei.com,
        current@FreeBSD.org
In-reply-to: Your message of Thu, 04 Apr 1996 21:27:26 +0200
Date: Thu, 04 Apr 1996 15:34:56 -0700
From: Warner Losh <imp@village.org>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

: That means the interrupt that happens is not guaranteed to be IRQ 7 but
: maybe any other unassigned interrupt?

We see these from time to time when we have both serial and ethernet
activity at the same time.  W edon't know if they are afrom the
ehtenret card or the serial modems.  We suspect the latter, but have
no way of proving it.  As far as we know, there is no disk I/o when we
see these all the time, but there is sometimes.

1.1R used to have more problems with the keyboard on my 486DX33
generating these interrupts, but 21.R and 2.0R didn't.

Warner