From: Andi Kleen <ak@linux.jf.intel.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Vaibhav Nagarnaik <vnagarnaik@google.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@linux.jf.intel.com>
Subject: Re: Oops in ring_buffer_alloc_read_page()
Date: Sun, 23 Jun 2013 11:06:05 -0700 [thread overview]
Message-ID: <20130623180605.GM5643@tassilo.jf.intel.com> (raw)
In-Reply-To: <20130623042528.GA20094@localhost>
> Good question! I tried disabling CPA self-test and the BUG does not
> show up for 10000 boots. So this should be the root cause.
>
The test is very different now than what I wrote originally, but I would
generally expect any bug to be in change_page_attr(), not be in the
self test.
> > > [ 36.776024] *pde = 0e3e1067 *pte = 061e7260
The oops is in a 2MB page that should not have changed by CPA
in theory (it just adds 4KB pages)
I suppose you could log the addresses touched by the test and compare
to the oops addresses.
Most likely the reason you don't see it all the time is that the
test is randomized. So you could make it more stable by fixing
the seed in pageattr-test and perhaps changing it to use more
pages.
> > > [ 36.776024] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2007
Could be also some virtualization problem?
-andi
--
ak@linux.intel.com -- Speaking for myself only
prev parent reply other threads:[~2013-06-23 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 12:08 Fengguang Wu
2013-06-20 14:05 ` Steven Rostedt
2013-06-23 4:25 ` Fengguang Wu
2013-06-23 18:06 ` Andi Kleen [this message]
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=20130623180605.GM5643@tassilo.jf.intel.com \
--to=ak@linux.jf.intel.com \
--cc=fengguang.wu@intel.com \
--cc=hpa@linux.jf.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=vnagarnaik@google.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