From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Alexei Starovoitov <ast@kernel.org>,
Borislav Petkov <bp@alien8.de>
Subject: Re: 6.1.48 regression at boot : WARNING: CPU: 0 PID: 0 at arch/x86/kernel/alternative.c:572 apply_returns+0x1e4/0x210
Date: Sun, 27 Aug 2023 07:52:22 +0700 [thread overview]
Message-ID: <ZOqeRpAHzqLDrlno@debian.me> (raw)
In-Reply-To: <3d6fbd04-2861-91a8-938c-45195f307eed@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 2248 bytes --]
On Sat, Aug 26, 2023 at 03:47:13PM +0200, Toralf Förster wrote:
>
> I do get a
>
> missing return thunk: 0xffffffff948a73fe-srso_untrain_ret+0x0/0x2: e9 7b 92
> 35 ff
> WARNING: CPU: 0 PID: 0 at arch/x86/kernel/alternative.c:572
> apply_returns+0x1e4/0x210
> Modules linked in:
> CPU: 0 PID: 0 Comm: swapper/0 Tainted: G T 6.1.48 #38
Do you have any external modules?
> Hardware name: LENOVO 21J5002FGE/21J5002FGE, BIOS R23ET60W (1.30 )
> 09/14/2022
> RIP: 0010:apply_returns+0x1e4/0x210
> Code: 36 01 00 0f 85 f7 fe ff ff 49 89 d8 b9 05 00 00 00 4c 89 f2 48 89 de
> 48 c7 c7 e8 7e ff 93 c6 05 22 7d 36 01 01 e8 8c a9 09 00 <0f> 0b e9 cf fe ff
> ff c7 84 24 81 00 00 00 cc cc cc cc 42 c7 44 38
> RSP: 0000:ffffffff94203e00 EFLAGS: 00010246
> RAX: 0000000000000000 RBX: ffffffff948a73fe RCX: 0000000000000000
> RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
> RBP: ffffffff9488601c R08: 0000000000000000 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff948866e8
> R13: cccccccccccccccc R14: ffffffff93c0067e R15: ffffffff94219118
> FS: 0000000000000000(0000) GS:ffff97dcdee00000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: ffff97d6f4c01000 CR3: 0000000234210000 CR4: 0000000000750ef0
> PKRU: 55555554
> Call Trace:
> <TASK>
> ? __warn+0x6f/0xc0
> ? apply_returns+0x1e4/0x210
> ? report_bug+0xdb/0x140
> ? handle_bug+0x3c/0x70
> ? exc_invalid_op+0x17/0x80
> ? asm_exc_invalid_op+0x1a/0x20
> ? retbleed_return_thunk+0x7e/0x7e
> ? apply_returns+0x1e4/0x210
> ? _raw_spin_unlock_irqrestore+0xd/0x30
> alternative_instructions+0x68/0x1e1
> arch_cpu_finalize_init+0x48/0x9a
> start_kernel+0x789/0x877
> secondary_startup_64_no_verify+0xd3/0xdb
> </TASK>
> ---[ end trace 0000000000000000 ]---
>
> here at a
>
> Linux p14s 6.1.48 #38 SMP Sat Aug 26 15:41:04 CEST 2023 x86_64 AMD Ryzen 7
> PRO 6850U with Radeon Graphics AuthenticAMD GNU/Linux
>
> Otherwise the kernel seems to work fine.
Can you confirm that v6.1.47 doesn't have this regression? Is it also
reproducible on latest mainline?
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-08-27 0:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 13:47 6.1.48 regression at boot : WARNING: CPU: 0 PID: 0 at arch/x86/kernel/alternative.c:572 apply_returns+0x1e4/0x210 Toralf Förster
2023-08-27 0:52 ` Bagas Sanjaya [this message]
2023-08-27 10:52 ` Toralf Förster
2023-08-27 11:15 ` Bagas Sanjaya
2023-08-27 11:13 ` Bagas Sanjaya
2023-08-27 19:23 ` Toralf Förster
2023-08-28 0:38 ` Bagas Sanjaya
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=ZOqeRpAHzqLDrlno@debian.me \
--to=bagasdotme@gmail.com \
--cc=ast@kernel.org \
--cc=bp@alien8.de \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=toralf.foerster@gmx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox