From owner-freebsd-stable Tue Jan 18 15: 1:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 4464214CF1 for ; Tue, 18 Jan 2000 15:01:31 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA03097; Tue, 18 Jan 2000 15:07:08 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001182307.PAA03097@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Phillip Salzman Cc: stable@freebsd.org Subject: Re: Stray IRQs In-reply-to: Your message of "Tue, 18 Jan 2000 15:42:12 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Jan 2000 15:07:08 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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