linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Cc: Linux MM <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	davidlohr@hp.com, Rik van Riel <riel@redhat.com>,
	Michel Lespinasse <walken@google.com>,
	Hugh Dickins <hughd@google.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [BUG] kernel BUG at mm/vmacache.c:85!
Date: Mon, 28 Apr 2014 20:00:31 -0400	[thread overview]
Message-ID: <20140429000031.GA4284@redhat.com> (raw)
In-Reply-To: <535EA976.1080402@linux.vnet.ibm.com>

On Tue, Apr 29, 2014 at 12:48:14AM +0530, Srivatsa S. Bhat wrote:
 > Hi,
 > 
 > I hit this during boot on v3.15-rc3, just once so far.
 > Subsequent reboots went fine, and a few quick runs of multi-
 > threaded ebizzy also didn't recreate the problem.
 > 
 > The kernel I was running was v3.15-rc3 + some totally
 > unrelated cpufreq patches.

Could you post those patches somewhere ?
They may not be directly related to the code in the trace, but if
they are randomly corrupting memory, maybe that would explain things ?

	Dave

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2014-04-29  0:00 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28 19:18 [BUG] kernel BUG at mm/vmacache.c:85! Srivatsa S. Bhat
2014-04-28 19:20 ` Srivatsa S. Bhat
2014-04-28 21:20 ` Linus Torvalds
2014-04-28 21:55   ` Linus Torvalds
2014-04-28 22:05     ` Hugh Dickins
2014-04-28 22:14       ` Davidlohr Bueso
2014-04-28 22:25         ` Linus Torvalds
2014-04-29  9:59           ` Srivatsa S. Bhat
2014-04-30 19:16             ` Srivatsa S. Bhat
2014-04-30 19:18               ` Srivatsa S. Bhat
2014-04-30 19:20                 ` Srivatsa S. Bhat
2014-04-30 20:26               ` Linus Torvalds
2014-05-01  3:56               ` Hugh Dickins
2014-04-28 22:39     ` Davidlohr Bueso
2014-04-28 22:58       ` Linus Torvalds
2014-04-28 23:11         ` Andrew Morton
2014-04-28 23:57           ` Linus Torvalds
2014-04-29  0:11             ` Davidlohr Bueso
2014-04-29 10:02               ` Srivatsa S. Bhat
2014-04-29 12:52                 ` [PATCH] vmacache: change vmacache_find() to always check ->vm_mm Oleg Nesterov
2014-04-29 13:09                   ` Srivatsa S. Bhat
2014-04-29 14:02                     ` Oleg Nesterov
2014-04-29 12:40               ` [BUG] kernel BUG at mm/vmacache.c:85! Oleg Nesterov
2014-04-29  8:02       ` Srivatsa S. Bhat
2014-04-29  7:59     ` Srivatsa S. Bhat
2014-04-29  0:00 ` Dave Jones [this message]
2014-04-29  8:21   ` Srivatsa S. Bhat

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=20140429000031.GA4284@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=davidlohr@hp.com \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@redhat.com \
    --cc=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=torvalds@linux-foundation.org \
    --cc=walken@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;
as well as URLs for NNTP newsgroup(s).