Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Anand <panand@redhat.com>
To: Nikolay Borisov <kernel@kyup.com>
Cc: kexec@lists.infradead.org, Baoquan He <bhe@redhat.com>
Subject: Re: Dmesg not being dumped
Date: Fri, 21 Aug 2015 10:19:12 +0530	[thread overview]
Message-ID: <20150821044912.GC26132@dhcppc13.redhat.com> (raw)
In-Reply-To: <55D4641D.70902@kyup.com>

Hi Nikolay,

On 19/08/2015:02:10:21 PM, Nikolay Borisov wrote:
> 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

Are you sure if you have 2.0.9. I see 2.0.9 is dated 09 Feb 2015.

commit 8e762175d295aad08a1cc62d6394e8285f225a40
Author: Simon Horman <horms@verge.net.au>
Date:   Mon Feb 9 14:33:24 2015 +0900

    kexec-tools 2.0.9


> >> been compiled with debugging info so the respective symbol should be
> >> exported but apparently it is not. Any ideas how to debug that?

Can you please cross check that you have following patch in your kexec-tool. If
you have that patch, then its really strange that you see this issue.

commit c96b723e17eb4af689de494b636d8bded4b98c88
Author: Vivek Goyal <vgoyal@redhat.com>
Date:   Thu May 22 10:43:14 2014 -0400

    vmcore-dmesg: Handle struct log to struct printk_log renaming

~Pratyush    

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2015-08-21  4:49 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 [this message]
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=20150821044912.GC26132@dhcppc13.redhat.com \
    --to=panand@redhat.com \
    --cc=bhe@redhat.com \
    --cc=kernel@kyup.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