Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 17 Oct 2002 00:57:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 17 Oct 2002 00:57:36 -0400 Received: from modemcable061.219-201-24.mtl.mc.videotron.ca ([24.201.219.61]:392 "EHLO montezuma.mastecende.com") by vger.kernel.org with ESMTP id ; Thu, 17 Oct 2002 00:57:35 -0400 Date: Thu, 17 Oct 2002 00:49:56 -0400 (EDT) From: Zwane Mwaikambo X-X-Sender: zwane@montezuma.mastecende.com To: Doug Ledford cc: linux-kernel@vger.kernel.org, Ingo Molnar , Subject: Re: 2.5.43 IO-APIC bug and spinlock deadlock In-Reply-To: <20021017033302.GP8159@redhat.com> Message-ID: 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: 1244 Lines: 28 On Wed, 16 Oct 2002, Doug Ledford wrote: > IO-APIC bug: regular kernel, UP, no IO-APIC or APIC on UP enabled, compile > fails (does *everyone* run SMP or at least UP + APIC now?) > > spinlock deadlock: run an smp kernel on a up machine. On mine here all I > have to do is try to boot to multiuser mode, it won't make it through the > startup scripts before it locks up by trying to reenter common_interrupt > on the only CPU. Seems like an SMP kernel on UP hardware doesn't disable > interrupts properly maybe? I get task lists via alt-sysreq when the > machine should be hardlocked I think. Anyway, this is what has been > tricking me into thinking I had an IDE problem. IDE is innocent, it's the > core interrupt handling code. Hmm i'm running an SMP kernel on a UP (only Local-APIC present) and the machine is currently running X. I've gotten an SMP kernel on a UP box without any APICs to also go multiuser too (currently 30 minutes uptime). Zwane -- function.linuxpower.ca - 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/