From owner-freebsd-questions  Thu Jan  4 08:23:32 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA14094
          for questions-outgoing; Thu, 4 Jan 1996 08:23:32 -0800 (PST)
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA14082
          for <questions@freebsd.org>; Thu, 4 Jan 1996 08:23:26 -0800 (PST)
Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id IAA03438; Thu, 4 Jan 1996 08:23:22 -0800
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.7.3/8.6.5) with SMTP id IAA02427; Thu, 4 Jan 1996 08:23:25 -0800 (PST)
Message-Id: <199601041623.IAA02427@corbin.Root.COM>
To: olsenc@ichips.intel.com
cc: jhewitt@uw-isdl.ee.washington.edu, jhp@cypress.com, questions@freebsd.org
Subject: Re: /kernel: stray irq 15 
In-reply-to: Your message of "Thu, 04 Jan 96 08:13:05 PST."
             <9601041613.AA25307@dtt034.intel.com> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Thu, 04 Jan 1996 08:23:16 -0800
Sender: owner-questions@freebsd.org
Precedence: bulk

>We've been having some really strange problems with our local HD:
>
>Jan  4 03:04:21 smokey /kernel: stray irq 15
>Jan  4 03:04:25 smokey /kernel: wd0: interrupt timeout:
>Jan  4 03:04:25 smokey /kernel: wd0: status 7e<rdy,wrtflt,seekdone,drq,ecc_cor,index> error 0
>Jan  4 03:05:25 smokey /kernel: wd0: interrupt timeout:
>Jan  4 03:05:25 smokey /kernel: wd0: status 7e<rdy,wrtflt,seekdone,drq,ecc_cor,index> error 1<no_dam>
>
>Lately, this has led to the eventual crashing of our FreeBSD box.  It 
>started somewhere in 2.0.5, we weren't sure what was going on, and now
>we're at 2.1 because 2.0.5 got trashed.
>
>Our hardware guy found a funky sound interface enabled in the BIOS on
>this Professional/GX workstation, and disabled it thinking it was the 
>culprit (IRQ 15).  We also had EOI enabled in the kernel before, and
>we've disabled that as well.
>
>I'm running out of ideers...

   This looks like you might have an interrupt conflict on irq 14. It
appears that you also have something on irq 15 that occasionally generates
an interrupt. In any case, the problem looks very much to be hardware related.
I suggest a careful examination of just what is in the machine and perhaps
pull out things that aren't being used.

-DG

David Greenman
Core Team/Principal Architect, The FreeBSD Project