From: Nikolay Borisov <kernel@kyup.com>
To: Baoquan He <bhe@redhat.com>
Cc: kexec@lists.infradead.org
Subject: Re: Dmesg not being dumped
Date: Wed, 19 Aug 2015 14:10:21 +0300 [thread overview]
Message-ID: <55D4641D.70902@kyup.com> (raw)
In-Reply-To: <20150819090202.GF19950@dhcp-128-28.nay.redhat.com>
Hi,
On 08/19/2015 12:02 PM, Baoquan He wrote:
> 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?
>
> That would be more helpful if you can attach the 1st kernel and kdump
> kernel console log.
I just tested with 4.1.6 with the same result. I'm sending you a link to
the bzImage in question
http://georgi.unixsol.org/cruft/tmp/bzImage-4.1.6-clouder1 ( I assume
you meant the bzImage, if you need I can provide the vmlinux as well).
Unfortunately, I couldn't figure how to obtain the log of kdump in
textual format (and didn't want to send pictures). Here are the 3
relevant lines (from memory):
Saving vmcore-dmesg.txt
Missing the struct log size export
Error saving vmcore-dmesg.txt.
Yet, when I load the crashdump inside the 'crash' utility and invoke the
'log' command the dmesg log is there. Whereas the
vmcore-dmesg-incomplete.txt is empty.
>
>>
>> [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 11:10 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 [this message]
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
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=55D4641D.70902@kyup.com \
--to=kernel@kyup.com \
--cc=bhe@redhat.com \
--cc=kexec@lists.infradead.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