From: "Seemanta Dutta" <seemanta@codeaurora.org>
To: linux-kernel@vger.kernel.org
Subject: kdump: Trouble reading /dev/oldmem from capture kernel
Date: Fri, 5 Aug 2011 14:01:03 -0700 (PDT) [thread overview]
Message-ID: <3f4665f1a191945db7c1711ecd154509.squirrel@www.codeaurora.org> (raw)
Greetings kernel hackers,
I am trying to dump the raw memory from the /dev/oldmem device from within
a kexec()'ed capture kernel. But it seems to be that I can only read 4k of
data from /dev/oldmem. I am following the kdump documentation given in:
http://www.mjmwired.net/kernel/Documentation/kdump/. And according to the
documentation in the above link, /dev/oldmem *should* present the raw view
of memory.
Some details about my scenario:
1. Production kernel panics, and I boot into the dump capture kernel
without any issues.
2. Dump capture kernel provides two interfaces to access 'old' kernel
memory (as per kdump dpcumentation): /dev/oldmem and /proc/vmcore. The
latter works perfectly. But I am more interested in the raw memory, rather
than the core file.
My expectation in this scenario was that I would be able to access entire
physical RAM using the /dev/oldmem device. But turns out, I can't.
I would be grateful if anyone pointed out if I was doing something wrong
or missing something.
This is happening over ARM. Could that have to do something with this ?
Not sure if the ARM integration of KDUMP/KEXEC has something to do with
it.
Your help would be greatly appreciated!
regards,
Seemanta
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next reply other threads:[~2011-08-05 21:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 21:01 Seemanta Dutta [this message]
2011-08-09 7:41 ` kdump: Trouble reading /dev/oldmem from capture kernel Mika Westerberg
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=3f4665f1a191945db7c1711ecd154509.squirrel@www.codeaurora.org \
--to=seemanta@codeaurora.org \
--cc=linux-kernel@vger.kernel.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