From owner-freebsd-hackers Fri Jul 7 12:58:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 8743837BE85 for ; Fri, 7 Jul 2000 12:58:46 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id PAA08667; Fri, 7 Jul 2000 15:58:16 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Fri, 7 Jul 2000 15:58:16 -0400 (EDT) From: Adam To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: stray interrupts in 4.0 In-Reply-To: <200007061634.MAA16071@etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Jul 2000, Dennis wrote: >>> >> We're seeing lots of "stray" interrupts in 4.0 while running 3.4 on the >>> >> same hardware reports nothing. The interrupt its complaining about is >IRQ7 >>> >> even though parallel port is disabled and no other device. It happens on >>> >> more than 1 MB. >[snip] > >> >>Generally this message indicates that you have hardware in the system >>that is not signalling interrupts correctly. > >great, so intel doesnt know how to make MBs with their own parts...so how >can the message be turned off. Its using more resources printing the >message thsn the "stray interrupts" themselves. > >DB If you *have* an lpt controller and dont need the IRQ you could turn it on and enable the lpt driver in the kernel, that usually seems to take care of it on systems I had this message on. For this reason I usually leave lpt stuff enabled on systems even I'm unlikely to need the parallel port.. The other obvious alternative is to grep for it in the source and comment the printf. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message