From owner-freebsd-current Thu Apr 4 11:32:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA22802 for current-outgoing; Thu, 4 Apr 1996 11:32:10 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA22757 for ; Thu, 4 Apr 1996 11:32:07 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id MAA17330; Thu, 4 Apr 1996 12:31:59 -0700 Date: Thu, 4 Apr 1996 12:31:59 -0700 From: Nate Williams Message-Id: <199604041931.MAA17330@rocky.sri.MT.net> To: root@deadline.snafu.de (Andreas S. Wetzel) Cc: nate@sri.MT.net (Nate Williams), jgreco@brasil.moneng.mei.com, current@freebsd.org Subject: Re: tty-level buffer overflows - what to do? In-Reply-To: References: <199604041914.MAA17253@rocky.sri.MT.net> 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? Yep. > The only cards I have installed in this machine are the following: > > IDE/FDC controller card (without any other ports etc) > > Multi I/O card with COM1 COM2 LPT(completely disabled including IRQ) and > Gameport (also disabled) I'll bet dollars to donuts that the 'disabling' of the card doesn't actually disable the generation of suprious interupts. I have found few cheap I/O boards that actually 'disable' interrupts. Most of them no longer assign them to an IRQ handler, but still generate them. Nate