Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263089AbUCSWGo (ORCPT ); Fri, 19 Mar 2004 17:06:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263098AbUCSWES (ORCPT ); Fri, 19 Mar 2004 17:04:18 -0500 Received: from mail.gmx.net ([213.165.64.20]:35776 "HELO mail.gmx.net") by vger.kernel.org with SMTP id S263089AbUCSWEI (ORCPT ); Fri, 19 Mar 2004 17:04:08 -0500 X-Authenticated: #20450766 Date: Fri, 19 Mar 2004 23:01:55 +0100 (CET) From: Guennadi Liakhovetski To: "Maciej W. Rozycki" cc: Robert_Hentosh@Dell.com, , Subject: RE: spurious 8259A interrupt In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 731 Lines: 21 On Fri, 19 Mar 2004, Maciej W. Rozycki wrote: > The best way to deal with spurious interrupts is to ack the interrupt at > the device ASAP in the handler, especially if you know that the response > is slow. I am getting those from the lAPIC timer interrupt (on a VIA KM133 Duron system). And the APIC timer interrupt IS acked (almost) immediately. So, I have a choice: no NMI watchdog or that uncomfortably increasing ERR: counter. Kernel 2.6.3. Guennadi --- Guennadi Liakhovetski - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/