All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: Xishi Qiu <qiuxishi@huawei.com>
Cc: "Fleming, Matt" <matt.fleming@intel.com>,
	"Yu, Fenghua" <fenghua.yu@intel.com>,
	Liujiang <jiang.liu@huawei.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Hanjun Guo <guohanjun@huawei.com>,
	WuJianguo <wujianguo@huawei.com>
Subject: RE: [PATCH V3] ia64/mm: fix a bad_page bug when crash kernel booting
Date: Tue, 19 Feb 2013 21:38:52 +0000	[thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F1E06A8F1@ORSMSX108.amr.corp.intel.com> (raw)
In-Reply-To: <5113450C.1080109@huawei.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 388 bytes --]

> In efi_init() memory aligns in IA64_GRANULE_SIZE(16M). If set "crashkernel=1024M-:600M"

Is this where the real problem begins?  Should we insist that users provide crashkernel
parameters rounded to GRANULE boundaries?

-Tony
ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

WARNING: multiple messages have this Message-ID (diff)
From: "Luck, Tony" <tony.luck@intel.com>
To: Xishi Qiu <qiuxishi@huawei.com>
Cc: "Fleming, Matt" <matt.fleming@intel.com>,
	"Yu, Fenghua" <fenghua.yu@intel.com>,
	Liujiang <jiang.liu@huawei.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Hanjun Guo <guohanjun@huawei.com>,
	WuJianguo <wujianguo@huawei.com>
Subject: RE: [PATCH V3] ia64/mm: fix a bad_page bug when crash kernel booting
Date: Tue, 19 Feb 2013 21:38:52 +0000	[thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F1E06A8F1@ORSMSX108.amr.corp.intel.com> (raw)
In-Reply-To: <5113450C.1080109@huawei.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 333 bytes --]

> In efi_init() memory aligns in IA64_GRANULE_SIZE(16M). If set "crashkernel=1024M-:600M"

Is this where the real problem begins?  Should we insist that users provide crashkernel
parameters rounded to GRANULE boundaries?

-Tony
N‹§²æìr¸›zǧu©ž²Æ {\b­†éì¹»\x1c®&Þ–)îÆi¢žØ^n‡r¶‰šŽŠÝ¢j$½§$¢¸\x05¢¹¨­è§~Š'.)îÄÃ,yèm¶ŸÿÃ\f%Š{±šj+ƒðèž×¦j)Z†·Ÿ

WARNING: multiple messages have this Message-ID (diff)
From: "Luck, Tony" <tony.luck@intel.com>
To: Xishi Qiu <qiuxishi@huawei.com>
Cc: "Fleming, Matt" <matt.fleming@intel.com>,
	"Yu, Fenghua" <fenghua.yu@intel.com>,
	Liujiang <jiang.liu@huawei.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Hanjun Guo <guohanjun@huawei.com>,
	WuJianguo <wujianguo@huawei.com>
Subject: RE: [PATCH V3] ia64/mm: fix a bad_page bug when crash kernel booting
Date: Tue, 19 Feb 2013 21:38:52 +0000	[thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F1E06A8F1@ORSMSX108.amr.corp.intel.com> (raw)
In-Reply-To: <5113450C.1080109@huawei.com>

PiBJbiBlZmlfaW5pdCgpIG1lbW9yeSBhbGlnbnMgaW4gSUE2NF9HUkFOVUxFX1NJWkUoMTZNKS4g
SWYgc2V0ICJjcmFzaGtlcm5lbD0xMDI0TS06NjAwTSINCg0KSXMgdGhpcyB3aGVyZSB0aGUgcmVh
bCBwcm9ibGVtIGJlZ2lucz8gIFNob3VsZCB3ZSBpbnNpc3QgdGhhdCB1c2VycyBwcm92aWRlIGNy
YXNoa2VybmVsDQpwYXJhbWV0ZXJzIHJvdW5kZWQgdG8gR1JBTlVMRSBib3VuZGFyaWVzPw0KDQot
VG9ueQ0K

  parent reply	other threads:[~2013-02-19 21:39 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29  3:52 [PATCH] ia64/mm: fix a bad_page bug when crash kernel booting Xishi Qiu
2013-01-29  3:52 ` Xishi Qiu
2013-01-29  3:52 ` Xishi Qiu
2013-01-29  3:52 ` Xishi Qiu
2013-02-04 16:32 ` Matt Fleming
2013-02-04 16:32   ` Matt Fleming
2013-02-04 16:32   ` Matt Fleming
2013-02-05  3:48   ` Xishi Qiu
2013-02-05  3:48     ` Xishi Qiu
2013-02-05  3:48     ` Xishi Qiu
2013-02-05  3:48     ` Xishi Qiu
2013-02-07  2:32   ` [PATCH V2] " Xishi Qiu
2013-02-07  2:32     ` Xishi Qiu
2013-02-07  2:32     ` Xishi Qiu
2013-02-07  2:32     ` Xishi Qiu
2013-02-07  6:09     ` [PATCH V3] " Xishi Qiu
2013-02-07  6:09       ` Xishi Qiu
2013-02-07  6:09       ` Xishi Qiu
2013-02-07  6:09       ` Xishi Qiu
2013-02-13  0:11       ` Tony Luck
2013-02-13  0:11         ` Tony Luck
2013-02-13  0:11         ` Tony Luck
2013-02-13  0:11         ` Tony Luck
2013-02-13  0:19         ` Andrew Morton
2013-02-13  0:19           ` Andrew Morton
2013-02-13  0:19           ` Andrew Morton
2013-02-13  0:19           ` Andrew Morton
2013-02-13  0:32           ` Tony Luck
2013-02-13  0:32             ` Tony Luck
2013-02-13  0:32             ` Tony Luck
2013-02-13  0:22         ` Andrew Morton
2013-02-13  0:22           ` Andrew Morton
2013-02-13  0:22           ` Andrew Morton
2013-02-13  0:22           ` Andrew Morton
2013-02-13 10:07       ` Matt Fleming
2013-02-13 10:07         ` Matt Fleming
2013-02-13 10:07         ` Matt Fleming
2013-02-16  1:55         ` Xishi Qiu
2013-02-16  1:55           ` Xishi Qiu
2013-02-16  1:55           ` Xishi Qiu
2013-02-16  1:55           ` Xishi Qiu
2013-02-19 21:38       ` Luck, Tony [this message]
2013-02-19 21:38         ` Luck, Tony
2013-02-19 21:38         ` Luck, Tony
2013-02-19 21:56       ` Tony Luck
2013-02-19 21:56         ` Tony Luck
2013-02-19 21:56         ` Tony Luck
2013-02-19 21:56         ` Tony Luck
2013-02-20  1:38         ` Xishi Qiu
2013-02-20  1:38           ` Xishi Qiu
2013-02-20  1:38           ` Xishi Qiu
2013-02-21 18:21           ` Tony Luck
2013-02-21 18:21             ` Tony Luck
2013-02-21 18:21             ` Tony Luck

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=3908561D78D1C84285E8C5FCA982C28F1E06A8F1@ORSMSX108.amr.corp.intel.com \
    --to=tony.luck@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=fenghua.yu@intel.com \
    --cc=guohanjun@huawei.com \
    --cc=jiang.liu@huawei.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=matt.fleming@intel.com \
    --cc=qiuxishi@huawei.com \
    --cc=wujianguo@huawei.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 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.