Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757762Ab2K0BLM (ORCPT ); Mon, 26 Nov 2012 20:11:12 -0500 Received: from mail-ie0-f174.google.com ([209.85.223.174]:43197 "EHLO mail-ie0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757676Ab2K0BLK (ORCPT ); Mon, 26 Nov 2012 20:11:10 -0500 MIME-Version: 1.0 In-Reply-To: References: <097501cdca7b$7e303890$7a90a9b0$@lucidpixels.com> <20121126224245.248f0901@neptune.home> Date: Mon, 26 Nov 2012 17:11:09 -0800 Message-ID: Subject: Re: Supermicro X9SRL-F - channel enumeration error & ACPI/firmware bug question From: Dan Williams To: Bjorn Helgaas Cc: =?ISO-8859-1?Q?Bruno_Pr=E9mont?= , Justin Piszcz , support@supermicro.com, linux-kernel@vger.kernel.org, Dan Williams , "dave.jiang" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 985 Lines: 22 On Mon, Nov 26, 2012 at 4:56 PM, Bjorn Helgaas wrote: > The "channel error register unreachable" message indicates that > pci_read_config_dword() failed. The register in question > (IOAT_PCI_CHANERR_INT_OFFSET) is at 0x180, so possibly we don't have > PCI config accessors for the extended config space (0x100-0xfff). A > complete dmesg log should show that. Yes, this happens when extended pci configuration space is not reachable. Although the need to access this register has been found to no longer be needed. So, it appears this patch [1] from Dave should be modified to just stop touching that register altogether and then go to -stable. -- Dan [1]: http://marc.info/?l=linux-kernel&m=135310841032707&w=2 -- 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/