linux-kernel - Re: [PATCH v2] of: address: Work around missing device

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]

Date:   Wed, 30 Sep 2020 18:23:21 +0100
From:   Marc Zyngier <maz@...nel.org>
To:     Niklas Söderlund <niklas.soderlund@...natech.se>
Cc:     devicetree@...r.kernel.org, linux-pci@...r.kernel.org,
        linux-rockchip@...ts.infradead.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        Rob Herring <robh@...nel.org>,
        Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
        Heiko Stuebner <heiko@...ech.de>,
        Frank Rowand <frowand.list@...il.com>,
        Shawn Lin <shawn.lin@...k-chips.com>,
        Jiaxun Yang <jiaxun.yang@...goat.com>,
        Rob Herring <robh+dt@...nel.org>,
        Bjorn Helgaas <bhelgaas@...gle.com>, kernel-team@...roid.com,
        samuel@...nne-riel.com
Subject: Re: [PATCH v2] of: address: Work around missing device_type property
 in pcie nodes

Hi Niklas,

[+ Samuel]

On 2020-09-30 17:27, Niklas Söderlund wrote:
> Hi Marc,
> 
> I'm afraid this commit breaks booting my rk3399 device.
> 
> I bisected the problem to this patch merged as [1]. I'm testing on a
> Scarlet device and I'm using the unmodified upstream
> rk3399-gru-scarlet-inx.dtb for my tests.
> 
> The problem I'm experience is a black screen after the bootloader and
> the device is none responsive over the network. I have no serial 
> console
> to this device so I'm afraid I can't tell you if there is anything
> useful on to aid debugging there.
> 
> If I try to test one commit earlier [2] the system boots as expected 
> and
> everything works as it did for me in v5.8 and earlier. I have worked
> little with this device and have no clue about what is really on the 
> PCI
> buss. But running from [2] I have this info about PCI if it's helpful,
> please ask if somethings missing.

Please see the thread at [1]. The problem was reported a few weeks back
by Samuel, and I was expecting Rob and Lorenzo to push a fix for this.

Rob, Lorenzo, any update on this?

         M.

[1] 
https://lore.kernel.org/linux-devicetree/20200829164920.7d28e01a@DUFFMAN/
-- 
Jazz is not dead. It just smells funny...