From owner-freebsd-stable Tue Jan 18 14:46:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from beholder.ods.org (ppp-047.m2-1.sub.ican.net [142.51.225.47]) by hub.freebsd.org (Postfix) with ESMTP id A72C7150DA for ; Tue, 18 Jan 2000 14:46:11 -0800 (PST) (envelope-from beholder@beholder.ods.org) Received: from beholder.ods.org (laptop [192.168.0.21]) by beholder.ods.org (8.9.3/8.9.3) with ESMTP id RAA05925; Tue, 18 Jan 2000 17:45:29 -0500 (EST) (envelope-from beholder@beholder.ods.org) Message-ID: <3884ED90.25FAA604@beholder.ods.org> Date: Tue, 18 Jan 2000 17:47:44 -0500 From: Pat Wendorf X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Phillip Salzman Cc: stable@FreeBSD.ORG Subject: Re: Stray IRQs References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Phillip Salzman wrote: > > 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? > I had that same problem, but it happened when I shutdown a Printer port (in my bios setup) for a very buggy motherboard. It happened because, even though I had shut it down, the IRQ was still firing (which confused the hell out of freebsd I guess). Sounds like you've got a flakey NIC on that machine, and you should probably get it replaced. -- ---------------------- Pat Wendorf beholder@unios.dhs.org ICQ: 1503733 --------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message