From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Jones <davej@redhat.com>, Hugh Dickins <hughd@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Paul McKenney <paul.mckenney@linaro.org>
Subject: Re: Debugging Thinkpad T430s occasional suspend failure.
Date: Fri, 15 Feb 2013 16:50:28 +0100 [thread overview]
Message-ID: <20130215155028.GC3324@gmail.com> (raw)
In-Reply-To: <CA+55aFyVE0jyu9uw659ERw5E2DdOhwkQp3gk=gcXP0xrmMh9qA@mail.gmail.com>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
> Paul? Apparently you end up with a dead machine at least
> during resume and no oops. Which isn't very helpful. Maybe
> there is possibly some BUG_ON() in the RCU code somewhere?
AFAICS there's no BUG_ON() or panic() in the RCU code, outside
early init code allocation failure paths where we genuinely
can't continue.
( Unless it _is_ one of those BUG_ON()s triggering during early
resume, reconstructing kernel threads, or the BUG_ON() comes
in indirectly via some other way ... )
Dave, one thing that might be worth trying is to disable
CONFIG_BUG and see whether the system manages to limp through to
get console output?
Thanks,
Ingo
next prev parent reply other threads:[~2013-02-15 15:50 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 19:39 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
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 [this message]
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-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=20130215155028.GC3324@gmail.com \
--to=mingo@kernel.org \
--cc=davej@redhat.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.mckenney@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome