From: Marc Zyngier <maz@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Regressions <regressions@lists.linux.dev>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: WARNING: arch/arm64/kernel/cpufeature.c:3369 this_cpu_has_cap
Date: Tue, 13 Feb 2024 19:18:48 +0000 [thread overview]
Message-ID: <87il2sw4tj.wl-maz@kernel.org> (raw)
In-Reply-To: <CA+G9fYuVJ3DfmOR2GxbVmLqh_d=3y_wTXX-vQOUgp86uX-3oGg@mail.gmail.com>
On Tue, 13 Feb 2024 18:21:23 +0000,
Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>
> Following kernel warning notices on all arm64 devices on today's Linux
> next-20240213 tag.
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
What is the sense of this tag, and even of this email, for an issue
that has already been reported, as outlined below?
>
> [ 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
> [ 0.038691] Modules linked in:
> [ 0.038707] CPU: 0 PID: 1 Comm: swapper/0 Not tainted
> 6.8.0-rc4-next-20240213 #1
> [ 0.038721] Hardware name: Radxa ROCK Pi 4B (DT)
> [ 0.038729] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [ 0.038744] pc : this_cpu_has_cap+0x1c/0x70
> [ 0.038761] lr : has_nv1+0x28/0xe8
> ..
> [ 0.039008] Call trace:
> [ 0.039014] this_cpu_has_cap+0x1c/0x70
> [ 0.039031] update_cpu_capabilities+0xd4/0x138
> [ 0.039048] setup_system_features+0x38/0x130
> [ 0.039075] smp_cpus_done+0x50/0xc8
> [ 0.039094] smp_init+0x84/0xa0
> [ 0.039109] kernel_init_freeable+0x11c/0x400
> [ 0.039126] kernel_init+0x28/0x1f0
> [ 0.039148] ret_from_fork+0x10/0x20
> [ 0.039167] ---[ end trace 0000000000000000 ]---
>
>
> Links:
> - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240213/testrun/22596318/suite/log-parser-boot/test/check-kernel-exception/log
> - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240213/testrun/22596318/suite/log-parser-boot/tests/
>
> 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/
> I will test the corresponding fix patch and get back to you.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Regressions <regressions@lists.linux.dev>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: WARNING: arch/arm64/kernel/cpufeature.c:3369 this_cpu_has_cap
Date: Tue, 13 Feb 2024 19:18:48 +0000 [thread overview]
Message-ID: <87il2sw4tj.wl-maz@kernel.org> (raw)
In-Reply-To: <CA+G9fYuVJ3DfmOR2GxbVmLqh_d=3y_wTXX-vQOUgp86uX-3oGg@mail.gmail.com>
On Tue, 13 Feb 2024 18:21:23 +0000,
Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>
> Following kernel warning notices on all arm64 devices on today's Linux
> next-20240213 tag.
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
What is the sense of this tag, and even of this email, for an issue
that has already been reported, as outlined below?
>
> [ 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
> [ 0.038691] Modules linked in:
> [ 0.038707] CPU: 0 PID: 1 Comm: swapper/0 Not tainted
> 6.8.0-rc4-next-20240213 #1
> [ 0.038721] Hardware name: Radxa ROCK Pi 4B (DT)
> [ 0.038729] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [ 0.038744] pc : this_cpu_has_cap+0x1c/0x70
> [ 0.038761] lr : has_nv1+0x28/0xe8
> ..
> [ 0.039008] Call trace:
> [ 0.039014] this_cpu_has_cap+0x1c/0x70
> [ 0.039031] update_cpu_capabilities+0xd4/0x138
> [ 0.039048] setup_system_features+0x38/0x130
> [ 0.039075] smp_cpus_done+0x50/0xc8
> [ 0.039094] smp_init+0x84/0xa0
> [ 0.039109] kernel_init_freeable+0x11c/0x400
> [ 0.039126] kernel_init+0x28/0x1f0
> [ 0.039148] ret_from_fork+0x10/0x20
> [ 0.039167] ---[ end trace 0000000000000000 ]---
>
>
> Links:
> - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240213/testrun/22596318/suite/log-parser-boot/test/check-kernel-exception/log
> - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240213/testrun/22596318/suite/log-parser-boot/tests/
>
> 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/
> I will test the corresponding fix patch and get back to you.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-13 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 18:21 WARNING: arch/arm64/kernel/cpufeature.c:3369 this_cpu_has_cap Naresh Kamboju
2024-02-13 18:21 ` Naresh Kamboju
2024-02-13 19:18 ` Marc Zyngier [this message]
2024-02-13 19:18 ` Marc Zyngier
2024-02-13 19:38 ` Naresh Kamboju
2024-02-13 19:38 ` Naresh Kamboju
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87il2sw4tj.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=m.szyprowski@samsung.com \
--cc=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
--cc=suzuki.poulose@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.