All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ser Olmy <ser.olmy@protonmail.com>
To: Borislav Petkov <bp@alien8.de>
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: Wed, 06 Oct 2021 14:22:22 +0000	[thread overview]
Message-ID: <f0EaZtO29WDhyAmh9vNfb-GcAbQsiJ1Nc5Fh7THzZdKVi2BGt4jl3MQPhAQEhsFFdj6a_OzdY9upf9_FIjvQwpayJoKgs4gcLe92S_1Jq8s=@protonmail.com> (raw)
In-Reply-To: <YV2l+1oIGd2p/Gt5@zn.tnic>

On Wednesday, October 6th, 2021 at 3:34 PM, Borislav Petkov <bp@alien8.de> wrote:
>
> On Wed, Oct 06, 2021 at 12:42:47AM +0000, Ser Olmy wrote:
>
> > [ 21.670972] fpu->state.fxsave.mxcsr: 0xb7be13b4, mxcsr_feature_mask: 0xffbf
> >
> > [ 21.754383] WARNING: CPU: 0 PID: 1 at arch/x86/kernel/fpu/signal.c:384 __fpu_restore_sig+0x51f/0x540
>
> As tglx expected.
>
> I guess this fixes your issue (replace with previous diff pls):
>

I can confirm that with the patch installed, the system does indeed boot normally with nothing out of the ordinary in the dmesg log. Thanks.

Best Regards,

Olmy

  reply	other threads:[~2021-10-06 14:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04 17:47 [x86] Kernel v5.14 series panic on Celeron Mendocino CPU Ser Olmy
2021-10-04 17:59 ` Borislav Petkov
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 [this message]
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='f0EaZtO29WDhyAmh9vNfb-GcAbQsiJ1Nc5Fh7THzZdKVi2BGt4jl3MQPhAQEhsFFdj6a_OzdY9upf9_FIjvQwpayJoKgs4gcLe92S_1Jq8s=@protonmail.com' \
    --to=ser.olmy@protonmail.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.