lkml.org 
[lkml]   [2014]   [Sep]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: [BUG] Bisected Problem with LSI PCI FC Adapter
    Date
    Andreas Noever <andreas.noever@gmail.com> writes:

    > On Wed, Sep 3, 2014 at 2:47 PM, Dirk Gouders <dirk@gouders.net> wrote:
    >> Andreas Noever <andreas.noever@gmail.com> writes:
    >>
    >>> On Wed, Sep 3, 2014 at 12:57 PM, Dirk Gouders <dirk@gouders.net> 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


    \
     
     \ /
      Last update: 2014-09-04 08:41    [W:3.041 / U:0.044 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site