From owner-freebsd-current Thu Apr 4 11:14:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA21375 for current-outgoing; Thu, 4 Apr 1996 11:14:19 -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 LAA21368 for ; Thu, 4 Apr 1996 11:14:15 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id MAA17253; Thu, 4 Apr 1996 12:14:09 -0700 Date: Thu, 4 Apr 1996 12:14:09 -0700 From: Nate Williams Message-Id: <199604041914.MAA17253@rocky.sri.MT.net> To: root@deadline.snafu.de (Andreas S. Wetzel) Cc: jgreco@brasil.moneng.mei.com (Joe Greco), current@freebsd.org Subject: Re: tty-level buffer overflows - what to do? In-Reply-To: References: <199604041821.MAA01616@brasil.moneng.mei.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > But another problem is still going on on that machine. During boot there > are several occurences of "stray irq 7" messages until syslog says it would > not log them anymore. I have no idea where this stray irq's should happen. > Physically there is no adaptor card installed which could ever generate a > IRQ 7 ? Possible that this has to do with the other thing? This is a pretty good indication that something is mis-confugred. IRQ 7 is the 'junk' interrupt, which means it gets all of the interrupts not otherwise assigned to a particular piece of hardware. Something is generating interrupts on your system bogusly and you need to find out what. Nate