linux-kernel - Re: next/master bisection: baseline.login on qemu

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: <CAL_JsqJ9fDXkVgcXTiO+NM9T7OKO+p43NGmJPRvvLi3-_Bd4dQ@mail.gmail.com>
Date:   Fri, 24 Sep 2021 15:05:27 -0500
From:   Rob Herring <robh@...nel.org>
To:     Guillaume Tucker <guillaume.tucker@...labora.com>
Cc:     Sudeep Holla <sudeep.holla@....com>,
        Linus Walleij <linus.walleij@...aro.org>,
        "kernelci-results@...ups.io" <kernelci-results@...ups.io>,
        devicetree@...r.kernel.org,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        Liviu Dudau <liviu.dudau@....com>,
        linux-kernel@...r.kernel.org,
        Lorenzo Pieralisi <lorenzo.pieralisi@....com>
Subject: Re: next/master bisection: baseline.login on qemu_arm-vexpress-a9

On Thu, Sep 23, 2021 at 12:28 PM Guillaume Tucker
<guillaume.tucker@...labora.com> wrote:
>
> Hi Rob,
>
> Please see the bisection report below about a boot failure on ARM
> Versatile Express.
>
> Reports aren't automatically sent to the public while we're
> trialing new bisection features on kernelci.org but this one
> looks valid.

Have you considered given you have the commit, if there's a Link tag,
sending this as a reply to the original patch? That would be a bit
easier to find IMO.

> Some more details can be found here, for Cortex A9:
>
>   https://linux.kernelci.org/test/case/id/614c36cf0c427f123799a2db/

I should have remembered there's a qemu model... Anyways, sending out
a fix in a moment.

The log here was empty. Any reason 'earlycon' is not set here? I also
noticed stdout-path is not set on many of the Arm Ltd boards. I'll
send a patch for that, too. You really shouldn't have to set the
console on the cmdline nowadays unless you want the non-default.

Rob