From owner-freebsd-hackers  Wed Aug 14 12:31:07 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id MAA21523
          for hackers-outgoing; Wed, 14 Aug 1996 12:31:07 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA21511
          for <freebsd-hackers@FreeBSD.ORG>; Wed, 14 Aug 1996 12:31:04 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id FAA01058; Thu, 15 Aug 1996 05:27:27 +1000
Date: Thu, 15 Aug 1996 05:27:27 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199608141927.FAA01058@godzilla.zeta.org.au>
To: freebsd-hackers@FreeBSD.ORG, j@uriah.heep.sax.de
Subject: Re: sio problems with 2.2-960801-SNAP
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>> Aug  8 11:52:22 plato /kernel.2.2: stray irq 4
>> Aug  8 11:52:41 plato last message repeated 3 times
>> Aug  8 11:53:55 plato /kernel.2.2: stray irq 4
>> Aug  8 11:53:55 plato /kernel.2.2: too many stray irq 4's; not logging any more
>> Aug  8 12:15:41 plato /kernel.2.2: stray irq 3

>Basically, there's something screwed with your interrupt
>configuration.  Stray irq's are not supposed to happen for a
>configured driver, they are generated by catch-all code inside
>the ISA bus controller driver, thus a strong indication that
>your IRQs never reach the sio driver.

The catch-all code delivers stray IRQs to IRQ7 (and maybe to
IRQ15).  `stray irq 4' simply means that an IRQ4 occurred
but no driver is attached to IRQ4.  I don't know how this can
happen.  If there is no driver attached to an IRQ, then that
IRQ is masked, except for the catch-all IRQ7.

Bruce