From: Nikolay Borisov <kernel@kyup.com>
To: Dave Anderson <anderson@redhat.com>
Cc: kexec@lists.infradead.org
Subject: Re: Dmesg not being dumped
Date: Fri, 21 Aug 2015 11:09:58 +0300 [thread overview]
Message-ID: <55D6DCD6.8050000@kyup.com> (raw)
In-Reply-To: <1497907178.20184517.1440075877293.JavaMail.zimbra@redhat.com>
On 08/20/2015 04:04 PM, Dave Anderson wrote:
> The vmcoreinfo data strings were initially located in an ELF note in /proc/vmcore.
> When makedumpfile -c was run on /proc/vmcore, it copied those ELF notes into the
> compressed kdump header, and you have dumped them above.
>
> So it seems to be an issue with vmcore-dmesg. If you change the core_collector
> variable to "cp" or "scp", it will copy /proc/vmcore unmodified to the target
> location. Then you can run vmcore-dmesg on that file to debug it.
This is very, very odd. Obtaining a raw vmcore with cp and then running
vmcore-dmesg does show the dmesg log. But at the same time, the
vmcore-dmesg.txt file is empty and its name is
vmcore-dmesg-incomplete.txt...
>
> Dave
>
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2015-08-21 8:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5.1440010802.20553.kexec@lists.infradead.org>
2015-08-19 20:38 ` Dmesg not being dumped Dave Anderson
2015-08-20 6:52 ` Nikolay Borisov
2015-08-20 13:04 ` Dave Anderson
2015-08-21 8:09 ` Nikolay Borisov [this message]
2015-08-24 13:03 ` Dave Anderson
2015-08-24 14:17 ` Nikolay Borisov
2015-08-19 6:21 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
2015-08-19 14:08 ` Minfei Huang
2015-08-19 14:09 ` 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=55D6DCD6.8050000@kyup.com \
--to=kernel@kyup.com \
--cc=anderson@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.