linux-kernel - [BUG, bisect] hrtimer: severe lag after suspend & resume

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150604005624.GA1789@hudson.localdomain>
Date:	Wed, 3 Jun 2015 17:56:24 -0700
From:	Jeremiah Mahler <jmmahler@...il.com>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Preeti U Murthy <preeti@...ux.vnet.ibm.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Viresh Kumar <viresh.kumar@...aro.org>,
	Marcelo Tosatti <mtosatti@...hat.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	John Stultz <john.stultz@...aro.org>,
	linux-kernel@...r.kernel.org
Subject: [BUG, bisect] hrtimer: severe lag after suspend & resume

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@...utronix.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@...utronix.de>
  Reviewed-by: Preeti U Murthy <preeti@...ux.vnet.ibm.com>
  Acked-by: Peter Zijlstra <peterz@...radead.org>
  Cc: Viresh Kumar <viresh.kumar@...aro.org>
  Cc: Marcelo Tosatti <mtosatti@...hat.com>
  Cc: Frederic Weisbecker <fweisbec@...il.com>
  Cc: John Stultz <john.stultz@...aro.org>
  Link: http://lkml.kernel.org/r/20150414203501.132820245@linutronix.de
  Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
  Cc: John Stultz <john.stultz@...aro.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/