Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 8 Jan 2002 07:27:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 8 Jan 2002 07:27:13 -0500 Received: from weta.f00f.org ([203.167.249.89]:62661 "EHLO weta.f00f.org") by vger.kernel.org with ESMTP id ; Tue, 8 Jan 2002 07:27:02 -0500 Date: Wed, 9 Jan 2002 01:30:05 +1300 From: Chris Wedgwood To: "Maciej W. Rozycki" Cc: Petr Vandrovec , Alan Cox , swsnyder@home.com, Linux Kernel Mailing List Subject: Re: "APIC error on CPUx" - what does this mean? Message-ID: <20020108123005.GA29924@weta.f00f.org> In-Reply-To:

Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.25i X-No-Archive: Yes Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 08, 2002 at 01:12:04PM +0100, Maciej W. Rozycki wrote: A possible reason is the 8259A in the chipset deasserts its INT output late enough for the Athlon CPU's local APIC to register another ExtINTA interrupt sometimes, possibly under specific circumstances. Actully... we could potentially measure this... after an interrupt it serviced (or before, or both) we could store the interrupt source globally and the cycle counter... when a suprrious interrupt is received check the last interrupt and how long ago it was and then start looking for a pattern... --cw - 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/