From: Borislav Petkov <bp@alien8.de>
To: Ser Olmy <ser.olmy@protonmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
x86-ml <x86@kernel.org>
Subject: Re: [x86] Kernel v5.14 series panic on Celeron Mendocino CPU
Date: Mon, 4 Oct 2021 19:59:07 +0200 [thread overview]
Message-ID: <YVtA67jImg3KlBTw@zn.tnic> (raw)
In-Reply-To: <CPeoI7yf4421QpWLM-CbgeDR17BBmhlLoixeYI3mu2WbDkgrZItfgImOO6BZez7CXQXXO9liq-rmZzgRVB95TP5MN0xUA8-d7-fSQZdyIZE=@protonmail.com>
On Mon, Oct 04, 2021 at 05:47:37PM +0000, Ser Olmy wrote:
> Booting any 5.14 kernel on certain Celeron-based 32-bit machines results in a panic:
>
> [ 22.546247] Run /init as init process
> [ 22.610556] init[1] bad frame in sigreturn frame:(ptrval) ip:b7d46be6 sp:bff3af30 orax:ffffffff in libc-2.33.so[b7c94000+156000]
> [ 22.749531] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
> [ 22.750240] CPU: 0 PID: 1 Comm: init Not tainted 5.14.9 #1
> [ 22.750240] Hardware name: Hewlett-Packard HP PC/HP Board, BIOS JD.00.06 12/06/2001
> [ 22.750240] Call Trace:
> [ 22.750240] ? dump_stack_lvl+0x32/0x41
> [ 22.750240] ? dump_stack+0xa/0xc
> [ 22.750240] ? panic+0xa2/0x23f
> [ 22.750240] ? do_exit.cold+0x94/0x94
> [ 22.750240] ? do_group_exit+0x2a/0x80
> [ 22.750240] ? get_signal+0x142/0x7a0
> [ 22.750240] ? arch_do_signal_or_restart+0xb1/0x570
> [ 22.750240] ? force_sig_info_to_task+0x65/0xf0
> [ 22.750240] ? vprintk_emit+0x150/0x190
> [ 22.750240] ? exit_to_user_mode_prepare+0x145/0x1e0
> [ 22.750240] ? syscall_exit_to_user_mode+0x18/0x40
> [ 22.750240] ? do_int80_syscall_32+0x3d/0x80
> [ 22.750240] ? entry_INT80_32+0xf0/0xf0
>
> I've bisected it to this commit:
>
> 6f9866a166cd1ad3ebb2dcdb3874aa8fee8dea2f [x86/fpu/signal: Let xrstor handle the features to init]
I'm assuming your CPU cannot do 64-bit mode?
Can you send .config, /proc/cpuinfo and full dmesg pls?
Privately is fine too.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-10-04 17:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 17:47 Ser Olmy
2021-10-04 17:59 ` Borislav Petkov [this message]
2021-10-04 18:17 ` Ser Olmy
2021-10-05 10:05 ` Borislav Petkov
2021-10-06 0:42 ` Ser Olmy
2021-10-06 13:34 ` Borislav Petkov
2021-10-06 14:22 ` Ser Olmy
2021-10-06 17:38 ` [tip: x86/urgent] x86/fpu: Restore the masking out of reserved MXCSR bits tip-bot2 for Borislav Petkov
2021-10-07 23:40 ` Thomas Gleixner
2021-10-08 9:58 ` tip-bot2 for Borislav Petkov
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=YVtA67jImg3KlBTw@zn.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ser.olmy@protonmail.com \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®