From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Subject: Debugging Thinkpad T430s occasional suspend failure.
Date: Tue, 12 Feb 2013 14:39:01 -0500 [thread overview]
Message-ID: <20130212193901.GA18906@redhat.com> (raw)
My Thinkpad T430s suspend/resumes fine most of the time. But every so often
(like one in ten times or so), as soon as I suspend, I get a black screen,
and a blinking power button.
(Note: Not the capslock lights like when we panic, this laptop 'conveniently
doesn't have those. This is the light surrounding the power button, which afaik
isn't even OS controlled, so maybe we're dying somewhere in SMI/BIOS land?)
I tried debugging this with pm_trace, which told me..
[ 4.576035] Magic number: 0:455:740
[ 4.576037] hash matches drivers/base/power/main.c:645
Which points me at..
642 Complete:
643 complete_all(&dev->power.completion);
644
645 TRACE_RESUME(error);
646
647 return error;
648 }
The only thing interesting here I think is that this is the resume path.
So perhaps something failed to suspend, and we tried to back out of suspending,
but something was too screwed up to abort cleanly ?
I've tried hooking up a serial console, and even tried console_noblank,
which yielded no additional info at all. (I'm guessing the consoles are suspended
at the time of panic)
I also tried unloading all the modules I have loaded before the suspend, which
seemed to reduce the chances of it happening, but eventually it reoccurred.
Any ideas on how I can further debug this ?
Dave
next reply other threads:[~2013-02-12 19:39 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 19:39 Dave Jones [this message]
2013-02-12 20:13 ` Debugging Thinkpad T430s occasional suspend failure 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
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=20130212193901.GA18906@redhat.com \
--to=davej@redhat.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.