Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264183AbTEaHKT (ORCPT ); Sat, 31 May 2003 03:10:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264184AbTEaHKT (ORCPT ); Sat, 31 May 2003 03:10:19 -0400 Received: from modemcable204.207-203-24.mtl.mc.videotron.ca ([24.203.207.204]:8832 "EHLO montezuma.mastecende.com") by vger.kernel.org with ESMTP id S264183AbTEaHKS (ORCPT ); Sat, 31 May 2003 03:10:18 -0400 Date: Sat, 31 May 2003 03:13:20 -0400 (EDT) From: Zwane Mwaikambo X-X-Sender: zwane@montezuma.mastecende.com To: Nicolas Mailhot cc: linux-kernel@vger.kernel.org Subject: RE: RFC Proposal to enable MSI support in Linux kernel In-Reply-To: <1054306504.7890.5.camel@ulysse.olympe.o2t> Message-ID: References: <1054306504.7890.5.camel@ulysse.olympe.o2t> 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 On Fri, 30 May 2003, Nicolas Mailhot wrote: > Hi, > > Before you say all's well in linux 2.5 edge/level APIC processing take > a look at: > > http://bugzilla.kernel.org/show_bug.cgi?id=10 > > (not that I know if it's actually closely related to this thread, but > for once there is an APIC guru gathering on linux-kernel...) It doesn't appear to be a edge/level trigger issue, i've posted a comment regarding the possible cause (lack of an MADT causes ACPI to make wrong decision with respect to interrupt controller type). There was a report a couple of weeks back with what appears to be the same symptoms. 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/