[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090605064316.GB8171@cr0.nay.redhat.com>
Date: Fri, 5 Jun 2009 14:43:16 +0800
From: Amerigo Wang <xiyou.wangcong@...il.com>
To: Tao Ma <tao.ma@...cle.com>
Cc: Amerigo Wang <xiyou.wangcong@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: /proc/kcore has a unreasonable size(281474974617600) in x86_64
2.6.30-rc8.
On Fri, Jun 05, 2009 at 02:07:58PM +0800, Tao Ma wrote:
>
>
> Amerigo Wang wrote:
>> On Fri, Jun 05, 2009 at 12:03:52PM +0800, Tao Ma wrote:
>>> Hi list,
>>> In 2.6.30-rc8, /proc/kcore in x86_64's size is unreasonable
>>> large to be 281474974617600.
>>> While in a x86 box, it is 931131392 which looks sane.
>>>
>>> [root@...t8 ~]# ll /proc/kcore
>>> -r-------- 1 root root 281474974617600 Jun 5 11:15 /proc/kcore
>>>
>>> [root@...s2-test9 ~]$ ll /proc/kcore
>>> -r-------- 1 root root 931131392 Jun 5 11:58 /proc/kcore
>>
>> Hmm, what is your physical RAM size on test8?
>> /proc/kcore looks fine on my x86_64 box.
> Only 4G.
Hmm, my x86_box has 8G mem, the size of kcore looks much
saner than the above huge number, but it is still wrong
according to what the man page describes...
Please do what Andrew said, it will be helpful.
>>
>>> I just noticed this when kexec fails in "Can't find kernel text map
>>> area from kcore".
>>>
>>> Is there something wrong?
>>
>> It looks like that error message is from userspace?
> I just started kdump and get the error message.
IIRC, kdump should use /proc/vmcore, instead of /proc/kcore...
nothing related.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists