Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 11 Mar 2002 19:37:40 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 11 Mar 2002 19:37:31 -0500 Received: from e31.co.us.ibm.com ([32.97.110.129]:22459 "EHLO e31.co.us.ibm.com") by vger.kernel.org with ESMTP id ; Mon, 11 Mar 2002 19:37:16 -0500 Date: Mon, 11 Mar 2002 16:36:57 -0800 From: "Martin J. Bligh" To: Mark Hahn , Adam K Kirchhoff cc: linux-kernel Subject: Re: SMP & APIC problem. Message-ID: <132630000.1015893417@flay> In-Reply-To: In-Reply-To: X-Mailer: Mulberry/2.1.2 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org >> My second question: Is there any chance of getting this working with >> APIC, if not in 2.4.* maybe in a future release? > > given that it's a hardware problem, no. but it *would* be cool > if the kernel noticed repeated APIC warnings and just turned > off apic use (as if you had booted with noapic). I'm guessing > this would be ugly, since APIC setup is probably discarded after boot... There were some patches floating around to do exactly this (don't remember where, sorry ;-) ) There's also an esr_disable flag variable I put in a while back when doing bringup of NUMA-Q to smack the ESR into submission. You might want to try tweaking that on in smp.h. It's not like we actually do anything with the errors anyway. (all assuming my mind isn't faulty, and this is actually the same thing). The read / write protocol for ESR is really .... wierd, and it seems to need smacking multiple times to accept a write. M. - 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/