From owner-freebsd-current Thu Sep 24 13:53:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12198 for freebsd-current-outgoing; Thu, 24 Sep 1998 13:53:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12159; Thu, 24 Sep 1998 13:53:22 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id OAA09297; Thu, 24 Sep 1998 14:53:07 -0600 (MDT) Message-Id: <199809242053.OAA09297@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: "Justin T. Gibbs" , bde@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: options DPT_LOST_IRQ In-reply-to: Your message of "Thu, 24 Sep 1998 13:54:23 PDT." <199809242054.NAA00826@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Sep 1998 14:46:36 -0600 From: "Justin T. Gibbs" 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. I don't have my "ISA Architecture" book here, but my understanding was that the stray was detected during the transition from pending to in-service as initiated by the CPU and not based on an "internal to the PIC" event. I don't know anything about APICs. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message