From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: David Rientjes <rientjes@google.com>
Cc: Stephan von Krawczynski <skraw@ithnet.com>,
Jesse Brandeburg <jesse.brandeburg@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: What to do with this message (2.6.30.1) ?
Date: Wed, 15 Jul 2009 04:31:36 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0907150430080.4475@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.2.00.0907150115190.14393@chino.kir.corp.google.com>
On Wed, 15 Jul 2009, David Rientjes wrote:
> On Wed, 15 Jul 2009, Stephan von Krawczynski wrote:
>
>> Jul 15 03:01:29 backup kernel: 1444268 total pagecache pages
>> Jul 15 03:01:29 backup kernel: 34 pages in swap cache
>> Jul 15 03:01:29 backup kernel: Swap cache stats: add 118, delete 84, find 0/2
>> Jul 15 03:01:29 backup kernel: Free swap = 2104080kB
>> Jul 15 03:01:29 backup kernel: Total swap = 2104488kB
>>
>
> I added Justin Piszcz to the cc since he was having the same problem as
> described in http://bugzilla.kernel.org/show_bug.cgi?id=13648.
>
> He was unable to get slabtop -o output when this was happening, though, so
> maybe you could grab a snapshot of that when you get these failures? It
> will help us figure out what cache the slab leak is in (assuming there is
> one, >1G of slab on this machine is egregious).
>
> Justin, were you using e1000e in your bug report?
Yes:
[ 9.302541] e1000e 0000:00:19.0: irq 32 for MSI/MSI-X
I will note with 2.6.30.1 (thus far) it has not re-appeared (yet).
>
> If you have some additional time, it would also be helpful to get a
> bisection of when the problem started occurring (it appears to be sometime
> between 2.6.29 and 2.6.30).
>
--
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>
next prev parent reply other threads:[~2009-07-15 7:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090713134621.124aa18e.skraw@ithnet.com>
2009-07-14 5:40 ` Jesse Brandeburg
2009-07-14 5:53 ` David Rientjes
2009-07-14 9:21 ` Stephan von Krawczynski
2009-07-15 6:47 ` Stephan von Krawczynski
2009-07-15 8:18 ` David Rientjes
2009-07-15 8:31 ` Justin Piszcz [this message]
2009-07-15 9:37 ` Stephan von Krawczynski
2009-07-15 20:24 ` David Rientjes
2009-07-16 15:14 ` Justin Piszcz
2009-07-16 16:44 ` What to do with this message (2.6.30.1) ? (happened again) Justin Piszcz
2009-07-18 10:23 ` What to do with this message (2.6.30.1) ? Stephan von Krawczynski
2009-07-19 13:22 ` Stephan von Krawczynski
2009-07-20 12:15 ` Stephan von Krawczynski
2009-07-21 13:38 ` Stephan von Krawczynski
2009-07-22 11:53 ` Stephan von Krawczynski
2009-07-15 9:46 ` Stephan von Krawczynski
2009-07-15 20:22 ` David Rientjes
2009-07-16 13:19 ` Stephan von Krawczynski
2009-07-17 6:36 ` Stephan von Krawczynski
2009-07-14 9:16 ` Stephan von Krawczynski
2009-07-14 10:14 ` Stephan von Krawczynski
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.00.0907150430080.4475@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=jesse.brandeburg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=rjw@sisk.pl \
--cc=skraw@ithnet.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