From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Lin Ming <mlin@ss.pku.edu.cn>
Cc: linux-kernel@vger.kernel.org, Alan Piszcz <ap@solarrain.com>
Subject: Re: 3.0.1: pagevec_lookup+0x1d/0x30, SLAB issues? [again w/DEBUG_VM & SLAB_DEBUG enabled]
Date: Mon, 12 Sep 2011 04:39:16 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1109120438340.16088@p34.internal.lan> (raw)
In-Reply-To: <CAF1ivSa8fFq6hemzJr6A_kgfNN4tOeEfD8kGfx==7JKV6M2hDg@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 877 bytes --]
On Mon, 12 Sep 2011, Lin Ming wrote:
>> [27336.007233] [<ffffffff81089fc3>] kswapd+0xb3/0x250
>> [27336.007237] [<ffffffff8104fea0>] ? abort_exclusive_wait+0xb0/0xb0
>> [27336.007241] [<ffffffff81089f10>] ? balance_pgdat+0x6a0/0x6a0
>> [27336.007244] [<ffffffff8104f457>] kthread+0x87/0x90
>> [27336.007248] [<ffffffff81648814>] kernel_thread_helper+0x4/0x10
>> [27336.007252] [<ffffffff8104f3d0>] ? kthread_flush_work_fn+0x10/0x10
>> [27336.007256] [<ffffffff81648810>] ? gs_change+0xb/0xb
>
> No more info got.
>
> Could you try to make a test case which can trigger this bug reliably?
> You may also try some benchmarks, for example, fio, ffsb, etc.
>
> Lin Ming
Hi,
I do not unfortunately, it seems to occur at random times during heavy I/O+
mem and processing time, are there any other debug options that would help us
here?
Justin.
next prev parent reply other threads:[~2011-09-12 8:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-11 22:17 3.0.1: pagevec_lookup+0x1d/0x30, SLAB issues? Justin Piszcz
2011-09-11 22:44 ` Justin Piszcz
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 [this message]
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.1109120438340.16088@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®