From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Christoph Lameter <clameter@sgi.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
npiggin@suse.de, Andrew Morton <akpm@linux-foundation.org>,
GOTO <y-goto@jp.fujitsu.com>
Subject: Re: Warning on memory offline (and possible in usual migration?)
Date: Wed, 16 Apr 2008 11:23:41 +0900 [thread overview]
Message-ID: <20080416112341.ef1d5452.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20080416092334.2dabce2c.kamezawa.hiroyu@jp.fujitsu.com>
On Wed, 16 Apr 2008 09:23:34 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> What I experienced was.
> ==
> %echo offline > /sys/device/system/memoryXXXX/state
> ...wait for a minute
> Ctrl-C
> % sync
> % sync
> % echo offline > /sys/device/system/memoryXXXX/state
> ...wait for a minute
> % echo 3 > /proc/sys/vm/drop_caches
> % echo offline > /sys/device/system/memoryXXXX/state
> success.
> ==
>
> I'll see what happens wish -EBUSY but maybe no help...
>
Adding -EBUSY was no help. some pages seems never to be Uptodate...
== prinkt result ==
not-up-to-date a000400144d83768 60000000000801
not-up-to-date a000400144d83d98 60000000000801
not-up-to-date a000400144d840b0 60000000000801
not-up-to-date a000400144d842a8 60000000000801
not-up-to-date a000400144d8a638 60000000000801
not-up-to-date a000400144d8f780 60000000000801
not-up-to-date a000400144d901a0 60000000000801
not-up-to-date a000400144d915e0 60000000000801
not-up-to-date a000400144d937a0 60000000000801
not-up-to-date a000400144d95d50 60000000000801
not-up-to-date a000400144d97028 60000000000801
not-up-to-date a000400144d97e38 60000000000801
not-up-to-date a000400144d99398 60000000000801
not-up-to-date a000400144d995d8 60000000000801
not-up-to-date a000400144df4e98 60000000000801
not-up-to-date a000400144df5ee8 60000000000801
not-up-to-date a000400144df7010 60000000000801
not-up-to-date a000400144df7400 60000000000801
== repeated.
Hmm...
Thanks,
-Kame
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-04-16 2:23 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 5:58 KAMEZAWA Hiroyuki
2008-04-14 17:46 ` Christoph Lameter
2008-04-15 10:13 ` KAMEZAWA Hiroyuki
2008-04-15 19:31 ` Christoph Lameter
2008-04-16 0:23 ` KAMEZAWA Hiroyuki
2008-04-16 2:23 ` KAMEZAWA Hiroyuki [this message]
2008-04-16 3:10 ` KAMEZAWA Hiroyuki
2008-04-16 5:22 ` KAMEZAWA Hiroyuki
2008-04-16 18:04 ` Christoph Lameter
2008-04-16 11:00 ` KAMEZAWA Hiroyuki
2008-04-16 18:36 ` Andrew Morton
2008-04-17 0:19 ` KAMEZAWA Hiroyuki
2008-04-17 6:38 ` Warning on memory offline (possible in migration ?) KAMEZAWA Hiroyuki
2008-04-17 6:43 ` Andrew Morton
2008-04-17 6:55 ` KAMEZAWA Hiroyuki
2008-04-22 4:41 ` Warning on memory offline (and possible in usual migration?) Nick Piggin
2008-04-22 4:52 ` Nick Piggin
2008-04-22 7:56 ` KAMEZAWA Hiroyuki
2008-04-22 9:43 ` Nick Piggin
2008-04-22 9:57 ` KAMEZAWA Hiroyuki
2008-04-22 19:16 ` Christoph Lameter
2008-04-23 0:48 ` Nick Piggin
2008-04-23 1:37 ` KAMEZAWA Hiroyuki
2008-04-23 2:41 ` KAMEZAWA Hiroyuki
2008-04-23 2:53 ` Nick Piggin
2008-04-23 3:44 ` KAMEZAWA Hiroyuki
2008-04-23 15:28 ` Nick Piggin
2008-04-24 1:34 ` KAMEZAWA Hiroyuki
2008-04-23 17:50 ` Christoph Lameter
2008-04-24 1:36 ` KAMEZAWA Hiroyuki
2008-04-24 19:11 ` Christoph Lameter
2008-04-25 0:11 ` KAMEZAWA Hiroyuki
2008-04-23 17:47 ` Christoph Lameter
2008-04-24 2:13 ` Nick Piggin
2008-04-29 7:20 ` KAMEZAWA Hiroyuki
2008-04-30 6:56 ` Nick Piggin
2008-04-30 7:04 ` KAMEZAWA Hiroyuki
2008-04-30 7:12 ` Andrew Morton
2008-04-30 7:22 ` KAMEZAWA Hiroyuki
2008-04-30 7:26 ` Nick Piggin
2008-04-30 17:59 ` Christoph Lameter
2008-04-30 18:01 ` Christoph Lameter
2008-05-01 1:44 ` Nick Piggin
2008-05-01 19:25 ` Christoph Lameter
2008-05-02 0:44 ` Nick Piggin
2008-05-02 1:07 ` Christoph Lameter
2008-05-02 1:23 ` Nick Piggin
2008-05-02 1:37 ` Christoph Lameter
2008-05-02 21:16 ` Christoph Lameter
2008-05-05 4:27 ` Nick Piggin
2008-05-05 17:28 ` Christoph Lameter
2008-05-06 8:52 ` Nick Piggin
2008-05-06 17:49 ` Christoph Lameter
2008-04-30 23:29 ` kamezawa.hiroyu
2008-05-01 0:34 ` Badari Pulavarty
2008-05-01 8:36 ` kamezawa.hiroyu
2008-04-22 4:50 ` Nick Piggin
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=20080416112341.ef1d5452.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=y-goto@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