Date: Thu, 4 Apr 1996 12:31:59 -0700 From: Nate Williams <nate@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? Message-ID: <199604041931.MAA17330@rocky.sri.MT.net> In-Reply-To: <m0u4ugp-000A0mC@deadline.snafu.de> References: <199604041914.MAA17253@rocky.sri.MT.net> <m0u4ugp-000A0mC@deadline.snafu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604041931.MAA17330>