From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756493AbaIDGK3 (ORCPT ); Thu, 4 Sep 2014 02:10:29 -0400 Received: from services.gouders.net ([141.101.32.176]:43083 "EHLO services.gouders.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754582AbaIDGK2 (ORCPT ); Thu, 4 Sep 2014 02:10:28 -0400 From: Dirk Gouders To: Andreas Noever Cc: Bjorn Helgaas , Linux Kernel Subject: Re: [BUG] Bisected Problem with LSI PCI FC Adapter In-Reply-To: (Andreas Noever's message of "Wed, 3 Sep 2014 17:54:17 +0200") References: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) Date: Thu, 04 Sep 2014 08:09:26 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Andreas Noever writes: > On Wed, Sep 3, 2014 at 2:47 PM, Dirk Gouders wrote: >> Andreas Noever writes: >> >>> On Wed, Sep 3, 2014 at 12:57 PM, Dirk Gouders wrote: >>>> On a Tyan VX50 (B4985) I ran into problems when updating the kernel: the >>>> PCI FC Adapter is no longer recognized. >>> >>> Can you provide the output of lspci -vvv and the output of dmesg from >>> a working boot? Which card is the one that is not recognized? >> >> Sure, the card that disappeared is: >> >> 0a:00.0 Fibre Channel: LSI Logic / Symbios Logic FC949ES Fibre Channel Adapter (rev 02) > > As far as I can tell the following is happening: > The root bus resource window (advertised by the bios?) is to small: > pci_bus 0000:00: root bus resource [bus 00-07] > Previously we didn't really care. There is a resource conflict but we > ignored it: > pci_bus 0000:0a: busn_res: can not insert [bus 0a] under [bus 00-07] > (conflicts with (null) [bus 00-07]) > With the patch we mark the bridge as broken and reassign the bus to 06: > pci 0000:00:0e.0: bridge configuration invalid ([bus 0a-0a]), reconfiguring > pci 0000:00:0e.0: PCI bridge to [bus 06-07] > pci 0000:00:0e.0: bridge window [io 0x3000-0x3fff] > pci 0000:00:0e.0: bridge window [mem 0xd4200000-0xd42fffff] > pci_bus 0000:06: busn_res: [bus 06-07] end is updated to 06 > > We still scan for children but nothing shows up ("PCI bridge to" is > from pci_scan_child_bus -> pcibios_fixup_bus -> pci_read_bridge_base, > after pci_scan_slot). I have no idea why the device does not respond. Please excuse my ignorance but a naive question: __pci_setup_bridge() outputs the same text (exept for an additional string that is empty in this case) and I wonder how to say where it came from. Anyway, please let me know if it would help that I activate more verbose messages with the working or problematic kernel. I will then risk to annoy the users with one more short downtime. Dirk