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: <20160929142424.GB14309@csclub.uwaterloo.ca>
Date:   Thu, 29 Sep 2016 10:24:24 -0400
From:   lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To:     Steve Kenton <skenton@...edu>
Cc:     linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
        Bjorn Helgaas <bhelgaas@...gle.com>,
        yinghai Lu <yinghai@...nel.org>,
        Blackmagic Developer Support <developer@...ckmagicdesign.com>
Subject: Re: lspci not showing motherboard ethernet controller after PCIe
 card firmware update change from 32-bit to 64-bit BAR

On Wed, Sep 28, 2016 at 09:05:44AM -0500, Steve Kenton wrote:
> I decided to experiment with /sys/bus/pci and the BIOS settings to try
> and understand things better.
> 
> The BIOS has a settings to enable/disable the on-board LAN. When the
> Blackmagic card firmware is upgraded
> bus[03] and hence the on-board LAN disappears, but the apparently unused
> bus[02] is still visible and
> the BIOS setting is still enabled. When the BIOS LAN settings is
> disabled busses[02][03] and the on-board
> LAN disappear. In both cases, the "disappeared" resources are not
> restored by echo to /sys/.../rescan
> 
> Why? What can the BIOS be doing to the chipset/busses[02][03] to make
> them invisible to /sys manipulation?

It can activate the reset line to the network chip making it never able
to respond to anything.  Or it could even power it off.

And PCIe is point to point, so they are not really busses anymore.
So at least turning off the network chip means no link on that point to
point PCIe link and hence no "bus" there.

> There is apparently something I do not understand about the H81 chipset
> PCIe configuration. I have
> been reading the Intel Series 8 / Series C220 Chipset documentation but
> so far have come up empty.
> 
> Anybody have cluebat for me?

I wish.

-- 
Len Sorensen

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ