From: Andi Kleen <ak@linux.intel.com>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Cc: Maciej Rutecki <maciej.rutecki@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.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: Mon, 22 Jun 2009 08:43:34 +0200 [thread overview]
Message-ID: <4A3F2816.7040103@linux.intel.com> (raw)
In-Reply-To: <4A3EE668.5090400@jp.fujitsu.com>
Hidetoshi Seto wrote:
> Maciej Rutecki wrote:
>>> 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
>> I didn't instructions from above, but I found something else. After
>> normal boot I try:
>>
>> echo 1 > /sys/devices/system/machinecheck/machinecheck0/check_interval
>>
>> I I found this in dmesg:
>>
>> [ 141.704025] ------------[ cut here ]------------
>> [ 141.704039] WARNING: at arch/x86/kernel/cpu/mcheck/mce.c:1102
>> mcheck_timer+0xf5/0x100()
>
> I see. At least this warning will be cleared by following patch.
> WARN_ON(smp_processor_id() != data);
>
> But I'm not sure whether this can cause system hangs or not.
It might actually. If two different handlers run on the same CPU
they could re-add a timer twice, which might cause loops in the timer
list etc.
Maciej, can you test Seto-san's patch please?
BTW this is probably related to
commit eea08f32adb3f97553d49a4f79a119833036000a
Author: Arun R Bharadwaj <arun@linux.vnet.ibm.com>
Date: Thu Apr 16 12:16:41 2009 +0530
timers: Logic to move non pinned timers
it might be also useful to test if reverting that patch makes
the problem go away. But with this patch we need the add_timer_on change.
-Andi
next prev parent reply other threads:[~2009-06-22 6: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
2009-06-21 20:13 ` Maciej Rutecki
2009-06-22 2:03 ` Hidetoshi Seto
2009-06-22 6:43 ` Andi Kleen [this message]
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=4A3F2816.7040103@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