lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMxnaaUqTMf1uEQUqrAGjym8ZrQaBf2QbE4Jqxh2t6a2JgJkOQ@mail.gmail.com>
Date:	Wed, 3 Sep 2014 17:54:17 +0200
From:	Andreas Noever <andreas.noever@...il.com>
To:	Dirk Gouders <dirk@...ders.net>
Cc:	Bjorn Helgaas <bhelgaas@...gle.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [BUG] Bisected Problem with LSI PCI FC Adapter

On Wed, Sep 3, 2014 at 2:47 PM, Dirk Gouders <dirk@...ders.net> wrote:
> Andreas Noever <andreas.noever@...il.com> writes:
>
>> On Wed, Sep 3, 2014 at 12:57 PM, Dirk Gouders <dirk@...ders.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ