From owner-freebsd-current  Thu Sep 24 15:08:36 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA25866
          for freebsd-current-outgoing; Thu, 24 Sep 1998 15:08:36 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25851;
          Thu, 24 Sep 1998 15:08:27 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id IAA32108;
	Fri, 25 Sep 1998 08:08:21 +1000
Date: Fri, 25 Sep 1998 08:08:21 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199809242208.IAA32108@godzilla.zeta.org.au>
To: gibbs@plutotech.com, mike@smith.net.au
Subject: Re: options DPT_LOST_IRQ
Cc: bde@FreeBSD.ORG, current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> If it stops asserting the interrupt, we should get a stray interrupt
>> reported when we go to clear the pending mask.  Is this what is happening?
>
>I don't actually think we should; the stray interrupt feature occurs 
>when an edge is seen on an interrupt line, but when the latch fires 
>(one or two clocks later?) there is nothing there to latch.  This is 
>the way the 8259 works; PCI and APIC interrupt behaviour is still largely
>a mystery to me.

To me too.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message