From owner-freebsd-questions Mon Sep 1 23:47:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA20335 for questions-outgoing; Mon, 1 Sep 1997 23:47:44 -0700 (PDT) Received: from gdi.uoregon.edu (cisco-ts15-line15.uoregon.edu [128.223.150.198]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA20327 for ; Mon, 1 Sep 1997 23:47:38 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id XAA03306; Mon, 1 Sep 1997 23:47:22 -0700 (PDT) Date: Mon, 1 Sep 1997 23:47:21 -0700 (PDT) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: Hugh Blandford cc: questions@FreeBSD.ORG Subject: Re: Stray IRQ 7 messages In-Reply-To: <3.0.1.32.19970901155604.00739ca0@mail.island.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 1 Sep 1997, Hugh Blandford wrote: > Hi all, > > I've received some messages from my 2.2.2 system that there have been some > stray IRQ7s generated. I have disabled the parallel port in the BIOS and > do not have the lpr daemon running. There must be some software that is > generating this IRQ and I would appreciate any suggestions for tracking > this down. IRQ 7 is the system ``junk IRQ.'' Never put anything IRQ-sensitive there. I have a ASUS motherboard that generates them when the serial port is closed; I just ignore them, and the kernel will too eventually. So, to answer the question, it's normal on some systems, and apparently yours is one of them. It caused me grief with a QuickCam attached, which would cause the system to panic when I closed my X session. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major Spam routed to /dev/null by Procmail | Death to Cyberpromo