From: Fengguang Wu <fengguang.wu@intel.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
Jet Chen <jet.chen@intel.com>, Su Tao <tao.su@intel.com>,
Yuanhan Liu <yuanhan.liu@intel.com>, LKP <lkp@01.org>,
linux-kernel@vger.kernel.org
Subject: Re: [x86,kaslr] [ 0.000000] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/cpu/common.c:1422 warn_pre_alternatives()
Date: Thu, 31 Jul 2014 19:27:47 +0800 [thread overview]
Message-ID: <20140731112747.GA13753@localhost> (raw)
In-Reply-To: <20140731025837.GC11241@linux.vnet.ibm.com>
On Wed, Jul 30, 2014 at 07:58:37PM -0700, Paul E. McKenney wrote:
> On Thu, Jul 31, 2014 at 10:42:12AM +0800, Fengguang Wu wrote:
> > On Wed, Jul 30, 2014 at 08:52:07AM -0700, Paul E. McKenney wrote:
> > > On Wed, Jul 30, 2014 at 10:17:32PM +0800, Fengguang Wu wrote:
> > > > On Wed, Jul 30, 2014 at 10:07:56PM +0800, Fengguang Wu wrote:
> > > > > Hi Andy,
> > > > >
> > > > > Here is another WARNING message for the same commit.
> > > > >
> > > > > commit d07c7f1ed61789e175fa975134855be32263be2c
> > > > > Author: Andy Lutomirski <luto@amacapital.net>
> > > > > AuthorDate: Tue Jul 15 18:34:20 2014 -0700
> > > > > Commit: Andy Lutomirski <luto@amacapital.net>
> > > > > CommitDate: Wed Jul 16 10:01:27 2014 -0700
> > > > >
> > > > > x86,kaslr: Use MSR_KVM_GET_RNG_SEED for KASLR if available
> > > > >
> > > > > It's considerably better than any of the alternatives on KVM.
> > > > >
> > > > > Rather than reinventing all of the cpu feature query code, this fixes
> > > > > native_cpuid to work in PIC objects.
> > > > >
> > > > > I haven't combined it with boot/cpuflags.c's cpuid implementation:
> > > > > including asm/processor.h from boot/cpuflags.c results in a flood of
> > > > > unrelated errors, and fixing it might be messy.
> > > > >
> > > > > Signed-off-by: Andy Lutomirski <luto@amacapital.net>
> > > > >
> > > > > +-------------------------------------------------------------------------+------------+------------+
> > > > > | | c6f07a6360 | d07c7f1ed6 |
> > > > > +-------------------------------------------------------------------------+------------+------------+
> > > > > | boot_successes | 1000 | 636 |
> > > > > | boot_failures | 0 | 84 |
> > > > > | WARNING:CPU:PID:at_arch/x86/kernel/cpu/common.c:warn_pre_alternatives() | 0 | 84 |
> > > > > | BUG:unable_to_handle_kernel_NULL_pointer_dereference | 0 | 84 |
> > > > > | Oops | 0 | 84 |
> > > > > | RIP:__free_pages_bootmem | 0 | 84 |
> > > > > | Kernel_panic-not_syncing:Fatal_exception | 0 | 84 |
> > > > > | backtrace:free_all_bootmem | 0 | 84 |
> > > > > | backtrace:mem_init | 0 | 84 |
> > > > > +-------------------------------------------------------------------------+------------+------------+
> > > > >
> > > > > [ 0.000000] PID hash table entries: 2048 (order: 2, 16384 bytes)
> > > > > [ 0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x0
> > > > > [ 0.000000] ------------[ cut here ]------------
> > > > > [ 0.000000] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/cpu/common.c:1422 warn_pre_alternatives+0x1e/0x20()
> > > > > [ 0.000000] You're using static_cpu_has before alternatives have run!
> > > > > [ 0.000000] Modules linked in:
> > > > > [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 3.16.0-rc5-00004-gd07c7f1 #4
> > > > > [ 0.000000] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
> > > > > [ 0.000000] 0000000000000000 ffffffff81803c18 ffffffff813a7bd2 ffffffff81803c60
> > > > > [ 0.000000] ffffffff81803c50 ffffffff810a5485 ffffffff810102f9 ffffffff81803e08
> > > > > [ 0.000000] 0000000000000002 000000000000077c 0000000000000000 ffffffff81803cb0
> > > > > [ 0.000000] Call Trace:
> > > > > [ 0.000000] [<ffffffff813a7bd2>] dump_stack+0x4d/0x66
> > > > > [ 0.000000] [<ffffffff810a5485>] warn_slowpath_common+0x7f/0x98
> > > > > [ 0.000000] [<ffffffff810102f9>] ? warn_pre_alternatives+0x1e/0x20
> > > > > [ 0.000000] [<ffffffff810a54ea>] warn_slowpath_fmt+0x4c/0x4e
> > > > > [ 0.000000] [<ffffffff813b14e3>] ? restore_args+0x30/0x30
> > > > > [ 0.000000] [<ffffffff810102f9>] warn_pre_alternatives+0x1e/0x20
> > > > > [ 0.000000] [<ffffffff810378b5>] __do_page_fault+0x1bd/0x7ca
> > > > > [ 0.000000] [<ffffffff810f5782>] ? console_unlock+0x377/0x3c1
> > > > > [ 0.000000] [<ffffffff810e912e>] ? trace_hardirqs_off+0xd/0xf
> > > > > [ 0.000000] [<ffffffff813afcc5>] ? _raw_spin_unlock_irqrestore+0x40/0x5e
> > > > > [ 0.000000] [<ffffffff81b93d22>] ? __next_mem_range_rev+0x205/0x232
> > > > > [ 0.000000] [<ffffffff810e90e0>] ? trace_hardirqs_off_caller+0xe7/0x128
> > > > > [ 0.000000] [<ffffffff81226d8a>] ? trace_hardirqs_off_thunk+0x3a/0x3c
> > > > > [ 0.000000] [<ffffffff81037ee4>] do_page_fault+0x22/0x27
> > > > > [ 0.000000] [<ffffffff813b2378>] page_fault+0x28/0x30
> > > > > [ 0.000000] [<ffffffff81b74f76>] ? __free_pages_bootmem+0x2d/0xf9
> > > > > [ 0.000000] [<ffffffff81b78d61>] __free_memory_core+0xa7/0xbe
> > > > > [ 0.000000] [<ffffffff81b78fe9>] free_all_bootmem+0x51/0xd2
> > > > > [ 0.000000] [<ffffffff81b67188>] mem_init+0x5c/0x8d
> > > > > [ 0.000000] [<ffffffff81b53cca>] start_kernel+0x1f7/0x53d
> > > > > [ 0.000000] [<ffffffff81b53814>] ? set_init_arg+0x55/0x55
> > > > > [ 0.000000] [<ffffffff81b53120>] ? early_idt_handlers+0x120/0x120
> > > > > [ 0.000000] [<ffffffff81b53471>] x86_64_start_reservations+0x2a/0x2c
> > > > > [ 0.000000] [<ffffffff81b535b3>] x86_64_start_kernel+0x140/0x14d
> > > > > [ 0.000000] ---[ end trace e4962b91bd705c64 ]---
> > > > > [ 0.000000] BUG: unable to handle kernel NULL pointer dereference at 000000000000077c
> > > >
> > > >
> > > > Interestingly, the other bisect result for the above WARNING message
> > > > is
> > > >
> > > > commit ddfb3b363440172d62ce62fbffdf046670d3ce2b
> > >
> > > This is an obsolete commit, but...
> >
> > Paul, would you suggest me to test any new commit or branch HEAD?
>
> The latest branch containing this commit is rcu/dev.2014.07.28e,
> might be worth a shot.
The current rcu/dev.2014.07.28e HEAD commit
8a73ddf16763989f53e85e422ab6af7ca8114c98 looks fine: 110 boots without
a single error!
Thanks,
Fengguang
next prev parent reply other threads:[~2014-07-31 11:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 14:05 [x86,kaslr] [ 0.000000] general protection fault: 0000 [#1] SMP DEBUG_PAGEALLOC Fengguang Wu
2014-07-30 14:07 ` [x86,kaslr] [ 0.000000] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/cpu/common.c:1422 warn_pre_alternatives() Fengguang Wu
2014-07-30 14:17 ` Fengguang Wu
2014-07-30 15:52 ` Paul E. McKenney
2014-07-31 2:42 ` Fengguang Wu
2014-07-31 2:58 ` Paul E. McKenney
2014-07-31 11:27 ` Fengguang Wu [this message]
2014-07-31 14:17 ` Paul E. McKenney
2014-07-30 14:11 ` [x86,kaslr] [ 0.000000] BUG: unable to handle kernel NULL pointer dereference at 00000000000006fc Fengguang Wu
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=20140731112747.GA13753@localhost \
--to=fengguang.wu@intel.com \
--cc=jet.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=luto@amacapital.net \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tao.su@intel.com \
--cc=yuanhan.liu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox