From: Andi Kleen <ak@linux.intel.com>
To: Maciej Rutecki <maciej.rutecki@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
seto.hidetoshi@jp.fujitsu.com, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: 2.6.30-git(16 and 17) system hangs after resume from suspend to disk, mce related?
Date: Sun, 21 Jun 2009 20:43:04 +0200 [thread overview]
Message-ID: <4A3E7F38.7030300@linux.intel.com> (raw)
In-Reply-To: <8db1092f0906211002y2b391212ve2902fc3a6517586@mail.gmail.com>
Maciej Rutecki wrote:
> Tested kernel version: 2.6.30-git16 and 2.6.30-git17
> Last known good: 2.6.30
>
> System hangs few minutes after resume from suspend to disk.
Thanks for the report.
I assume it runs stable for hours without resume from disk?
And you made sure you don't use stale data from
a different kernel for resume from disk?
It is strange that resume from disk affects machine check.
How is your resume setup?
Do you have any init scripts that change machine check state
before the resume from disk runs?
Is there any chance you could configure netconsole or similar
to get output during the hang?
> I have
> tried bisection and here is result:
I assume you have CONFIG_X86_NEW_MCE enabled, correct?
Does it still happen with CONFIG_X86_OLD_MCE instead?
Also a "a few minutes" suggest something might be going wrong
with the poll handler. Does the problem still happen
with you use CONFIG_X86_NEW_MCE again, but before
resume do
echo 0 > /sys/device/system/machinecheck/machinecheck0/check_interval
On the other hand you should get a crash very fast with
echo 1 > /sys/device/system/machinecheck/machinecheck0/check_interval
If we confirm it's the poll handler I can send you a debugging patch
to narrow it down further if I can't reproduce it.
But that would need console output during the crash.
Your dmesg also doesn't have anything related to resume from disk?
Thanks,
-Andi
next prev parent reply other threads:[~2009-06-21 18:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-21 17:02 2.6.30-git(16 and 17) system hangs after resume from suspend to disk, mce related? Maciej Rutecki
2009-06-21 18:43 ` Andi Kleen [this message]
2009-06-21 20:13 ` Maciej Rutecki
2009-06-22 2:03 ` Hidetoshi Seto
2009-06-22 6:43 ` Andi Kleen
2009-06-22 7:19 ` Maciej Rutecki
2009-06-22 7:20 ` Maciej Rutecki
2009-06-22 9:58 ` Andi Kleen
2009-06-22 11:53 ` Maciej Rutecki
2009-06-22 12:35 ` Andi Kleen
2009-06-22 13:27 ` Maciej Rutecki
2009-06-22 13:49 ` Andi Kleen
2009-06-22 14:08 ` Maciej Rutecki
2009-06-22 14:55 ` Maciej Rutecki
2009-06-22 16:56 ` Andi Kleen
2009-06-22 17:37 ` Maciej Rutecki
2009-06-22 18:12 ` Maciej Rutecki
2009-06-22 18:41 ` Rafael J. Wysocki
2009-06-22 18:45 ` Maciej Rutecki
2009-06-22 19:19 ` Maciej Rutecki
2009-06-23 3:40 ` Hidetoshi Seto
2009-06-23 10:54 ` Hugh Dickins
2009-06-23 11:06 ` Andi Kleen
2009-06-23 14:47 ` Maciej Rutecki
2009-06-23 19:57 ` Andi Kleen
2009-06-24 0:21 ` Hidetoshi Seto
2009-06-24 6:17 ` Andi Kleen
2009-06-25 15:53 ` Maciej Rutecki
2009-06-25 16:20 ` H. Peter Anvin
2009-06-22 6:20 ` Maciej Rutecki
2009-06-22 9:40 ` Maciej Rutecki
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=4A3E7F38.7030300@linux.intel.com \
--to=ak@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=rjw@sisk.pl \
--cc=seto.hidetoshi@jp.fujitsu.com \
/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