Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752064AbXBDEpO (ORCPT ); Sat, 3 Feb 2007 23:45:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752066AbXBDEpO (ORCPT ); Sat, 3 Feb 2007 23:45:14 -0500 Received: from ms-smtp-04.nyroc.rr.com ([24.24.2.58]:44137 "EHLO ms-smtp-04.nyroc.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752056AbXBDEpM (ORCPT ); Sat, 3 Feb 2007 23:45:12 -0500 Message-ID: <09ba01c74817$1ae12980$84163e05@kroptech.com> From: "Adam Kropelin" To: "Eric W. Biederman" Cc: "Auke Kok" , "Adrian Bunk" , "Linus Torvalds" , "Andrew Morton" , "Linux Kernel Mailing List" , , , "Allen Parker" , , , , References: <20070203004447.GJ3754@stusta.de> <45C42669.2010105@intel.com> <089b01c747be$0ca22620$84163e05@kroptech.com> <45C4F3F1.6060500@intel.com> <098001c747e9$d8931b60$84163e05@kroptech.com> Subject: Re: 2.6.20-rc7: known regressions (v2) (part 1) Date: Sat, 3 Feb 2007 23:44:07 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3028 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1151 Lines: 28 Eric W. Biederman wrote: > "Adam Kropelin" writes: > >>> Can I get the corresponding lspci -xxx output. I suspect the BIOS >>> did not program the hypertransport MSI mapping capabilities >>> correctly. All it has to do is set the enable but still, >>> occasionally BIOS writers miss the most amazing things. >> >> Here you go. This is from 2.6.20-rc7. > > Thanks. Conclusion. I could not find bit 16 (the enable bit) set in > any of your hypertransport msi mapping capabilities. > > So MSI interrupts won't work until someone enables your chipset > to transform them into hypertransport interrupts. Naive question... Can the pci layer (or e1000) detect that MSI is not enabled in the hardware and avoid using it in that case? With the number of MSI problems showing up it seems risky to assume it's usable on any given platform without some sort of sanity check. --Adam - 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/