From: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Maciej Rutecki <maciej.rutecki@gmail.com>,
Andi Kleen <ak@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"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: Wed, 24 Jun 2009 09:21:10 +0900 [thread overview]
Message-ID: <4A417176.40008@jp.fujitsu.com> (raw)
In-Reply-To: <4A3EE668.5090400@jp.fujitsu.com>
Peter, could you put this patch into urgent too?
Thanks,
H.Seto
===
[PATCH] x86, mce: percpu mcheck_timer should be pinned
Maciej Rutecki wrote:
> > After normal boot I try:
> >
> > echo 1 > /sys/devices/system/machinecheck/machinecheck0/check_interval
> >
> > 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()
If CONFIG_NO_HZ + CONFIG_SMP, timer added via add_timer() might
be migrated on other cpu. Use add_timer_on() instead.
Reported-by: Maciej Rutecki <maciej.rutecki@gmail.com>
Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Tested-by Maciej Rutecki <maciej.rutecki@gmail.com>
CC: Andi Kleen <ak@linux.intel.com>
---
arch/x86/kernel/cpu/mcheck/mce.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/cpu/mcheck/mce.c b/arch/x86/kernel/cpu/mcheck/mce.c
index 7da8fec..8e1794a 100644
--- a/arch/x86/kernel/cpu/mcheck/mce.c
+++ b/arch/x86/kernel/cpu/mcheck/mce.c
@@ -1117,7 +1117,7 @@ static void mcheck_timer(unsigned long data)
*n = min(*n*2, (int)round_jiffies_relative(check_interval*HZ));
t->expires = jiffies + *n;
- add_timer(t);
+ add_timer_on(t, smp_processor_id());
}
static void mce_do_trigger(struct work_struct *work)
@@ -1321,7 +1321,7 @@ static void mce_init_timer(void)
return;
setup_timer(t, mcheck_timer, smp_processor_id());
t->expires = round_jiffies(jiffies + *n);
- add_timer(t);
+ add_timer_on(t, smp_processor_id());
}
/*
--
1.6.3
next prev parent reply other threads:[~2009-06-24 0:21 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
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 [this message]
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=4A417176.40008@jp.fujitsu.com \
--to=seto.hidetoshi@jp.fujitsu.com \
--cc=ak@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=rjw@sisk.pl \
/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