[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+G9fYu-2x48SC6jYzuLVDsYt=FF8-9x9e0Nt0X2gb5G1PvdaA@mail.gmail.com>
Date: Wed, 14 Feb 2024 01:08:01 +0530
From: Naresh Kamboju <naresh.kamboju@...aro.org>
To: Marc Zyngier <maz@...nel.org>
Cc: Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Linux Regressions <regressions@...ts.linux.dev>, open list <linux-kernel@...r.kernel.org>,
lkft-triage@...ts.linaro.org, Suzuki K Poulose <suzuki.poulose@....com>,
Marek Szyprowski <m.szyprowski@...sung.com>, Catalin Marinas <catalin.marinas@....com>
Subject: Re: WARNING: arch/arm64/kernel/cpufeature.c:3369 this_cpu_has_cap
On Wed, 14 Feb 2024 at 00:48, Marc Zyngier <maz@...nel.org> wrote:
>
> On Tue, 13 Feb 2024 18:21:23 +0000,
> Naresh Kamboju <naresh.kamboju@...aro.org> wrote:
> >
> > Following kernel warning notices on all arm64 devices on today's Linux
> > next-20240213 tag.
> >
> > Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
>
> What is the sense of this tag, and even of this email, for an issue
> that has already been reported, as outlined below?
LKFT building and testing Linux next tree and found this warning on
today's Linux next-20240213. However it is been reported by someone
else.
You may ignore the tag.
>
> >
> > [ 0.038524] SMP: Total of 6 processors activated.
> > [ 0.038539] CPU: All CPU(s) started at EL2
> > [ 0.038588] CPU features: detected: 32-bit EL0 Support
> > [ 0.038602] CPU features: detected: 32-bit EL1 Support
> > [ 0.038620] CPU features: detected: CRC32 instructions
> > [ 0.038650] ------------[ cut here ]------------
> > [ 0.038656] WARNING: CPU: 0 PID: 1 at
> > arch/arm64/kernel/cpufeature.c:3369 this_cpu_has_cap+0x1c/0x70
..
> >
> > This issue has been addressed in the relevant email thread,
> > https://lore.kernel.org/all/0593516b-2419-49b7-83aa-fe189ffad0c2@arm.com/
> Correct link:
>
> https://lore.kernel.org/all/86bk8k5ts3.wl-maz@kernel.org/
Thank you.
>
> > I will test the corresponding fix patch and get back to you.
I have tested your patch and the reported issue has been fixed.
- Naresh
Powered by blists - more mailing lists