From owner-freebsd-stable Wed Jan 19 22:10:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from evil.2y.net (port-3-192.adsl.one.net [216.2.0.192]) by hub.freebsd.org (Postfix) with ESMTP id C9BC115377; Wed, 19 Jan 2000 22:10:31 -0800 (PST) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id UAA71242; Tue, 18 Jan 2000 20:55:00 -0500 (EST) (envelope-from cokane) Date: Tue, 18 Jan 2000 20:55:00 -0500 From: Coleman Kane To: Mike Smith Cc: Phillip Salzman , stable@freebsd.org Subject: Re: Stray IRQs Message-ID: <20000118205500.A71226@evil.2y.net> References: <200001182307.PAA03097@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001182307.PAA03097@mass.cdrom.com>; from msmith@freebsd.org on Tue, Jan 18, 2000 at 06:04:37PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG IRQ 15 is typically an interrupt for the second IDE controller. You may be using SCSI and have disabled the wdc on a mobo that doesn't like that too much. The network traffic blockage could be attributed to the PIC not being reset before the requests were handled. IRQs 8-15 are handled by IRQ 2, mid you, so they are higher priority if your netcard is on PIC1. --cokane Mike Smith had the audacity to say: > > A mission-critical production machine of ours seems to be > > having issues with stray irqs. > > > > This is in the dmesg: > > ----------------------------- > > stray irq 15 > > stray irq 15 > > stray irq 15 > > stray irq 15 > > stray irq 15 > > too many stray irq 15's; not logging any more > > ---------------------------- > > > > It seems as if the ethernet traffic stops for about a minute > > when it posts that message. > > > > I've searched back in the mailing lists to find that this > > may be caused by the BIOS grabbing the IRQ -- and was just > > wondering if anyone else has seen this problem lately? > > No; this is typically caused by having hardware in the system that's > generating interrupts but isn't handled by a driver. It may be > symptomatic of faulty hardware or a system misconfiguration. > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message