All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Christoph Lameter <cl@linux.com>
Cc: Michal Hocko <mhocko@suse.cz>, Pekka Enberg <penberg@kernel.org>,
	Matt Mackall <mpm@selenic.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: mm: slub: gpf in deactivate_slab
Date: Mon, 07 Apr 2014 13:16:43 -0400	[thread overview]
Message-ID: <5342DD7B.5070202@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1404071212200.9896@nuc>

On 04/07/2014 01:13 PM, Christoph Lameter wrote:
> On Sat, 5 Apr 2014, Sasha Levin wrote:
> 
>> Unfortunately I've been unable to reproduce the issue to get more debug info
>> out of it. However, I've hit something that seems to be somewhat similar
>> to that:
> 
> Could you jsut run with "slub_debug" on the kernel command line to get us
> more diagnostics? Could be memory corruption.

I was running it with "slub_debug=FZPU" when I reported both errors,
there was no other information beyond the traces in the log.


Thanks,
Sasha

--
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>

WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sasha.levin@oracle.com>
To: Christoph Lameter <cl@linux.com>
Cc: Michal Hocko <mhocko@suse.cz>, Pekka Enberg <penberg@kernel.org>,
	Matt Mackall <mpm@selenic.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: mm: slub: gpf in deactivate_slab
Date: Mon, 07 Apr 2014 13:16:43 -0400	[thread overview]
Message-ID: <5342DD7B.5070202@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1404071212200.9896@nuc>

On 04/07/2014 01:13 PM, Christoph Lameter wrote:
> On Sat, 5 Apr 2014, Sasha Levin wrote:
> 
>> Unfortunately I've been unable to reproduce the issue to get more debug info
>> out of it. However, I've hit something that seems to be somewhat similar
>> to that:
> 
> Could you jsut run with "slub_debug" on the kernel command line to get us
> more diagnostics? Could be memory corruption.

I was running it with "slub_debug=FZPU" when I reported both errors,
there was no other information beyond the traces in the log.


Thanks,
Sasha

  reply	other threads:[~2014-04-07 17:16 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12 16:25 mm: slub: gpf in deactivate_slab Sasha Levin
2014-03-12 16:25 ` Sasha Levin
2014-03-25 15:54 ` Sasha Levin
2014-03-25 15:54   ` Sasha Levin
2014-03-25 16:51   ` Christoph Lameter
2014-03-25 16:51     ` Christoph Lameter
2014-03-25 16:52   ` Michal Hocko
2014-03-25 16:52     ` Michal Hocko
2014-03-25 17:06     ` Christoph Lameter
2014-03-25 17:06       ` Christoph Lameter
2014-03-25 17:15       ` Sasha Levin
2014-03-25 17:15         ` Sasha Levin
2014-03-25 18:10         ` Christoph Lameter
2014-03-25 18:10           ` Christoph Lameter
2014-03-26  0:17           ` Sasha Levin
2014-03-26  0:17             ` Sasha Levin
2014-03-26 15:43             ` Christoph Lameter
2014-03-26 15:43               ` Christoph Lameter
2014-04-05 15:20               ` Sasha Levin
2014-04-05 15:20                 ` Sasha Levin
2014-04-07 17:13                 ` Christoph Lameter
2014-04-07 17:13                   ` Christoph Lameter
2014-04-07 17:16                   ` Sasha Levin [this message]
2014-04-07 17:16                     ` Sasha Levin
2014-04-07 19:34                 ` Christoph Lameter
2014-04-07 19:34                   ` Christoph Lameter
2014-03-25 17:56       ` Michal Hocko
2014-03-25 17:56         ` Michal Hocko
2014-03-25 18:01         ` Michal Hocko
2014-03-25 18:01           ` Michal Hocko

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=5342DD7B.5070202@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=cl@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    --cc=mpm@selenic.com \
    --cc=penberg@kernel.org \
    /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.