mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: kernel test robot <fengguang.wu@intel.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@01.org, Pranith Kumar <bobby.prani@gmail.com>
Subject: Re: [LKP] [rcu] BUG: kernel_boot_hang mode:0x10d0
Date: Sun, 26 Oct 2014 19:51:44 -0700	[thread overview]
Message-ID: <1414378304.15751.26.camel@perches.com> (raw)
In-Reply-To: <20141027020415.GC27038@yliu-dev.sh.intel.com>

On Mon, 2014-10-27 at 10:04 +0800, kernel test robot wrote:
> FYI, we noticed the below changes on
> 
> commit eea203fea3484598280a07fe503e025e886297fb ("rcu: Use pr_alert/pr_cont for printing logs")
> 
> 
> +------------------------------------------------------------------+------------+------------+
> |                                                                  | 188c1e896c | eea203fea3 |
> +------------------------------------------------------------------+------------+------------+
> | boot_successes                                                   | 0          | 2          |
> | boot_failures                                                    | 15         | 13         |
> | page_allocation_failure:order:,mode:x10d0                        | 15         | 13         |
> | Kernel_panic-not_syncing:Out_of_memory_and_no_killable_processes | 15         |            |
> | backtrace:ring_buffer_consumer_thread                            | 15         | 13         |
> | backtrace:rcu_torture_stats                                      | 15         |            |
> | BUG:kernel_boot_hang                                             | 0          | 13         |
> +------------------------------------------------------------------+------------+------------+

I've no good idea why this change should cause any issue.



           reply	other threads:[~2014-10-27  2:51 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20141027020415.GC27038@yliu-dev.sh.intel.com>]

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=1414378304.15751.26.camel@perches.com \
    --to=joe@perches.com \
    --cc=bobby.prani@gmail.com \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=paulmck@linux.vnet.ibm.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

Powered by JetHome