From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
John Stultz <johnstul@us.ibm.com>, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Prarit Bhargava <prarit@redhat.com>,
stable@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Andreas Schwab <schwab@linux-m68k.org>
Subject: [Regression][Revert request] Excessive delay or hang during resume from system suspend due to a hrtimer commit
Date: Sun, 15 Jul 2012 22:40:49 +0200 [thread overview]
Message-ID: <201207152240.50129.rjw@sisk.pl> (raw)
Hi Linus,
Please revert:
commit 5baefd6d84163443215f4a99f6a20f054ef11236
Author: John Stultz <johnstul@us.ibm.com>
Date: Tue Jul 10 18:43:25 2012 -0400
hrtimer: Update hrtimer base offsets each hrtimer_interrupt
This breaks resume on the iBook G4 and Toshiba Portege R500 (at least), by
adding an excessive delay to it (the Toshiba box sometimes hangs hard during
resume from system suspend). According to Andreas
(https://lkml.org/lkml/2012/7/15/66):
"Apparently during or before noirq resume the system is hanging by the same
amount of time as the system was sleeping."
which seems to agree with my observations.
Given that the two known-affected boxes are so different, it is quite probable
that the total number of affected systems is actually quite high.
Thanks!
To everyone involved: the fact that this change, which was likely to introduce
regressions from the look of it alone, has been pushed to Linus (an to -stable
at the same time!) so late in the cycle, is seriuosly disappointing.
Thanks,
Rafael
next reply other threads:[~2012-07-15 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-15 20:40 Rafael J. Wysocki [this message]
2012-07-16 9:47 ` [Regression][Revert request] Excessive delay or hang during resume from system suspend due to a hrtimer commit Thomas Gleixner
2012-07-16 11:16 ` Rafael J. Wysocki
2012-07-16 11:15 ` Thomas Gleixner
2012-07-16 11:26 ` Thomas Gleixner
2012-07-16 15:47 ` John Stultz
2012-07-16 12:48 ` Andreas Schwab
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=201207152240.50129.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=a.p.zijlstra@chello.nl \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=prarit@redhat.com \
--cc=schwab@linux-m68k.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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