From: Nikolay Borisov <kernel@kyup.com>
To: Minfei Huang <mhuang@redhat.com>
Cc: kexec@lists.infradead.org
Subject: Re: Dmesg not being dumped
Date: Wed, 19 Aug 2015 16:40:56 +0300 [thread overview]
Message-ID: <55D48768.4020207@kyup.com> (raw)
In-Reply-To: <20150819131302.GA11631@dhcp-128-25.nay.redhat.com>
On 08/19/2015 04:13 PM, Minfei Huang wrote:
> Hi. Nikolay.
Hi
>
> Does kexec-tools work for original rhel kernel, like 3.10.0-xxx. Also do
Unfortunately I canno test with an official rhel kernel since we are not
using those. Also, the problem is not that kexec is not working at all,
but just that the dmesg log is not being saved in the vmcore-dmesg.txt
file. Here are the relevant portion of the my .config which deal with
debug info:
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_INFO_REDUCED is not set
# CONFIG_DEBUG_INFO_SPLIT is not set
# CONFIG_DEBUG_INFO_DWARF4 is not set
The failures is happening (according to my reading of the vmcore-dmesg.c
file) here:
+ if (!log_sz) {
+ fprintf(stderr, "Missing the struct log size export\n");
+ exit(64);
+ }
And log_size is being set here:
str = "SIZE(printk_log)=";
if (memcmp(str, pos, strlen(str)) == 0)
log_sz = strtoull(pos + strlen(str), NULL, 10);
The pertinent question I guess is why this string cannot be found in the
resulting vmcore image. I just tried with kexec 2.0.10 and the result is
the same.
> you specify the config to build the kernel? It is appropriate if you can
> paste the config related to the kexec.
>
> Thanks
> Minfei
>
> On 08/19/15 at 09:21am, Nikolay Borisov wrote:
>> Hello,
>>
>> I've recently noticed that when creating crashdumps the dmesg is not
>> being saved. The error reported is this: "Missing the struct log size
>> export". I've tested with both kernel 4.1.1 and 3.12.28. My version of
>> kexec tools is : kexec-tools 2.0.9 released 04 June 2015. The kernel has
>> been compiled with debugging info so the respective symbol should be
>> exported but apparently it is not. Any ideas how to debug that?
>>
>> [Please CC me as I'm not subscribed to the mailing list.]
>>
>> Regards,
>> Nikolay
>>
>> _______________________________________________
>> kexec mailing list
>> kexec@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/kexec
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2015-08-19 13:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 6:21 Dmesg not being dumped Nikolay Borisov
2015-08-19 9:02 ` Baoquan He
2015-08-19 11:10 ` Nikolay Borisov
2015-08-21 4:49 ` Pratyush Anand
2015-08-21 6:28 ` Dave Young
2015-08-19 13:13 ` Minfei Huang
2015-08-19 13:40 ` Nikolay Borisov [this message]
2015-08-19 14:08 ` Minfei Huang
2015-08-19 14:09 ` Nikolay Borisov
[not found] <mailman.5.1440010802.20553.kexec@lists.infradead.org>
2015-08-19 20:38 ` Dave Anderson
2015-08-20 6:52 ` Nikolay Borisov
2015-08-20 13:04 ` Dave Anderson
2015-08-21 8:09 ` Nikolay Borisov
2015-08-24 13:03 ` Dave Anderson
2015-08-24 14:17 ` Nikolay Borisov
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=55D48768.4020207@kyup.com \
--to=kernel@kyup.com \
--cc=kexec@lists.infradead.org \
--cc=mhuang@redhat.com \
/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