<br><font size=2 face="sans-serif">Hi,</font>
<br>
<br><font size=2 face="sans-serif">I checked.. through and fond out that
one of the following check condition is failing</font>
<br>
<br><font size=2 face="sans-serif"> 516
if (memcmp(ehdr.e_ident, ELFMAG, SELFMAG) != 0 ||</font>
<br><font size=2 face="sans-serif"> 517
(ehdr.e_type != ET_CORE) ||</font>
<br><font size=2 face="sans-serif"> 518
!vmcore_elf_check_arch(&ehdr) ||</font>
<br><font size=2 face="sans-serif"> 519
ehdr.e_ident[EI_CLASS] != ELFCLASS64
||</font>
<br><font size=2 face="sans-serif"> 520
ehdr.e_ident[EI_VERSION] != EV_CURRENT
||</font>
<br><font size=2 face="sans-serif"> 521
ehdr.e_version != EV_CURRENT ||</font>
<br><font size=2 face="sans-serif"> 522
ehdr.e_ehsize != sizeof(Elf64_Ehdr)
||</font>
<br><font size=2 face="sans-serif"> 523
ehdr.e_phentsize != sizeof(Elf64_Phdr)
||</font>
<br><font size=2 face="sans-serif"> 524
ehdr.e_phnum == 0) {</font>
<br><font size=2 face="sans-serif"> 525
printk(KERN_WARNING "Warning: Core
image elf header is not"</font>
<br><font size=2 face="sans-serif"> 526
"sane:%ld\n",elfcorehdr_addr);</font>
<br><font size=2 face="sans-serif"> 527
return -EINVAL</font>
<br><font size=2 face="sans-serif"> 528
}</font>
<br>
<br><font size=2 face="sans-serif">If I comment this return at line 527,
then the code flows through and the vmcore is getting generated. </font>
<br>
<br><font size=2 face="sans-serif">However, I am facing a new issue, my
user space is 32 bit and the kernel is 64 bit. And I want to access the
high memory (high_memory - BACK_UP_SIZE) area of the previous/primary kernel.
Where some log data I had saved. The toral RAM is 8GB.</font>
<br>
<br><font size=2 face="sans-serif">As the 32 bit pointers could not reach
there... means simple file operations lseek() , read etc are not working..
to access some region around 8GB.</font>
<br>
<br><font size=2 face="sans-serif">Can you please suggest me some way to
reach that memory and read my raw data from the user space. </font>
<br>
<br><font size=2 face="sans-serif">I am able to read the data from kernel
space( a simple kernel module via /proc interface to transfer the data
from kernel to user space using physical address of the primary kernel).</font>
<br>
<br>
<br><font size=2 face="sans-serif"><br>
Chandan Kumar<br>
TCS Mumbai<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Chandan12 K <chandan12.k@tcs.com></b>
</font>
<br><font size=1 face="sans-serif">Sent by: kexec-bounces@lists.infradead.org</font>
<p><font size=1 face="sans-serif">08/13/2009 03:40 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">kexec@lists.infradead.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">vmcore file 0 size in x86_64</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2 face="sans-serif"><br>
Hi,</font><font size=3> </font><font size=2 face="sans-serif"><br>
<br>
Adding boot logs</font><font size=3> </font><font size=2 face="sans-serif"><br>
<br>
NET: Registered protocol family 1</font><font size=3> </font><font size=2 face="sans-serif"><br>
audit: initializing netlink socket (disabled)</font><font size=3> </font><font size=2 face="sans-serif"><br>
type=2000 audit(1250069944.104:1): initialized</font><font size=3> </font><font size=2 face="sans-serif"><br>
VFS: Disk quotas dquot_6.5.1</font><font size=3> </font><font size=2 face="sans-serif"><br>
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)</font><font size=3>
</font><font size=2 face="sans-serif"><br>
Warning: Core image elf header is notsane</font><font size=3> </font><font size=2 face="sans-serif"><br>
Kdump: vmcore not initialized</font><font size=3> </font><font size=2 face="sans-serif"><br>
Registering unionfs 2.2-mm</font><font size=3> </font><font size=2 face="sans-serif"><br>
msgmni has been set to 90</font><font size=3> </font><font size=2 face="sans-serif"><br>
io scheduler noop registered</font><font size=3> </font><font size=2 face="sans-serif"><br>
io scheduler anticipatory registered</font><font size=3><br>
</font><font size=2 face="sans-serif"><br>
<br>
however, similar case has already been discussed in other mailing lists
with vivek. The only difference is that, I am not using redhat system and
dont have any user level kexel tools. </font><font size=3> </font><font size=3 color=blue><u><br>
<br>
</u></font><a href="https://lists.linux-foundation.org/pipermail/fastboot/2007-January/012572.html"><font size=2 color=blue face="Trebuchet MS"><u>https://lists.linux-foundation.org/pipermail/fastboot/2007-January/012572.html</u></font></a><font size=3>
</font><font size=2 face="sans-serif"><br>
<br>
The kernel command line of capture kernel (kexe'ed kernel) : Kernel command
line: root=/dev/nfs rw console=ttyS0,115200 ip=::::::dhcp selinux=0 noacpi
maxcpus=1 memmap=exactmap memmap=640K@0K memmap=64876K@16384K elfcorehdr=81260K</font><font size=3>
<br>
</font><font size=2 face="sans-serif"><br>
<br>
Command line for the Primary kernel : root=/dev/nfs rw console=ttyS0,115200
ip=::::::dhcp crashkernel=64M@16M</font><font size=3> </font><font size=2 face="sans-serif"><br>
<br>
kexec command used : kexec -p bzImage --append="root=/dev/nfs rw console=ttyS0,115200
ip=::::::dhcp selinux=0 noacpi maxcpus=1"</font><font size=3> </font><font size=2 face="sans-serif"><br>
<br>
Kconfig options :</font><font size=3> </font><font size=2 face="sans-serif"><br>
<br>
CONFIG_CRASH_DUMP=y</font><font size=3> </font><font size=2 face="sans-serif"><br>
CONFIG_PHYSICAL_START=0x200000</font><font size=3> </font><font size=2 face="sans-serif"><br>
CONFIG_RELOCATABLE=y</font><font size=3> </font><font size=2 face="sans-serif"><br>
CONFIG_PHYSICAL_ALIGN=0x200000<br>
<br>
Please suggest.</font><font size=3> </font><font size=2 face="sans-serif"><br>
</font><font size=3><br>
</font><font size=2 face="sans-serif"><br>
Chandan</font><font size=3> <br>
<br>
</font>
<table width=100%>
<tr valign=top>
<td width=48%><font size=1 face="sans-serif"><b>Dave Anderson <anderson@redhat.com></b>
<br>
Sent by: crash-utility-bounces@redhat.com</font><font size=3> </font>
<p><font size=1 face="sans-serif">08/12/2009 07:39 PM</font><font size=3>
</font>
<br>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
"Discussion list for crash utility usage, maintenance
and development" <crash-utility@redhat.com></font></div></table>
<br>
<td width=51%>
<br>
<table width=100%>
<tr valign=top>
<td width=7%>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td width=92%><font size=1 face="sans-serif">"Discussion list for
crash utility usage, maintenance and development"
<crash-utility@redhat.com></font><font size=3> </font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [Crash-utility] vmcore file size
0 on x86_64</font></table>
<br><font size=3><br>
</font>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br><font size=3><br>
<br>
</font><tt><font size=2><br>
<br>
<br>
Forwarded to kexec list:<br>
</font></tt><font size=3 color=blue><u><br>
</u></font><a href="http://lists.infradead.org/pipermail/kexec/2009-August/003474.html"><tt><font size=2 color=blue><u>http://lists.infradead.org/pipermail/kexec/2009-August/003474.html</u></font></tt></a><tt><font size=2><br>
<br>
----- "Chandan12 K" <chandan12.k@tcs.com> wrote:<br>
<br>
> Hi,<br>
> <br>
> I am little new in this mailing list. I just wondered if anybody could<br>
> help me regarding the vmcore file generation. I ran kexec on my x86_64<br>
> machine, and the /proc/vmcore file is created with zero size.<br>
> <br>
> However, even if I read the /dev/oldmem file, I am only able to read<br>
> till 16M. I guess I am only able to read till the 'X', where X is<br>
> crashkernel=Y@X.<br>
> <br>
> Moreover, My machine seems to have 32 bit user space and ofcourse,
64<br>
> bit kernel space.<br>
> <br>
> Appreciate any response.<br>
> <br>
> Chandan Kumar<br>
> ____________________________________________ =====-----=====-----=====<br>
> Notice: The information contained in this e-mail<br>
> message and/or attachments to it may contain<br>
> confidential or privileged information. If you are<br>
> not the intended recipient, any dissemination, use,<br>
> review, distribution, printing or copying of the<br>
> information contained in this e-mail message<br>
> and/or attachments to it are strictly prohibited. If<br>
> you have received this communication in error,<br>
> please notify us by reply e-mail or telephone and<br>
> immediately and permanently delete the message<br>
> and any attachments. Thank you <br>
> --<br>
> Crash-utility mailing list<br>
> Crash-utility@redhat.com<br>
> </font></tt><a href="https://www.redhat.com/mailman/listinfo/crash-utility"><tt><font size=2 color=blue><u>https://www.redhat.com/mailman/listinfo/crash-utility</u></font></tt></a><tt><font size=2><br>
<br>
--<br>
Crash-utility mailing list<br>
Crash-utility@redhat.com</font></tt><font size=3 color=blue><u><br>
</u></font><a href="https://www.redhat.com/mailman/listinfo/crash-utility"><tt><font size=2 color=blue><u>https://www.redhat.com/mailman/listinfo/crash-utility</u></font></tt></a><font size=1 color=white face="sans-serif"><br>
<br>
ForwardSourceID:NT0000987A </font><font size=3> </font><tt><font size=3><br>
=====-----=====-----=====<br>
Notice: The information contained in this e-mail<br>
message and/or attachments to it may contain <br>
confidential or privileged information. If you are <br>
not the intended recipient, any dissemination, use, <br>
review, distribution, printing or copying of the <br>
information contained in this e-mail message <br>
and/or attachments to it are strictly prohibited. If <br>
you have received this communication in error, <br>
please notify us by reply e-mail or telephone and <br>
immediately and permanently delete the message <br>
and any attachments. Thank you<br>
<br>
</font></tt><tt><font size=2><br>
_______________________________________________<br>
kexec mailing list<br>
kexec@lists.infradead.org</font></tt><font size=3 color=blue><u><br>
</u></font><a href=http://lists.infradead.org/mailman/listinfo/kexec><tt><font size=2 color=blue><u>http://lists.infradead.org/mailman/listinfo/kexec</u></font></tt></a><font size=3><br>
</font><font size=1 color=white face="sans-serif"><br>
ForwardSourceID:NT000098BE </font><font size=3> </font><font size=2 face="sans-serif"><br>
<br>
Chandan Kumar<br>
TCS Mumbai</font>
<br><tt><font size=3>=====-----=====-----=====<br>
Notice: The information contained in this e-mail<br>
message and/or attachments to it may contain <br>
confidential or privileged information. If you are <br>
not the intended recipient, any dissemination, use, <br>
review, distribution, printing or copying of the <br>
information contained in this e-mail message <br>
and/or attachments to it are strictly prohibited. If <br>
you have received this communication in error, <br>
please notify us by reply e-mail or telephone and <br>
immediately and permanently delete the message <br>
and any attachments. Thank you<br>
<br>
<br>
</font></tt><tt><font size=2>_______________________________________________<br>
kexec mailing list<br>
kexec@lists.infradead.org<br>
</font></tt><a href=http://lists.infradead.org/mailman/listinfo/kexec><tt><font size=2>http://lists.infradead.org/mailman/listinfo/kexec</font></tt></a><tt><font size=2><br>
</font></tt>
<br><font size=1 color=white face="sans-serif">ForwardSourceID:NT0000994A
</font>
<br><pre>=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
</pre>