Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262905AbUDUO2L (ORCPT ); Wed, 21 Apr 2004 10:28:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262953AbUDUO2L (ORCPT ); Wed, 21 Apr 2004 10:28:11 -0400 Received: from jurand.ds.pg.gda.pl ([153.19.208.2]:27569 "EHLO jurand.ds.pg.gda.pl") by vger.kernel.org with ESMTP id S262905AbUDUO2H (ORCPT ); Wed, 21 Apr 2004 10:28:07 -0400 Date: Wed, 21 Apr 2004 16:28:05 +0200 (CEST) From: "Maciej W. Rozycki" To: Chris Stromsoe Cc: Marcelo Tosatti , linux-kernel@vger.kernel.org, mikpe@csd.uu.se Subject: Re: apic errors and looping with 2.4, none with 2.2 (supermicro/serverworks LE chipset) In-Reply-To: Message-ID: References: <20040324212759.GD6572@logos.cnet> Organization: Technical University of Gdansk 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: 1256 Lines: 31 On Sat, 17 Apr 2004, Chris Stromsoe wrote: > When there are APIC errors logged, is it generally a hardware issue? I Yep. > have a few other boxes that log errors unless they're booted with noapic > (but with noapic, they run fine). Is the power supply generally the first > thing to check when trying to track down the source of an APIC related Experience shows that's a good thing for a start. Of course the reason may actually be a bad motherboard design and replacing the power supply wouldn't help then. > hardware problem? Pointers to URLs or other forms of documentation > appreciated. Well, just mailing list archives, unless, of course, you are interested in the exact details of APIC operation. In that case, http://developer.intel.com/ would be the right place to look for documentation. -- + Maciej W. Rozycki, Technical University of Gdansk, Poland + +--------------------------------------------------------------+ + e-mail: macro@ds2.pg.gda.pl, PGP key available + - 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/