From: Vlastimil Babka <vbabka@suse.cz>
To: Norbert Preining <preining@logic.at>
Cc: David Rientjes <rientjes@google.com>, linux-kernel@vger.kernel.org
Subject: Re: khugepaged / firefox going wild in 3.18-rc
Date: Fri, 07 Nov 2014 14:38:17 +0100 [thread overview]
Message-ID: <545CCB49.2010405@suse.cz> (raw)
In-Reply-To: <20141107130717.GF11838@auth.logic.tuwien.ac.at>
On 11/07/2014 02:07 PM, Norbert Preining wrote:
> Hi Vlastimil,
>
> On Thu, 06 Nov 2014, Vlastimil Babka wrote:
>> OK, one possibility is to do (it should apply cleanly)
>> git revert e14c720efdd73c6d69cd8d07fa894bcd11fe1973
>
> I am running with this reverted now, and I cannot reproduce the
> khugepage going overboard anymore.
Great, that's good news if I understand correctly, but ...
> I tried hard since 2 days now, no chance to reproduce.
> Before firefox or shotwell went into boom mode, but not now.
> (For now!)
I suggested the commit to you for revert 1 day ago, and you say you
can't reproduce it for 2 days already? That's a bit suspicious. Did you
already tried to revert it before my suggestion, or were you unable to
reproduce it anymore even before the revert?
>>> Again, as I mentioned, I don't have /proc/pid/stack for any "pid", is
>>> this depending on some specific kerenl option?
>>
>> Ah I missed that. Should be CONFIG_STACKTRACE to enable that.
>
> If you want, I can compile a "default" kernel without the above commit
Hmm it would probably be more useful if I sent you some debug printing
patches first... the stacktrace won't probably tell us much we don't
already know.
> reverted, and turn on STACKTRACE (I have turned it one for *all* future
> kernels I compile ;-)
Yeah that's a good idea :)
> I also didn't try the patch you send me, just the revert from above.
Yeah if the revert helped, the other patch probably wouldn't change
anything. It also didn't help the other guy with similar problem.
> Please let me know which other experiments you want to see.
I'll prepare a debugging patch and send with instructions. Meanwhile you
could send the /proc/zoneinfo contents? :)
Thanks!
Vlastimil
> Thanks
>
> Norbert
>
> ------------------------------------------------------------------------
> PREINING, Norbert http://www.preining.info
> JAIST, Japan TeX Live & Debian Developer
> GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
> ------------------------------------------------------------------------
>
next prev parent reply other threads:[~2014-11-07 13:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 23:20 khugepaged / firefox going wild in 3.18-rc Norbert Preining
2014-11-05 0:00 ` David Rientjes
2014-11-05 0:10 ` Norbert Preining
2014-11-05 0:12 ` Norbert Preining
2014-11-05 0:20 ` David Rientjes
2014-11-06 12:25 ` Vlastimil Babka
2014-11-06 12:39 ` Norbert Preining
2014-11-06 13:03 ` Vlastimil Babka
2014-11-07 13:07 ` Norbert Preining
2014-11-07 13:38 ` Vlastimil Babka [this message]
2014-11-07 13:57 ` Norbert Preining
2014-11-07 15:44 ` Vlastimil Babka
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=545CCB49.2010405@suse.cz \
--to=vbabka@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=preining@logic.at \
--cc=rientjes@google.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