Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Walle <bernhard@bwalle.de>
To: kexec@lists.infradead.org
Cc: public-fastboot-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@lo.gmane.org,
	public-kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@lo.gmane.org
Subject: Re: kdump cp /proc/vmcore exiting with "Invalid Argument" Error
Date: Sat, 06 Feb 2010 10:41:14 +0100	[thread overview]
Message-ID: <4B6D393A.7060103@bwalle.de> (raw)
In-Reply-To: <74ae4f6a1002051845i6a2787deve82963c5d258eda4@mail.gmail.com>

Am 06.02.2010 03:45, schrieb Sujit V:
> I have integrated the kdump in our linux 2.6.23 based kernel. If I do
> echo c > /proc/sysrq-trigger then it boots the kdump kernel & I use
> the cp /proc/vmcore /local/crash/vmcore-incomplete
> 
> On a new x86 based hardware (32 bit PAE kernel)  the "cp /proc/vmcore
> " command exits prematurely.
> 
> cp -v /proc/vmcore /local/crash/vmcore-incomplete
>       cp: reading `/proc/vmcore': Invalid argument  >>> Error >>
> 
> ls -l /local/crash/
> total 115588
> -r--------    1 0        0        2526724096 Feb  5 03:09 vmcore-incomplete
> 
> ls -l /proc/vmcore
> -r--------    1 0        0        4153763584 Feb  5 03:16 /proc/vmcore
> 
> 
> Every time I trigger kdump the cp command exits after copying
> 2526724096 bytes. So I thought it might be a file size issue.
> Googling pointed out a patch in include/linux/proc_fs.h

I would compare 'readelf -l /proc/vmcore' (ELF program headers) and map
the file offset 2526724096 to the physical memory that belongs to that
file offset. Maybe accessing that physical memory fails for some reason.

> struct vmcore {
> struct list_head list;
> unsigned long long paddr;
> - unsigned long size;
> + unsigned long long size;
> loff_t offset;
> 
> I checked my kernel & it already has this patch.

I don't think that this is the problem because 2526724096 is between 2G
and 4G, so it doesn't point to some "magic border".


Regards,
Bernhard


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2010-02-06  9:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-06  2:45 kdump cp /proc/vmcore exiting with "Invalid Argument" Error Sujit V
2010-02-06  9:41 ` Bernhard Walle [this message]
2010-02-10 18:46   ` Sujit V
2010-02-10 18:51     ` Sujit V
2010-02-11  7:53     ` Bernhard Walle
2010-02-12 23:25       ` Sujit V
2010-02-12 11:40 ` Neil Horman
2010-02-12 23:23   ` Sujit V
2010-02-13 12:59     ` nhorman

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=4B6D393A.7060103@bwalle.de \
    --to=bernhard@bwalle.de \
    --cc=kexec@lists.infradead.org \
    --cc=public-fastboot-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@lo.gmane.org \
    --cc=public-kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@lo.gmane.org \
    /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