<br><font size=2 face="sans-serif">Hi,</font>
<br>
<br><font size=2 face="sans-serif">Adding boot logs</font>
<br>
<br><font size=2 face="sans-serif">NET: Registered protocol family 1</font>
<br><font size=2 face="sans-serif">audit: initializing netlink socket (disabled)</font>
<br><font size=2 face="sans-serif">type=2000 audit(1250069944.104:1): initialized</font>
<br><font size=2 face="sans-serif">VFS: Disk quotas dquot_6.5.1</font>
<br><font size=2 face="sans-serif">Dquot-cache hash table entries: 512
(order 0, 4096 bytes)</font>
<br><font size=2 face="sans-serif">Warning: Core image elf header is notsane</font>
<br><font size=2 face="sans-serif">Kdump: vmcore not initialized</font>
<br><font size=2 face="sans-serif">Registering unionfs 2.2-mm</font>
<br><font size=2 face="sans-serif">msgmni has been set to 90</font>
<br><font size=2 face="sans-serif">io scheduler noop registered</font>
<br><font size=2 face="sans-serif">io scheduler anticipatory registered<br>
</font>
<br>
<br><font size=2 face="sans-serif">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>
<br>
<br><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>
<br>
<br><font size=2 face="sans-serif">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>
<br>
<br>
<br><font size=2 face="sans-serif">Command line for the Primary kernel
: root=/dev/nfs rw console=ttyS0,115200 ip=::::::dhcp crashkernel=64M@16M</font>
<br>
<br><font size=2 face="sans-serif">kexec command used : kexec -p bzImage
--append="root=/dev/nfs rw console=ttyS0,115200 ip=::::::dhcp selinux=0
noacpi maxcpus=1"</font>
<br>
<br><font size=2 face="sans-serif">Kconfig options :</font>
<br>
<br><font size=2 face="sans-serif">CONFIG_CRASH_DUMP=y</font>
<br><font size=2 face="sans-serif">CONFIG_PHYSICAL_START=0x200000</font>
<br><font size=2 face="sans-serif">CONFIG_RELOCATABLE=y</font>
<br><font size=2 face="sans-serif">CONFIG_PHYSICAL_ALIGN=0x200000<br>
</font>
<br><font size=2 face="sans-serif">Please suggest.</font>
<br>
<br><font size=2 face="sans-serif">Shukriya,</font>
<br>
<br><font size=2 face="sans-serif">Chandan</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Dave Anderson <anderson@redhat.com></b>
</font>
<br><font size=1 face="sans-serif">Sent by: crash-utility-bounces@redhat.com</font>
<p><font size=1 face="sans-serif">08/12/2009 07:39 PM</font>
<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=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">"Discussion list for crash utility
usage, maintenance and development"
<crash-utility@redhat.com></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>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2><br>
Forwarded to kexec list:<br>
<br>
</font></tt><a href="http://lists.infradead.org/pipermail/kexec/2009-August/003474.html"><tt><font size=2>http://lists.infradead.org/pipermail/kexec/2009-August/003474.html</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>https://www.redhat.com/mailman/listinfo/crash-utility</font></tt></a><tt><font size=2><br>
<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>https://www.redhat.com/mailman/listinfo/crash-utility</font></tt></a><tt><font size=2><br>
</font></tt>
<br><font size=1 color=white face="sans-serif">ForwardSourceID:NT0000987A
</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>