From: Dave Jones <davej@redhat.com>
To: Hugh Dickins <hughd@google.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: Debugging Thinkpad T430s occasional suspend failure.
Date: Wed, 13 Feb 2013 14:34:11 -0500 [thread overview]
Message-ID: <20130213193411.GA15928@redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1302122121170.15020@eggly.anvils>
On Tue, Feb 12, 2013 at 09:37:27PM -0800, Hugh Dickins wrote:
> I think for the moment I'm going to hope that under the surface our
> problems are related, and when your bisection points a finger, look
> around to see if it suggests anything for my case. Lazy, but...
I have the worst luck with bisects. Halfway through I started seeing
a *different* suspend failure, which led me down the wrong path
ultimately leading to 59a93c27c which was a red herring even though
it even talks about suspend (I had my hopes high when testing that one).
Started over, and ended up in a merge commit containing just a single
patch to slab (210ed9defff). Reverting that on top of 3.7-rc8 doesn't
fix the problem. Backing up one level of bisect, the other alternative
path was 5b3900cd40, which also didn't help when reverting.
My test was a loop of 100 suspend/resume cycles before calling something
'good'. The 'bad' cases all failed within 10 cycles (usually 2-3).
Dave
next prev parent reply other threads:[~2013-02-13 19:34 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 19:39 Debugging Thinkpad T430s occasional suspend failure Dave Jones
2013-02-12 20:13 ` Linus Torvalds
2013-02-13 0:26 ` Hugh Dickins
2013-02-13 0:40 ` Dave Jones
2013-02-13 0:56 ` Hugh Dickins
2013-02-13 4:16 ` Dave Jones
2013-02-13 5:37 ` Hugh Dickins
2013-02-13 19:34 ` Dave Jones [this message]
2013-02-13 19:56 ` Linus Torvalds
2013-02-13 20:53 ` Dave Jones
2013-02-16 20:54 ` Paul E. McKenney
2013-02-15 1:15 ` Dave Jones
2013-02-15 2:09 ` Linus Torvalds
2013-02-15 15:50 ` Ingo Molnar
2013-02-15 22:33 ` Dave Jones
2013-02-15 17:44 ` Paul E. McKenney
2013-02-15 18:34 ` Linus Torvalds
2013-02-15 18:35 ` Linus Torvalds
2013-02-15 18:50 ` Linus Torvalds
2013-02-16 19:25 ` Paul E. McKenney
2013-02-16 19:46 ` Linus Torvalds
2013-02-16 21:07 ` Paul E. McKenney
2013-02-16 21:53 ` H. Peter Anvin
2013-02-17 22:49 ` H. Peter Anvin
2013-02-18 8:41 ` Ingo Molnar
2013-02-19 8:50 ` Paul E. McKenney
2013-02-19 8:56 ` Ingo Molnar
2013-02-17 15:11 ` Frederic Weisbecker
2013-02-17 17:32 ` Linus Torvalds
2013-02-17 18:17 ` Frederic Weisbecker
2013-02-17 20:58 ` Frederic Weisbecker
2013-02-17 21:02 ` Frederic Weisbecker
2013-02-18 15:53 ` Frederic Weisbecker
2013-02-18 18:12 ` Linus Torvalds
2013-02-19 10:08 ` Frederic Weisbecker
2013-02-18 19:58 ` Thomas Gleixner
2013-02-19 10:38 ` Frederic Weisbecker
2013-02-19 10:44 ` Thomas Gleixner
2013-02-15 2:09 ` Hugh Dickins
2013-02-15 2:15 ` Linus Torvalds
2013-02-16 21:45 ` Hugh Dickins
2013-02-16 23:02 ` Linus Torvalds
2013-02-17 0:01 ` Hugh Dickins
2013-02-17 2:21 ` Hugh Dickins
2013-02-17 13:38 ` Daniel Vetter
2013-02-17 14:54 ` Daniel Vetter
2013-02-17 16:31 ` Hugh Dickins
2013-02-17 17:28 ` Daniel Vetter
2013-02-17 17:28 ` Daniel Vetter
2013-02-13 2:17 ` Dave Jones
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=20130213193411.GA15928@redhat.com \
--to=davej@redhat.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.