From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Cc: Alan Piszcz <ap@solarrain.com>, mlin@ss.pku.edu.cn
Subject: Re: 3.0.1: pagevec_lookup+0x1d/0x30, SLAB issues?
Date: Sun, 11 Sep 2011 18:44:17 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1109111837200.19558@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.2.02.1109111815520.19558@p34.internal.lan>
On Sun, 11 Sep 2011, Justin Piszcz wrote:
> Hi,
>
> With 3.0.1 now and all options compiled in and threadirqs removed, I get the
> same error this user is seeing:
> http://www.gossamer-threads.com/lists/linux/kernel/1424997
>
Hello Lin,
I missed your mail (sender IP is in a CIDR blacklist), disabled & whitelisted
for now:
http://marc.info/?l=linux-kernel&m=131567477126674&w=2
I've enabled this and I will post a new e-mail / output if it happens
again with debug enabled for SLAB.
Response to your e-mail:
> Could you tell how to reproduce this?
Running a lot of processes at the same time (memory/cpu+i/o)
> And would you please turn on more debug options to capture more info?
Yup, done now; however, I am using SLAB, not SLUB; so I've enabled:
-> [*] Debug slab memory allocations
-> [*] Memory leak debugging
-> [*] Debug VM
> CONFIG_SLUB_DEBUG=y
> CONFIG_SLUB_DEBUG_ON=y
> CONFIG_DEBUG_VM=y
Please let me know if there are any other options you think would be useful
to enable or if this should be good, if it recurs again-- as noted above
I will post an update.
Justin.
next prev parent reply other threads:[~2011-09-11 22:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-11 22:17 Justin Piszcz
2011-09-11 22:44 ` Justin Piszcz [this message]
2011-09-12 7:52 ` 3.0.1: pagevec_lookup+0x1d/0x30, SLAB issues? [again w/DEBUG_VM & SLAB_DEBUG enabled] Justin Piszcz
2011-09-12 8:32 ` Lin Ming
2011-09-12 8:39 ` Justin Piszcz
2011-09-12 15:15 ` 3.0.1: pagevec_lookup+0x1d/0x30, SLAB issues? (now shows further DEBUG w/DEBUG_SLAB! possibly(?)] Justin Piszcz
2011-09-14 8:56 ` 3.0.1: pagevec_lookup+0x1d/0x30, SLAB issues? Lin Ming
2011-09-14 9:47 ` Justin Piszcz
2011-09-14 10:20 ` Eric Dumazet
2011-09-14 10:53 ` Justin Piszcz
2011-09-14 13:10 ` Justin Piszcz
2011-09-14 18:58 ` Justin Piszcz
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=alpine.DEB.2.02.1109111837200.19558@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=ap@solarrain.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mlin@ss.pku.edu.cn \
/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
all inboxes | Powered by JetHome®