[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <31b066c2-d1c9-1592-48cd-bccb4b3a624a@kernel.org>
Date: Wed, 19 Feb 2020 09:16:03 -0700
From: shuah <shuah@...nel.org>
To: Cristian Marussi <cristian.marussi@....com>,
Naresh Kamboju <naresh.kamboju@...aro.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@...r.kernel.org>,
Kees Cook <keescook@...omium.org>
Cc: Anders Roxell <anders.roxell@...aro.org>,
lkft-triage@...ts.linaro.org,
open list <linux-kernel@...r.kernel.org>, ankita@...ibm.com,
Will Deacon <will@...nel.org>, ardb@...nel.org,
"Guohanjun (Hanjun Guo)" <guohanjun@...wei.com>,
shuah <shuah@...nel.org>
Subject: Re: selftests: Linux Kernel Dump Test Module output
On 2/17/20 8:36 AM, Cristian Marussi wrote:
> Hi
>
> n 17/02/2020 11:09, Naresh Kamboju wrote:
>> The selftest lkdtm test failed on x86_64 and arm64.
>> am I missing any pre-requisite?
>>
>> Boot log:
>> [ 3.297812] lkdtm: No crash points registered, enable through debugfs
>>
>
> from your logs I cannot deduce anything useful, but in our CI I've got similar issues
> since the 10/12th of Feb...
>
> TAP version 13
> 1..71
> # selftests: lkdtm: PANIC.sh
> # Cannot find /sys/kernel/debug/provoke-crash/DIRECT (missing CONFIG_LKDTM?)
> not ok 1 selftests: lkdtm: PANIC.sh # SKIP
> # selftests: lkdtm: BUG.sh
> # Cannot find /sys/kernel/debug/provoke-crash/DIRECT (missing CONFIG_LKDTM?)
>
> so I suppose this and a bunch of other (probably new) tests are simply
> missing a bit of CONFIGs... (but I have still to look into this properly)
> (not sure if this also is your case either...)
>
> Regards
>
> Cristian
>
Hi Kees,
Any ideas on what this is about? Missing config or something else?
thanks,
-- Shuah
Powered by blists - more mailing lists