From: Stephan von Krawczynski <skraw@ithnet.com>
To: David Rientjes <rientjes@google.com>
Cc: 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: Tue, 14 Jul 2009 11:21:59 +0200 [thread overview]
Message-ID: <20090714112159.ae8b154c.skraw@ithnet.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0907132247001.8784@chino.kir.corp.google.com>
On Mon, 13 Jul 2009 22:53:29 -0700 (PDT)
David Rientjes <rientjes@google.com> wrote:
> On Mon, 13 Jul 2009, Jesse Brandeburg wrote:
> > Try increasing /proc/sys/vm/min_free_kbytes
> >
>
> That won't do anything but cause the failure to happen earlier because
> GFP_HIGH will be restricted to even less ZONE_NORMAL memory.
>
> This is a duplicate of http://bugzilla.kernel.org/show_bug.cgi?id=13648
> which also only affects e1000.
>
> Stephan, perhaps you can try with a CONFIG_SLUB kernel and enable both
> CONFIG_SLUB_DEBUG and CONFIG_SLUB_DEBUG_ON? If that doesn't reveal any
> additional information, this sounds like a candidate for kmemleak.
I just enabled that, fortunately we can play some with this box ;-)
I will inform you tommorrow what happened.
Thanks, stay tuned.
--
Regards,
Stephan
WARNING: multiple messages have this Message-ID (diff)
From: Stephan von Krawczynski <skraw@ithnet.com>
To: David Rientjes <rientjes@google.com>
Cc: 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: Tue, 14 Jul 2009 11:21:59 +0200 [thread overview]
Message-ID: <20090714112159.ae8b154c.skraw@ithnet.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0907132247001.8784@chino.kir.corp.google.com>
On Mon, 13 Jul 2009 22:53:29 -0700 (PDT)
David Rientjes <rientjes@google.com> wrote:
> On Mon, 13 Jul 2009, Jesse Brandeburg wrote:
> > Try increasing /proc/sys/vm/min_free_kbytes
> >
>
> That won't do anything but cause the failure to happen earlier because
> GFP_HIGH will be restricted to even less ZONE_NORMAL memory.
>
> This is a duplicate of http://bugzilla.kernel.org/show_bug.cgi?id=13648
> which also only affects e1000.
>
> Stephan, perhaps you can try with a CONFIG_SLUB kernel and enable both
> CONFIG_SLUB_DEBUG and CONFIG_SLUB_DEBUG_ON? If that doesn't reveal any
> additional information, this sounds like a candidate for kmemleak.
I just enabled that, fortunately we can play some with this box ;-)
I will inform you tommorrow what happened.
Thanks, stay tuned.
--
Regards,
Stephan
--
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-14 9:22 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 11:46 What to do with this message (2.6.30.1) ? Stephan von Krawczynski
2009-07-14 5:40 ` Jesse Brandeburg
2009-07-14 5:40 ` Jesse Brandeburg
2009-07-14 5:53 ` David Rientjes
2009-07-14 5:53 ` David Rientjes
2009-07-14 9:21 ` Stephan von Krawczynski [this message]
2009-07-14 9:21 ` Stephan von Krawczynski
2009-07-15 6:47 ` Stephan von Krawczynski
2009-07-15 6:47 ` Stephan von Krawczynski
2009-07-15 8:18 ` David Rientjes
2009-07-15 8:18 ` David Rientjes
2009-07-15 8:31 ` Justin Piszcz
2009-07-15 8:31 ` Justin Piszcz
2009-07-15 9:37 ` Stephan von Krawczynski
2009-07-15 9:37 ` Stephan von Krawczynski
2009-07-15 20:24 ` David Rientjes
2009-07-15 20:24 ` David Rientjes
2009-07-16 15:14 ` Justin Piszcz
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-16 16:44 ` Justin Piszcz
2009-07-18 10:23 ` What to do with this message (2.6.30.1) ? Stephan von Krawczynski
2009-07-18 10:23 ` Stephan von Krawczynski
2009-07-19 13:22 ` Stephan von Krawczynski
2009-07-19 13:22 ` Stephan von Krawczynski
2009-07-20 12:15 ` Stephan von Krawczynski
2009-07-20 12:15 ` Stephan von Krawczynski
2009-07-21 13:38 ` Stephan von Krawczynski
2009-07-21 13:38 ` Stephan von Krawczynski
2009-07-22 11:53 ` Stephan von Krawczynski
2009-07-22 11:53 ` Stephan von Krawczynski
2009-07-15 9:46 ` Stephan von Krawczynski
2009-07-15 9:46 ` Stephan von Krawczynski
2009-07-15 20:22 ` David Rientjes
2009-07-15 20:22 ` David Rientjes
2009-07-16 13:19 ` Stephan von Krawczynski
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 9:16 ` Stephan von Krawczynski
2009-07-14 10:14 ` 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=20090714112159.ae8b154c.skraw@ithnet.com \
--to=skraw@ithnet.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 \
/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.