From: Ingo Molnar <mingo@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Borislav Petkov <bp@alien8.de>, Fenghua Yu <fenghua.yu@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Oleg Nesterov <oleg@redhat.com>,
"Yu, Yu-cheng" <yu-cheng.yu@intel.com>
Subject: Re: Got FPU related warning on Intel Quark during boot
Date: Thu, 10 Mar 2016 12:19:35 +0100 [thread overview]
Message-ID: <20160310111935.GB13102@gmail.com> (raw)
In-Reply-To: <CAHp75Vcugjp0UmmQKP3eEdhCEtranDVZMP4kHynaU__SCkmooA@mail.gmail.com>
I've Cc:-ed more FPU developers. Mail quoted below. I don't have a Quark system to
test this on, but maybe others have an idea why this warning triggers?
My thinking is that it's related to:
58122bf1d856 x86/fpu: Default eagerfpu=on on all CPUs
Thanks,
Ingo
* Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> Today tried first time after long break to boot Intel Quark SoC with
> most recent linux-next. Got the following warning:
>
> [ 14.714533] WARNING: CPU: 0 PID: 823 at
> arch/x86/include/asm/fpu/internal.h:163 fpu__clear+0x8c/0x160
> [ 14.726603] Modules linked in:
> [ 14.729910] CPU: 0 PID: 823 Comm: kworker/u2:0 Not tainted
> 4.5.0-rc7-next-20160310+ #137
> [ 14.738307] 00000000 00000000 ce691e20 c12b6fc9 ce691e50 c1049fd1
> c1978c6c 00000000
> [ 14.747000] 00000337 c196b530 000000a3 c102050c 000000a3 ce587ac0
> 00000000 ce653000
> [ 14.755722] ce691e64 c104a095 00000009 00000000 00000000 ce691e74
> c102050c ce587500
> [ 14.764468] Call Trace:
> [ 14.767172] [<c12b6fc9>] dump_stack+0x16/0x1d
> [ 14.771889] [<c1049fd1>] __warn+0xd1/0xf0
> [ 14.776253] [<c102050c>] ? fpu__clear+0x8c/0x160
> [ 14.781234] [<c104a095>] warn_slowpath_null+0x25/0x30
> [ 14.786648] [<c102050c>] fpu__clear+0x8c/0x160
> [ 14.791447] [<c101f347>] flush_thread+0x57/0x60
> [ 14.796341] [<c113a5cc>] flush_old_exec+0x4cc/0x600
> [ 14.801594] [<c117ab20>] load_elf_binary+0x2b0/0x1060
> [ 14.807010] [<c1111220>] ? get_user_pages_remote+0x50/0x60
> [ 14.812898] [<c12c4687>] ? _copy_from_user+0x37/0x40
> [ 14.818236] [<c1139f82>] search_binary_handler+0x62/0x150
> [ 14.824007] [<c113b19c>] do_execveat_common+0x45c/0x600
> [ 14.829647] [<c113b35f>] do_execve+0x1f/0x30
> [ 14.834289] [<c1059941>] call_usermodehelper_exec_async+0x91/0xe0
> [ 14.840765] [<c17f2310>] ret_from_kernel_thread+0x20/0x40
> [ 14.846540] [<c10598b0>] ? umh_complete+0x40/0x40
> [ 14.851626] ---[ end trace 137ff5893f9b85bf ]---
>
> Is it know issue? Or what could I try to fix it?
>
> Reproducibility: 3 of 3.
>
> --
> With Best Regards,
> Andy Shevchenko
next prev parent reply other threads:[~2016-03-10 11:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 10:46 Got FPU related warning on Intel Quark during boot Andy Shevchenko
2016-03-10 11:19 ` Ingo Molnar [this message]
2016-03-10 12:48 ` Andy Shevchenko
2016-03-10 12:56 ` Borislav Petkov
2016-03-10 13:31 ` Andy Shevchenko
2016-03-10 14:59 ` Borislav Petkov
2016-03-10 15:22 ` Andy Shevchenko
2016-03-10 15:45 ` Bryan O'Donoghue
2016-03-10 16:49 ` Borislav Petkov
2016-03-10 17:15 ` Bryan O'Donoghue
2016-03-10 19:06 ` Borislav Petkov
2016-03-11 1:31 ` Andy Lutomirski
2016-03-11 10:50 ` Bryan O'Donoghue
2016-03-11 1:39 ` Andy Lutomirski
2016-03-11 9:08 ` Ingo Molnar
2016-03-11 9:48 ` Borislav Petkov
2016-03-11 11:02 ` Bryan O'Donoghue
2016-03-11 11:26 ` Borislav Petkov
2016-03-11 11:32 ` [PATCH] x86/FPU: Fix FPU handling on legacy FPU machines Borislav Petkov
2016-03-11 18:32 ` Linus Torvalds
2016-03-11 22:03 ` Borislav Petkov
2016-03-11 22:07 ` Dave Hansen
2016-03-11 22:20 ` Borislav Petkov
2016-03-12 17:21 ` Andy Lutomirski
2016-03-12 17:47 ` Borislav Petkov
2016-03-12 12:04 ` Bryan O'Donoghue
2016-03-12 12:27 ` Borislav Petkov
2016-03-12 15:17 ` Ingo Molnar
2016-03-22 22:03 ` Maciej W. Rozycki
2016-03-12 15:08 ` Ingo Molnar
2016-03-12 15:12 ` Ingo Molnar
2016-03-12 15:16 ` [tip:x86/urgent] x86/fpu: Fix eager-FPU " tip-bot 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=20160310111935.GB13102@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oleg@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=yu-cheng.yu@intel.com \
/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.