Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1336225
| From | Borislav Petkov <bp@alien8.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: WARNING: CPU: 0 PID: 3031 at ./arch/x86/include/asm/fpu/internal.h:530 fpu__restore+0x90/0x130() |
| Date | 2016-02-17 11:40 +0100 |
| Message-ID | <r37Gy-55s-3@gated-at.bofh.it> (permalink) |
| References | (4 earlier) <r2wQF-5oT-7@gated-at.bofh.it> <r2DyO-1ku-15@gated-at.bofh.it> <r35v4-3Dc-15@gated-at.bofh.it> <r36AO-4lp-9@gated-at.bofh.it> <r36Ku-4qr-17@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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...
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
WARNING: CPU: 0 PID: 3031 at ./arch/x86/include/asm/fpu/internal.h:530 fpu__restore+0x90/0x130() Borislav Petkov <bp@alien8.de> - 2016-02-11 20:30 +0100
Re: WARNING: CPU: 0 PID: 3031 at ./arch/x86/include/asm/fpu/internal.h:530 fpu__restore+0x90/0x130() Andy Lutomirski <luto@amacapital.net> - 2016-02-12 00:50 +0100
Re: WARNING: CPU: 0 PID: 3031 at ./arch/x86/include/asm/fpu/internal.h:530 fpu__restore+0x90/0x130() Andy Lutomirski <luto@amacapital.net> - 2016-02-12 02:20 +0100
Re: WARNING: CPU: 0 PID: 3031 at ./arch/x86/include/asm/fpu/internal.h:530 fpu__restore+0x90/0x130() Borislav Petkov <bp@alien8.de> - 2016-02-12 18:10 +0100
Re: WARNING: CPU: 0 PID: 3031 at ./arch/x86/include/asm/fpu/internal.h:530 fpu__restore+0x90/0x130() Borislav Petkov <bp@alien8.de> - 2016-02-15 20:20 +0100
Re: WARNING: CPU: 0 PID: 3031 at ./arch/x86/include/asm/fpu/internal.h:530 fpu__restore+0x90/0x130() Andy Lutomirski <luto@amacapital.net> - 2016-02-16 03:30 +0100
Re: WARNING: CPU: 0 PID: 3031 at ./arch/x86/include/asm/fpu/internal.h:530 fpu__restore+0x90/0x130() Ingo Molnar <mingo@kernel.org> - 2016-02-17 09:20 +0100
Re: WARNING: CPU: 0 PID: 3031 at ./arch/x86/include/asm/fpu/internal.h:530 fpu__restore+0x90/0x130() Borislav Petkov <bp@alien8.de> - 2016-02-17 10:30 +0100
Re: WARNING: CPU: 0 PID: 3031 at ./arch/x86/include/asm/fpu/internal.h:530 fpu__restore+0x90/0x130() Ingo Molnar <mingo@kernel.org> - 2016-02-17 10:40 +0100
Re: WARNING: CPU: 0 PID: 3031 at ./arch/x86/include/asm/fpu/internal.h:530 fpu__restore+0x90/0x130() Borislav Petkov <bp@alien8.de> - 2016-02-17 11:40 +0100
Re: WARNING: CPU: 0 PID: 3031 at ./arch/x86/include/asm/fpu/internal.h:530 fpu__restore+0x90/0x130() Ingo Molnar <mingo@kernel.org> - 2016-02-17 12:10 +0100
Re: WARNING: CPU: 0 PID: 3031 at ./arch/x86/include/asm/fpu/internal.h:530 fpu__restore+0x90/0x130() Borislav Petkov <bp@alien8.de> - 2016-02-17 12:50 +0100
Re: WARNING: CPU: 0 PID: 3031 at ./arch/x86/include/asm/fpu/internal.h:530 fpu__restore+0x90/0x130() Andy Lutomirski <luto@amacapital.net> - 2016-02-17 19:00 +0100
Re: WARNING: CPU: 0 PID: 3031 at ./arch/x86/include/asm/fpu/internal.h:530 fpu__restore+0x90/0x130() Borislav Petkov <bp@alien8.de> - 2016-02-15 20:10 +0100
Re: WARNING: CPU: 0 PID: 3031 at ./arch/x86/include/asm/fpu/internal.h:530 fpu__restore+0x90/0x130() Borislav Petkov <bp@alien8.de> - 2016-02-12 12:20 +0100
csiph-web