From: Jiri Slaby <jirislaby@gmail.com>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: peterz@infradead.org, rjw@sisk.pl, akpm@linux-foundation.org,
rusty@rustcorp.com.au, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 1/1] sched: fix cpu_down deadlock
Date: Fri, 11 Sep 2009 08:28:49 +0200 [thread overview]
Message-ID: <4AA9EE21.5040007@gmail.com> (raw)
In-Reply-To: <4AA9E9B3.8060901@cn.fujitsu.com>
On 09/11/2009 08:09 AM, Lai Jiangshan wrote:
> Does this bug occur when a cpu is being offlined or
> when the system is being suspended?
> Or Both?
Hi, I tried echo 0/1 > /sys/devices/system/cpu/cpu1/online in a loop,
but it didn't trigger the bug. It happened only on suspend/resume cycle
(in the end I found even swsusp in qemu suffers from this).
next prev parent reply other threads:[~2009-09-11 6:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 8:41 [PATCH 1/1] Power: fix suspend vt regression Jiri Slaby
2009-08-11 17:00 ` Greg KH
2009-08-11 21:19 ` Jiri Slaby
2009-08-11 21:20 ` Jiri Slaby
2009-08-31 9:47 ` suspend race -next regression [Was: Power: fix suspend vt regression] Jiri Slaby
2009-08-31 19:32 ` Rafael J. Wysocki
2009-09-04 11:49 ` suspend race -mm " Jiri Slaby
2009-09-04 22:30 ` Jiri Slaby
2009-09-04 22:36 ` Jiri Slaby
2009-09-05 12:39 ` [-mm] warning during suspend [was: suspend race -mm regression] Jiri Slaby
2009-09-05 14:41 ` Xiao Guangrong
2009-09-10 20:57 ` Andrew Morton
2009-09-11 0:00 ` Suresh Siddha
2009-09-11 7:55 ` Xiao Guangrong
2009-09-09 11:41 ` [PATCH 1/1] sched: fix cpu_down deadlock Jiri Slaby
2009-09-09 11:53 ` Peter Zijlstra
2009-09-09 12:23 ` Jiri Slaby
2009-09-09 12:37 ` Peter Zijlstra
2009-09-09 13:46 ` Oleg Nesterov
2009-09-11 6:09 ` Lai Jiangshan
2009-09-11 6:28 ` Jiri Slaby [this message]
2009-09-11 7:38 ` Lai Jiangshan
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=4AA9EE21.5040007@gmail.com \
--to=jirislaby@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rjw@sisk.pl \
--cc=rusty@rustcorp.com.au \
/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.