Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754784AbZFEG4w (ORCPT ); Fri, 5 Jun 2009 02:56:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752688AbZFEG4p (ORCPT ); Fri, 5 Jun 2009 02:56:45 -0400 Received: from acsinet11.oracle.com ([141.146.126.233]:16635 "EHLO acsinet11.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751501AbZFEG4o (ORCPT ); Fri, 5 Jun 2009 02:56:44 -0400 Message-ID: <4A28C1A4.9050708@oracle.com> Date: Fri, 05 Jun 2009 14:56:36 +0800 From: Tao Ma User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Amerigo Wang CC: linux-kernel@vger.kernel.org Subject: Re: /proc/kcore has a unreasonable size(281474974617600) in x86_64 2.6.30-rc8. References: <4A289928.7040508@oracle.com> <20090605054902.GF7962@cr0.nay.redhat.com> <4A28B63E.1080004@oracle.com> <20090605064316.GB8171@cr0.nay.redhat.com> In-Reply-To: <20090605064316.GB8171@cr0.nay.redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Source-IP: abhmt004.oracle.com [141.146.116.13] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090209.4A28C1A9.009D:SCFSTAT5015188,ss=1,fgs=0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1744 Lines: 50 Amerigo Wang wrote: > 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@test8 ~]# ll /proc/kcore >>>> -r-------- 1 root root 281474974617600 Jun 5 11:15 /proc/kcore >>>> >>>> [root@ocfs2-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. in el5, when start kdump service it will do something like /sbin/kexec --args-linux -p '--command-line=ro root=LABEL=/ rhgb quiet irqpoll maxcpus=1' --initrd=/boot/initrd-2.6.18-53.el5kdump.img /boot/vmlinuz-2.6.18-53.el5 And the error message is from there. Regards, Tao -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/