Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263742AbUCXP2Y (ORCPT ); Wed, 24 Mar 2004 10:28:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263745AbUCXP2Y (ORCPT ); Wed, 24 Mar 2004 10:28:24 -0500 Received: from mail.shareable.org ([81.29.64.88]:56976 "EHLO mail.shareable.org") by vger.kernel.org with ESMTP id S263742AbUCXP2V (ORCPT ); Wed, 24 Mar 2004 10:28:21 -0500 Date: Wed, 24 Mar 2004 15:28:00 +0000 From: Jamie Lokier To: "Richard B. Johnson" Cc: Hans-Peter Jansen , Robert_Hentosh@Dell.com, Linux kernel Subject: Re: spurious 8259A interrupt Message-ID: <20040324152800.GA5758@mail.shareable.org> References: <6C07122052CB7749A391B01A4C66D31E014BEA49@ausx2kmps304.aus.amer.dell.com> <20040319130609.GE2650@mail.shareable.org> <200403211858.07445.hpj@urpla.net> 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: 738 Lines: 18 Richard B. Johnson wrote: > It isn't CPU-specific. It's motherboard glitch specific. If there > is ground-bounce on the motherboard or excessive induced > coupling, the CPU may occasionally get hit with a logic-level > that it "thinks" is an interrupt, even though no controller > actually generated it. That doesn't seem plausible on an otherwise reliable computer. Why would interrupt lines suffer ground-bounce logic glitches yet all the data, address and control lines be fine? -- 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/