LKFT detected arm64 boot regression on today's Linux next-20221121 tag.
The Kernel boot log did not show anything on the serial console.
Anders bisected this problem and found the subject commit is the
first bad commit.
# first bad commit: [9ed2b4616d4e846ece2a04cb5007ce1d1bd9e3f3]
arm64/mm: Drop redundant BUG_ON(!pgtable_alloc)
Later it was found this lore link which was already reported [1].
ref:
[1] https://lore.kernel.org/all/Y3pS5fdZ3MdLZ00t@dev-arch.thelio-3990X/
--
Linaro LKFT
https://lkft.linaro.org
On Mon, 21 Nov 2022 at 08:28, Naresh Kamboju <naresh.kamboju(a)linaro.org> wrote:
>
> Hi Dave,
>
> On Fri, 18 Nov 2022 at 05:24, Dave Hansen <dave.hansen(a)intel.com> wrote:
> >
> > On 11/17/22 15:23, Marco Elver wrote:
> > > Yes - it's the 'level != PG_LEVEL_4K'.
> >
> > That plus the bisect made it pretty easy to find, thanks for the effort!
> >
> > Could you double-check that the attached patch fixes it? It seemed to
> > for me.
>
> I have applied the attached patch on Linux next 20221118 and tested [1].
> The reported issue has been fixed now.
>
> Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org>
> Tested-by: Linux Kernel Functional Testing <lkft(a)linaro.org>
> Tested-by: Naresh Kamboju <naresh.kamboju(a)linaro.org>
>
> OTOH,
> I request you to walk through the boot and test log [1] (new see few failures).
> not ok 7 - test_double_free
> not ok 9 - test_invalid_addr_free
> not ok 11 - test_corruption
> not ok 18 - test_kmalloc_aligned_oob_write
> # kfence: pass:19 fail:4 skip:2 total:25
> # Totals: pass:19 fail:4 skip:2 total:25
> not ok 6 - kfence
Fixed by https://lkml.kernel.org/r/20221118152216.3914899-1-elver@google.com
kselftest running on LAVA infrastures provides test results parser
from test-definitions repository.
which is getting "Bad test result:".
I have noticed this on kernelci [1] and LKFT LAVA instances [2].
We need to investigate and change parse_output [3] inside test-definitions.
Report-by: Linux Kernel Functional Testing <lkft(a)linaro.org>
Test results parser showing “Bad test results: “,
Received signal: <TESTCASE> TEST_CASE_ID=arm64.sve-ptrace.SVE RESULT=FPSIMD
Bad test result: FPSIMD
<LAVA_SIGNAL_TESTCASE TEST_CASE_ID=arm64.sve-ptrace.SVE RESULT=FPSIMD>
Received signal: <TESTCASE> TEST_CASE_ID=arm64.sve-ptrace.SVE
RESULT=get_fpsimd()
Bad test result: get_fpsimd()
<LAVA_SIGNAL_TESTCASE TEST_CASE_ID=arm64.sve-ptrace.SVE RESULT=get_fpsimd()>
Received signal: <TESTCASE> TEST_CASE_ID=arm64.sve-ptrace.SVE
RESULT=SVE_PT_VL_INHERIT
Bad test result: SVE_PT_VL_INHERIT
<LAVA_SIGNAL_TESTCASE TEST_CASE_ID=arm64.sve-ptrace.SVE
RESULT=SVE_PT_VL_INHERIT>
Received signal: <TESTCASE> TEST_CASE_ID=arm64.sve-ptrace.SVE
RESULT=SVE_PT_VL_INHERIT
Bad test result: SVE_PT_VL_INHERIT
<LAVA_SIGNAL_TESTCASE TEST_CASE_ID=arm64.sve-ptrace.SVE
RESULT=SVE_PT_VL_INHERIT>
Received signal: <TESTCASE> TEST_CASE_ID=arm64.sve-ptrace.Set RESULT=SVE
Bad test result: SVE
<LAVA_SIGNAL_TESTCASE TEST_CASE_ID=arm64.sve-ptrace.Set RESULT=SVE>
<LAVA_SIGNAL_TESTCASE TEST_CASE_ID=arm64.sve-ptrace.Set RESULT=and>
Received signal: <TESTCASE> TEST_CASE_ID=arm64.sve-ptrace.Set RESULT=and
Bad test result: and
Received signal: <TESTCASE> TEST_CASE_ID=arm64.sve-ptrace.Set RESULT=and
Bad test result: and
..
<LAVA_SIGNAL_TESTCASE TEST_CASE_ID=clone3.clone3_set_tid.[1710] RESULT=Result>
Received signal: <TESTCASE> TEST_CASE_ID=clone3.clone3_set_tid.[1710]
RESULT=Result
Bad test result: Result
[1] https://storage.kernelci.org/next/master/next-20221116/arm64/defconfig+arm6…
[2] https://linaro.atlassian.net/browse/LKQ-934
[3] https://github.com/Linaro/test-definitions/blob/master/automated/linux/ksel…
[4] https://lkft.validation.linaro.org/scheduler/job/5729151#L2511
--
Linaro LKFT
https://lkft.linaro.org
