From: Borislav Petkov <bp@alien8.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: Andy Lutomirski <luto@amacapital.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>
Subject: Re: WARNING: CPU: 0 PID: 3031 at ./arch/x86/include/asm/fpu/internal.h:530 fpu__restore+0x90/0x130()
Date: Wed, 17 Feb 2016 12:41:27 +0100 [thread overview]
Message-ID: <20160217114127.GD2023@pd.tnic> (raw)
In-Reply-To: <20160217103141.GC2023@pd.tnic>
On Wed, Feb 17, 2016 at 11:31:41AM +0100, Borislav Petkov wrote:
> On Wed, Feb 17, 2016 at 10:35:12AM +0100, Ingo Molnar wrote:
> > So it probably triggers on vanilla v4.4 (or v4.5-rc4) as well, with no
> > recent FPU bits applied?
>
> Nope, 4.4 doesn't trigger. Lemme try some of those other commits...
Results:
tip/x86/fpu:
58122bf1d856 x86/fpu: Default eagerfpu=on on all CPUs - BAD
c6ab109f7e0e x86/fpu: Speed up lazy FPU restores slightly - BAD
a20d7297045f x86/fpu: Fold fpu_copy() into fpu__copy() - BAD
5ed73f40735c x86/fpu: Fix FNSAVE usage in eagerfpu mode - BAD
4ecd16ec7059 x86/fpu: Fix math emulation in eager fpu mode - BAD
765bdb406de4 ("Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm") - BAD
...
v4.4: GOOD
so it must be something else causing it AFAICT.
I'll continue trying the -rc's and the tip/master merges to see what
causes it. Let me know if you have a better idea.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-02-17 11:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 19:27 WARNING: CPU: 0 PID: 3031 at ./arch/x86/include/asm/fpu/internal.h:530 fpu__restore+0x90/0x130() Borislav Petkov
2016-02-11 23:47 ` Andy Lutomirski
2016-02-12 1:16 ` Andy Lutomirski
2016-02-12 17:00 ` Borislav Petkov
2016-02-15 19:14 ` Borislav Petkov
2016-02-16 2:25 ` Andy Lutomirski
2016-02-17 8:16 ` Ingo Molnar
2016-02-17 9:29 ` Borislav Petkov
2016-02-17 9:35 ` Ingo Molnar
2016-02-17 10:31 ` Borislav Petkov
2016-02-17 11:06 ` Ingo Molnar
2016-02-17 11:41 ` Borislav Petkov [this message]
2016-02-17 17:52 ` Andy Lutomirski
2016-02-15 19:05 ` Borislav Petkov
2016-02-12 11:17 ` 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=20160217114127.GD2023@pd.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@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.