linux-kernel - Re: AArch64 boot failure on Hikey960 on latest master after "arm64: insn: Don't fallback on nosync path for general insn patching"

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] [day] [month] [year] [list]

Message-ID: <CALAqxLUZiSyi0f365B-QRTT1gkWq9RP-4n2950NcF0w9oSXYEg@mail.gmail.com>
Date:   Thu, 16 Aug 2018 11:47:47 -0700
From:   John Stultz <john.stultz@...aro.org>
To:     Tuomas Tynkkynen <tuomas.tynkkynen@....fi>
Cc:     Will Deacon <will.deacon@....com>,
        Catalin Marinas <catalin.marinas@....com>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        lkml <linux-kernel@...r.kernel.org>
Subject: Re: AArch64 boot failure on Hikey960 on latest master after "arm64:
 insn: Don't fallback on nosync path for general insn patching"

On Thu, Aug 16, 2018 at 11:37 AM, Tuomas Tynkkynen
<tuomas.tynkkynen@....fi> wrote:
> Hi,
>
> On 08/16/2018 08:57 PM, John Stultz wrote:
>>
>> On Thu, Aug 16, 2018 at 3:22 AM, Will Deacon <will.deacon@....com> wrote:
>>>
>>> Hi Tuomas, [+John]
>
> ...
>>>
>>>
>>> Out of interest -- do you know if Hikey960 is used by any boot-testing
>>> farms? The patch above has been in linux-next for ages, but we didn't see
>>> any complaints until it hit mainline :(
>>
>>
>> Unfortunately not yet. HiKey960 upstreaming is ongoing, and the UFS
>> support patches should land in the 4.19 merge window.
>> After which, it will enable more mainline testing as folks won't have
>> to carry patches just to get the system to boot.
>>
>
> A microSD rootfs gets me a working system on e.g. v4.17... except that
> even there the system hangs if I don't have 'clk_ignore_unused' on
> the kernel command line. I wonder if this is a known problem?

Oh, good point. I'm usually focusing on AOSP, so I've not tried
booting from the uSD slot.

As for the  clk_ignore_unused, I've not seen it, but I'm usually
testing with a much larger patch stack targeting AOSP (only
occasionally trying with a smaller set to validate patches being
prepped for upstream).  So if you want to file a bug, please do so
here: https://bugs.96boards.org/

Appreciate your testing! Please do feel free to reach out/cc me if you
run into other issues.

thanks
-john