From owner-freebsd-current Thu Sep 24 13:44:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10145 for freebsd-current-outgoing; Thu, 24 Sep 1998 13:44:45 -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 NAA10107; Thu, 24 Sep 1998 13:44:33 -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 OAA08682; Thu, 24 Sep 1998 14:44:19 -0600 (MDT) Message-Id: <199809242044.OAA08682@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:43:16 PDT." <199809242043.NAA00705@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Sep 1998 14:37:47 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The problem seems to be that the DPT "stops asserting" the interrupt, >going by what Eivind said. I presume we're talking about a PCI device >here, right? 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? If so, then the problem is broken hardware. I would expect this problem to show up on non-SMP systems too. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message