mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeremiah Mahler <jmmahler@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Preeti U Murthy <preeti@linux.vnet.ibm.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	John Stultz <john.stultz@linaro.org>,
	linux-kernel@vger.kernel.org
Subject: [BUG, bisect] hrtimer: severe lag after suspend & resume
Date: Wed, 3 Jun 2015 17:56:24 -0700	[thread overview]
Message-ID: <20150604005624.GA1789@hudson.localdomain> (raw)

all,

After a fresh boot, the Chrome web browser behaves normally.  Pages
load quickly and scroll fast.  Even image heavy sites such as
images.google.com work fine.  However, after a suspend and resume
cycle, Chrome becomes very slow.  Pages take ten seconds or more to
load.  The scroll bars and buttons are almost completely
unresponsive.  Interestingly, I can run Firefox on the same sites
and it has no issue whatsoever.

I have bisected the kernel and found that the following commit
introduced the bug.  It is present in the latest linux-next (20150602).

  From 868a3e915f7f5eba8f8cb4f7da2276760807c51c Mon Sep 17 00:00:00 2001
  From: Thomas Gleixner <tglx@linutronix.de>
  Date: Tue, 14 Apr 2015 21:08:37 +0000
  Subject: [PATCH] hrtimer: Make offset update smarter
  
  On every tick/hrtimer interrupt we update the offset variables of the
  clock bases. That's silly because these offsets change very seldom.
  
  Add a sequence counter to the time keeping code which keeps track of
  the offset updates (clock_was_set()). Have a sequence cache in the
  hrtimer cpu bases to evaluate whether the offsets must be updated or
  not. This allows us later to avoid pointless cacheline pollution.
  
  Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
  Reviewed-by: Preeti U Murthy <preeti@linux.vnet.ibm.com>
  Acked-by: Peter Zijlstra <peterz@infradead.org>
  Cc: Viresh Kumar <viresh.kumar@linaro.org>
  Cc: Marcelo Tosatti <mtosatti@redhat.com>
  Cc: Frederic Weisbecker <fweisbec@gmail.com>
  Cc: John Stultz <john.stultz@linaro.org>
  Link: http://lkml.kernel.org/r/20150414203501.132820245@linutronix.de
  Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
  Cc: John Stultz <john.stultz@linaro.org>
  ---
   include/linux/hrtimer.h             |  4 ++--
   include/linux/timekeeper_internal.h |  2 ++
   kernel/time/hrtimer.c               |  3 ++-
   kernel/time/timekeeping.c           | 23 ++++++++++++++++-------
   kernel/time/timekeeping.h           |  7 ++++---
   5 files changed, 26 insertions(+), 13 deletions(-)

-- 
- Jeremiah Mahler

             reply	other threads:[~2015-06-04  0:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04  0:56 Jeremiah Mahler [this message]
2015-06-04 11:22 ` Thomas Gleixner
2015-06-04 20:13   ` Jeremiah Mahler
2015-06-04 22:54 ` John Stultz
2015-06-05  0:01   ` Jeremiah Mahler
2015-06-05  7:57   ` Ingo Molnar
2015-06-05  9:14   ` Thomas Gleixner
2015-06-05 10:07     ` Ingo Molnar
2015-06-05 18:52       ` John Stultz
2015-06-08  7:44         ` Thomas Gleixner
2015-06-08 17:37           ` John Stultz
2015-06-08 19:31             ` Thomas Gleixner
2015-06-05 14:02     ` Thomas Gleixner

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=20150604005624.GA1789@hudson.localdomain \
    --to=jmmahler@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=peterz@infradead.org \
    --cc=preeti@linux.vnet.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=viresh.kumar@linaro.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®