Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #80099 > unrolled thread

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

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1049967: regression: kernel WARNING at arch/x86/kernel/fpu/xstate.c:973 get_xsave_addr+0x9b/0xb0 Bernd Zeimetz <bzed@debian.org> - 2023-08-17 17:30 +0200
    Processed: Re: Bug#1049967: regression: kernel WARNING at  arch/x86/kernel/fpu/xstate.c:973 get_xsave_addr+0x9b/0xb0 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-08-17 18:40 +0200
    Bug#1049967: regression: kernel WARNING at arch/x86/kernel/fpu/xstate.c:973 get_xsave_addr+0x9b/0xb0 Diederik de Haas <didi.debian@cknow.org> - 2023-08-17 18:40 +0200
    Bug#1049967: marked as done (regression: kernel WARNING at  arch/x86/kernel/fpu/xstate.c:973 get_xsave_addr+0x9b/0xb0) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-08-18 22:40 +0200

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

Source: linux
Version: 5.10.179-5
Severity: important
X-Debbugs-Cc: b.zeimetz@conova.com, m.vierthaler@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: 0000:ffffffff9a203ec8 EFLAGS: 00010282
[    0.087958] RAX: 0000000000000000 RBX: ffffffff9a46a600 RCX: ffff8b635fdfffa8
[    0.087959] RDX: c0000000ffff7fff RSI: 00000000ffff7fff RDI: 0000000000000247
[    0.087960] RBP: ffffffff9a46a4a0 R08: 0000000000000000 R09: ffffffff9a203ce8
[    0.087960] R10: ffffffff9a203ce0 R11: ffff8b637fec18a8 R12: 0000000000000246
[    0.087961] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[    0.087962] FS:  0000000000000000(0000) GS:ffff8b635fe00000(0000) knlGS:0000000000000000
[    0.087962] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    0.087963] CR2: ffff8b5d8d602000 CR3: 00000001cbc0a001 CR4: 00000000007300b0
[    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 Zeimetz                            Debian GNU/Linux Developer
 http://bzed.de                                http://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

[toc] | [next] | [standalone]

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

Processing control commands:

> severity -1 normal
Bug #1049967 [src:linux] regression: kernel WARNING at arch/x86/kernel/fpu/xstate.c:973 get_xsave_addr+0x9b/0xb0
Severity set to 'normal' from 'important'
> tag -1 confirmed pending upstream
Bug #1049967 [src:linux] regression: kernel WARNING at arch/x86/kernel/fpu/xstate.c:973 get_xsave_addr+0x9b/0xb0
Added tag(s) confirmed, pending, and upstream.
> merge -1 1044518
Bug #1049967 [src:linux] regression: kernel WARNING at arch/x86/kernel/fpu/xstate.c:973 get_xsave_addr+0x9b/0xb0
Bug #1044518 [src:linux] linux: "RIP: 0010:get_xsave_addr+0x9b/0xb0" stacktrace in early boot with -24 bullseye kernel
Merged 1044518 1049967

-- 
1044518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044518
1049967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049967
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#80101

[Multipart message — attachments visible in raw view] — view raw

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.zeimetz@conova.com, m.vierthaler@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

[toc] | [prev] | [next] | [standalone]

#80121 — Bug#1049967: marked as done (regression: kernel WARNING at arch/x86/kernel/fpu/xstate.c:973 get_xsave_addr+0x9b/0xb0)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Fri, 18 Aug 2023 21:29:25 +0100
with message-id <2dadb28ca368809acbb9900196ab200e626ae565.camel@adam-barratt.org.uk>
and subject line Re: Bug#1044518: linux: "RIP: 0010:get_xsave_addr+0x9b/0xb0" stacktrace in early boot with -24 bullseye kernel
has caused the Debian Bug report #1044518,
regarding regression: kernel WARNING at arch/x86/kernel/fpu/xstate.c:973 get_xsave_addr+0x9b/0xb0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1044518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044518
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web