Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264173AbUD2MAq (ORCPT ); Thu, 29 Apr 2004 08:00:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264193AbUD2MAp (ORCPT ); Thu, 29 Apr 2004 08:00:45 -0400 Received: from mail.shareable.org ([81.29.64.88]:42624 "EHLO mail.shareable.org") by vger.kernel.org with ESMTP id S264173AbUD2MAo (ORCPT ); Thu, 29 Apr 2004 08:00:44 -0400 Date: Thu, 29 Apr 2004 13:00:17 +0100 From: Jamie Lokier To: "Maciej W. Rozycki" Cc: Ross Dickson , Jesse Allen , Len Brown , a.verweij@student.tudelft.nl, "Prakash K. Cheemplavam" , Craig Bradney , christian.kroener@tu-harburg.de, linux-kernel@vger.kernel.org, Daniel Drake , Ian Kumlien , Allen Martin Subject: Re: IO-APIC on nforce2 [PATCH] + [PATCH] for nmi_debug=1 + [PATCH] for idle=C1halt, 2.6.5 Message-ID: <20040429120017.GB7077@mail.shareable.org> References: <200404282133.34887.ross@datscreative.com.au> <20040428205938.GA1995@tesore.local> <200404292144.37479.ross@datscreative.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 756 Lines: 19 Maciej W. Rozycki wrote: > Not necessarily related to the PSU, but the noise may actually be the > reason of spurious timer interrupts. With most device interrupts, additional spurious ones don't cause any malfunction because the driver's handler checks whether the device actually has a condition pending. This is the basis of shared interrupts, of course. Is there any way we can check the timer itself to see whether an interrupt was caused by it, so that spurious timer interrupts are ignored? -- Jamie - 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/