lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f0EaZtO29WDhyAmh9vNfb-GcAbQsiJ1Nc5Fh7THzZdKVi2BGt4jl3MQPhAQEhsFFdj6a_OzdY9upf9_FIjvQwpayJoKgs4gcLe92S_1Jq8s=@protonmail.com>
Date:   Wed, 06 Oct 2021 14:22:22 +0000
From:   Ser Olmy <ser.olmy@...tonmail.com>
To:     Borislav Petkov <bp@...en8.de>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        x86-ml <x86@...nel.org>
Subject: Re: [x86] Kernel v5.14 series panic on Celeron Mendocino CPU

On Wednesday, October 6th, 2021 at 3:34 PM, Borislav Petkov <bp@...en8.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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ