mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Norbert Preining <preining@logic.at>
To: linux-kernel@vger.kernel.org
Subject: khugepaged / firefox going wild in 3.18-rc
Date: Wed, 5 Nov 2014 08:20:27 +0900	[thread overview]
Message-ID: <20141104232027.GO13232@auth.logic.tuwien.ac.at> (raw)

Dear all,

(please Cc)

since 3.18-rc started, regularly, but unpredictably, firefox
(Debian iceweasel) goes completely boom to 100% CPU, and there
is also a kernel task khugepaged doing the same.

I need to kill firefox, or better the X session to get it back to normal.

THe logs don't show any strange output

top's top process:

27021 norbert   20   0 1351536 449868  88788 R 100.4  5.6   4:46.16 iceweasel   
   35 root      39  19       0      0      0 R 100.0  0.0   2:41.10 khugepaged  

Switching back to 3.17 does Not* exhibit the same behaviour.

Is this a bug in Firefox/Iceweasel, or is there something luring in the
kernel.


All the best

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
------------------------------------------------------------------------

             reply	other threads:[~2014-11-04 23:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 23:20 Norbert Preining [this message]
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
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=20141104232027.GO13232@auth.logic.tuwien.ac.at \
    --to=preining@logic.at \
    --cc=linux-kernel@vger.kernel.org \
    /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®