Bug#1049967: regression: kernel WARNING at arch/x86/kernel/fpu/xstate.c:973 get_xsave_addr+0x9b/0xb0

2023-08-17 Thread Diederik de Haas 
Control: severity -1 normal
Control: tag -1 confirmed pending upstream
Control: merge -1 1044518

On Thursday, 17 August 2023 17:25:17 CEST Bernd Zeimetz wrote:
> Source: linux
> Version: 5.10.179-5
> Severity: important
> X-Debbugs-Cc: b.zeim...@conova.com, m.viertha...@conova.com
> 
> Hi,
> 
> since updating the bullseye kernel to 5.10.179-5, we get the following
> kernel WARNING (and so a tainted kernel) while running under vmware ESX:
> 
> [0.087938] [ cut here ]
> [0.087940] get of unsupported state
> [0.087947] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:973
> get_xsave_addr+0x9b/0xb0 [0.087948] Modules linked in:

This is the same bug as https://bugs.debian.org/1044518, thus merging

signature.asc
Description: This is a digitally signed message part.

Bug#1049967: regression: kernel WARNING at arch/x86/kernel/fpu/xstate.c:973 get_xsave_addr+0x9b/0xb0

2023-08-17 Thread Bernd Zeimetz 
Source: linux
Version: 5.10.179-5
Severity: important
X-Debbugs-Cc: b.zeim...@conova.com, m.viertha...@conova.com

Hi,

since updating the bullseye kernel to 5.10.179-5, we get the following
kernel WARNING (and so a tainted kernel) while running under vmware ESX:

[0.087938] [ cut here ]
[0.087940] get of unsupported state
[0.087947] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:973 
get_xsave_addr+0x9b/0xb0
[0.087948] Modules linked in:
[0.087952] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.10.0-24-amd64 #1 
Debian 5.10.179-5
[0.087953] Hardware name: VMware, Inc. VMware Virtual Platform/440BX 
Desktop Reference Platform, BIOS 6.00 11/12/2020
[0.087954] RIP: 0010:get_xsave_addr+0x9b/0xb0
[0.087956] Code: 48 83 c4 08 5b e9 15 80 bc 00 80 3d 8d 7c 80 01 00 75 a8 
48 c7 c7 97 de cb 99 89 74 24 04 c6 05 79 7c 80 01 01 e8 f5 96 88 00 <0f> 0b 8b 
74 24 04 eb 89 31 c0 e9 e6 7f bc 00 66 0f 1f 44 00 00 89
[0.087957] RSP: :9a203ec8 EFLAGS: 00010282
[0.087958] RAX:  RBX: 9a46a600 RCX: 8b635fdfffa8
[0.087959] RDX: c0007fff RSI: 7fff RDI: 0247
[0.087960] RBP: 9a46a4a0 R08:  R09: 9a203ce8
[0.087960] R10: 9a203ce0 R11: 8b637fec18a8 R12: 0246
[0.087961] R13:  R14:  R15: 
[0.087962] FS:  () GS:8b635fe0() 
knlGS:
[0.087962] CS:  0010 DS:  ES:  CR0: 80050033
[0.087963] CR2: 8b5d8d602000 CR3: 0001cbc0a001 CR4: 007300b0
[0.087977] Call Trace:
[0.087982]  identify_cpu+0x51f/0x540
[0.087985]  identify_boot_cpu+0xc/0x94
[0.087986]  arch_cpu_finalize_init+0x5/0x47
[0.087988]  start_kernel+0x4ec/0x599
[0.087991]  secondary_startup_64_no_verify+0xb0/0xbb
[0.087993] ---[ end trace 8ac8962c4c9dda0c ]---


This sounds like the issue described in
https://lore.kernel.org/lkml/2023081511-easing-exerciser-c356@gregkh/

Could you please follow up and include the fix in case its not in the
next kernel pointrelease?

Thanks,

Bernd

-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F