public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dirk Gouders <dirk@gouders.net>
To: Andreas Noever <andreas.noever@gmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] Bisected Problem with LSI PCI FC Adapter
Date: Thu, 04 Sep 2014 08:09:26 +0200	[thread overview]
Message-ID: <ghmwafvrvt.fsf@quad.gouders.net> (raw)
In-Reply-To: <CAMxnaaUqTMf1uEQUqrAGjym8ZrQaBf2QbE4Jqxh2t6a2JgJkOQ@mail.gmail.com> (Andreas Noever's message of "Wed, 3 Sep 2014 17:54:17 +0200")

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

  reply	other threads:[~2014-09-04  6:10 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-03 10:57 [BUG] Bisected Problem with LSI PCI FC Adapter Dirk Gouders
2014-09-03 12:28 ` Andreas Noever
2014-09-03 12:47   ` Dirk Gouders
2014-09-03 15:54     ` Andreas Noever
2014-09-04  6:09       ` Dirk Gouders [this message]
2014-09-11 13:43       ` Dirk Gouders
2014-09-11 17:30         ` Bjorn Helgaas
2014-09-11 19:26           ` Yinghai Lu
2014-09-11 20:33             ` Dirk Gouders
2014-09-11 20:42               ` Bjorn Helgaas
2014-09-11 21:24                 ` Dirk Gouders
2014-09-11 22:51                   ` Bjorn Helgaas
2014-09-11 23:50                     ` Dirk Gouders
2014-09-12 11:11                       ` Dirk Gouders
2014-09-12 20:05                         ` Dirk Gouders
2014-09-12 20:37                           ` Andreas Noever
2014-09-12 20:38                           ` Bjorn Helgaas
2014-09-12 20:39                           ` Yinghai Lu
2014-09-12 20:54                             ` Dirk Gouders
2014-09-12 21:49                               ` Yinghai Lu
2014-09-12 22:05                                 ` Dirk Gouders
2014-09-12 23:09                                   ` Yinghai Lu
2014-09-13  0:11                                     ` Dirk Gouders
2014-09-13  1:59                                       ` Yinghai Lu
2014-09-13  4:07                                         ` Bjorn Helgaas
2014-09-13  9:30                                           ` Dirk Gouders
2014-09-13 19:41                                             ` Dirk Gouders
2014-09-14 10:42                                               ` Andreas Noever
2014-09-14 10:44                                               ` Andreas Noever
2014-09-14 11:40                                                 ` Dirk Gouders
2014-09-14 13:16                                                   ` Andreas Noever
2014-09-14 14:24                                                     ` Dirk Gouders
2014-09-19 18:39                                               ` Bjorn Helgaas
2014-09-20 18:41                                                 ` Dirk Gouders
2014-09-22 14:25                                                   ` Bjorn Helgaas
2014-09-22 14:53                                                     ` Andreas Noever
2014-09-22 15:23                                                       ` Bjorn Helgaas
2014-09-19 17:12                                           ` Bjorn Helgaas
2014-09-19 15:03                                         ` Dirk Gouders
2014-09-19 18:21                                           ` Dirk Gouders
2014-09-11 20:35             ` Dirk Gouders
2014-09-11 20:42             ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ghmwafvrvt.fsf@quad.gouders.net \
    --to=dirk@gouders.net \
    --cc=andreas.noever@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox