Re: selftests: ftrace: Internal error: Oops: sve_save_state

[Daniel Díaz]

Hello!

On Thu, 19 Oct 2023 at 11:26, Mark Brown <broonie@xxxxxxxxxx> wrote:
> On Thu, Oct 19, 2023 at 09:07:02PM +0530, Naresh Kamboju wrote:
> > On Tue, 17 Oct 2023 at 17:52, Mark Brown <broonie@xxxxxxxxxx> wrote:
[...]
> > > To confirm have you seen this on other stables as well or is this only
> > > v6.5?  For how long have you been seeing this?
>
> > This is only seen on 6.5.8-rc2 and seen only once.
> > I have checked on mainline / next and other stable branches and this crash
> > is not seen anywhere else.
>
> > However, I will keep checking them on other branches and next and mainline.
>
> I see.  If the bug has never been reproduced I don't think we can draw
> any conclusion about which branches are affected, I would be a bit
> surprised by something that affects v6.5 only.

We have been seeing this problem in other instances, specifically on
the following kernels:
* 5.15.132, 5.15.134-rc1, 5.15.135, 5.15.136-rc1, 5.15.142, 5.15.145-rc1
* 6.1.42, 6.1.43, 6.1.51-rc1, 6.1.56-rc1, 6.1.59-rc1, 6.1.63
* 6.3.10, 6.3.11
* 6.4.7
* 6.5.2, 6.5.10-rc2

Most recent case is for the current 5.15 RC. Decoded stack trace is here:
-----8<-----
  <4>[   29.297166] ------------[ cut here ]------------
  <4>[ 29.298039] WARNING: CPU: 1 PID: 220 at
arch/arm64/kernel/fpsimd.c:950 do_sve_acc
(/builds/linux/arch/arm64/kernel/fpsimd.c:950 (discriminator 1))
  <4>[   29.300418] Modules linked in: fuse drm dm_mod ip_tables x_tables
  <4>[   29.302720] CPU: 1 PID: 220 Comm: systemd-udevd Not tainted
5.15.145-rc1 #1
  <4>[   29.303601] Hardware name: linux,dummy-virt (DT)
  <4>[   29.304804] pstate: 40400009 (nZcv daif +PAN -UAO -TCO -DIT
-SSBS BTYPE=--)
  <4>[ 29.305615] pc : do_sve_acc
(/builds/linux/arch/arm64/kernel/fpsimd.c:950 (discriminator 1))
  <4>[ 29.306499] lr : do_sve_acc
(/builds/linux/arch/arm64/include/asm/jump_label.h:38
/builds/linux/arch/arm64/include/asm/lse.h:24
/builds/linux/arch/arm64/include/asm/atomic.h:86
/builds/linux/include/linux/atomic/atomic-long.h:335
/builds/linux/include/asm-generic/bitops/atomic.h:42
/builds/linux/include/asm-generic/bitops/instrumented-atomic.h:71
/builds/linux/include/linux/thread_info.h:108
/builds/linux/arch/arm64/kernel/fpsimd.c:949)
  <4>[   29.307466] sp : ffff8000083b3e60
  <4>[   29.308447] x29: ffff8000083b3e60 x28: ffff0000c2f42000 x27:
0000000000000000
  <4>[   29.310500] x26: 0000000000000000 x25: 0000000000000000 x24:
0000000000000000
  <4>[   29.312034] x23: 0000000080001000 x22: 0000ffffb3c8a454 x21:
00000000ffffffff
  <4>[   29.313338] x20: 0000000064000000 x19: ffff0000c2f42000 x18:
0000000000000000
  <4>[   29.314636] x17: 0000000000000000 x16: 0000000000000000 x15:
0000000000000000
  <4>[   29.316090] x14: 0000000000000000 x13: 0000000000000000 x12:
0000000000000000
  <4>[   29.317096] x11: 0000000000000000 x10: 0000000000000000 x9 :
ffffb047a36178f4
  <4>[   29.318131] x8 : ffff0000c2c4d888 x7 : 0000000000000000 x6 :
0000000000000200
  <4>[   29.319171] x5 : ffffb047a5c6f260 x4 : 0000000000000200 x3 :
0000000000000001
  <4>[   29.320180] x2 : 0000000000000000 x1 : ffff4fb95a329000 x0 :
0000000000800800
  <4>[   29.321599] Call trace:
  <4>[ 29.321996] do_sve_acc
(/builds/linux/arch/arm64/kernel/fpsimd.c:950 (discriminator 1))
  <4>[ 29.322674] el0_sve_acc
(/builds/linux/arch/arm64/include/asm/daifflags.h:28
/builds/linux/arch/arm64/kernel/entry-common.c:129
/builds/linux/arch/arm64/kernel/entry-common.c:138
/builds/linux/arch/arm64/kernel/entry-common.c:529)
  <4>[ 29.323273] el0t_64_sync_handler
(/builds/linux/arch/arm64/kernel/entry-common.c:639)
  <4>[ 29.323951] el0t_64_sync (/builds/linux/arch/arm64/kernel/entry.S:584)
  <4>[   29.324598] ---[ end trace b31d3b95f436e1b5 ]---
----->8-----

Complete log (and reproducer) here:
  https://tuxapi.tuxsuite.com/v1/groups/linaro/projects/lkft/tests/2ZoYpOR79EjlFiAuFHeOWN2rwC3

Artifacts (including vmlinux and System.map) can be found here:
  https://storage.tuxsuite.com/public/linaro/lkft/builds/2ZoYoIewSKk26jISEo4QlNaOvVR/

Greetings!

Daniel Díaz
daniel.diaz@xxxxxxxxxx