[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y3NjmfPGK6qjh5LP@sirena.org.uk>
Date: Tue, 15 Nov 2022 10:02:01 +0000
From: Mark Brown <broonie@...nel.org>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: open list <linux-kernel@...r.kernel.org>,
linux-stable <stable@...r.kernel.org>,
lkft-triage@...ts.linaro.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Arnd Bergmann <arnd@...db.de>,
Catalin Marinas <catalin.marinas@....com>,
Ard Biesheuvel <ardb@...nel.org>
Subject: Re: WARNING: CPU: 0 PID: 1111 at arch/arm64/kernel/fpsimd.c:464
fpsimd_save+0x170/0x1b0
On Tue, Nov 15, 2022 at 12:57:53PM +0530, Naresh Kamboju wrote:
> Following kernel warning noticed while running kselftest arm64 sve-ptrace
> on qemu-arm64 on ampere-altra server.
> [ 422.607034] ------------[ cut here ]------------
> [ 422.615382] WARNING: CPU: 0 PID: 1111 at
> arch/arm64/kernel/fpsimd.c:464 fpsimd_save+0x170/0x1b0
> [ 422.617588] Modules linked in: cfg80211 bluetooth rfkill
> crct10dif_ce sm3_ce sm3 sha3_ce sha512_ce sha512_arm64 fuse drm
Without the ability to reproduce this or more information this
isn't really actionable - since I'm not seeing any changes that
look in the least bit relevant in the stable queue I'm guessing
that it's just happened once?
You mention that this is hosted on an Altra but it looks like
you're running the TCG backend, if there's some reason to expect
that qemu might be unstable when hosted on that platform it's
probably worth looping the qemu people in.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists