Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161293AbWKEPSf (ORCPT ); Sun, 5 Nov 2006 10:18:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161311AbWKEPSf (ORCPT ); Sun, 5 Nov 2006 10:18:35 -0500 Received: from ebiederm.dsl.xmission.com ([166.70.28.69]:20650 "EHLO ebiederm.dsl.xmission.com") by vger.kernel.org with ESMTP id S1161293AbWKEPSe (ORCPT ); Sun, 5 Nov 2006 10:18:34 -0500 From: ebiederm@xmission.com (Eric W. Biederman) To: Adrian Bunk Cc: Linux Kernel Mailing List , "Bryan O'Sullivan" Subject: Re: 2.6.19-rc4: known unfixed regressions (v3) References: <20061105064801.GV13381@stusta.de> Date: Sun, 05 Nov 2006 08:17:53 -0700 In-Reply-To: <20061105064801.GV13381@stusta.de> (Adrian Bunk's message of "Sun, 5 Nov 2006 07:48:01 +0100") Message-ID: User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux) 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: 1703 Lines: 39 Adrian Bunk writes: > This email lists some known regressions in 2.6.19-rc4 compared to 2.6.18 > that are not yet fixed in Linus' tree. > > If you find your name in the Cc header, you are either submitter of one > of the bugs, maintainer of an affectected subsystem or driver, a patch > of you caused a breakage or I'm considering you in any other way possibly > involved with one or more of these issues. > > Due to the huge amount of recipients, please trim the Cc when answering. > > > Subject : ipath driver MCEs system on load when HT chip present > References : http://bugzilla.kernel.org/show_bug.cgi?id=7455 > Submitter : Bryan O'Sullivan > Caused-By : Eric W. Biederman > Status : unknown Status in problem is being debugged. I have posted some infrastructure patches that should allow Bryan to fix his driver cleanly. I did not cause this. The ipath HTX card driver's irq handling has never been anything but a hack. It has never worked correctly even in the instances it worked. It only worked on i386 or x86_64 when CONFIG_PCI_MSI was enabled but did not use MSI. It was relying on the implementation detail that the architecture specific vector number was placed in the dev->irq. dev->irq is actually meaningless on this card as it doesn't have any ordinary pci interrupts. So while I am happy to take credit for flushing this bug out I did not introduce it. Eric - 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/