Dmesg not being dumped

Dave Anderson anderson at
Mon Aug 24 06:03:32 PDT 2015

----- Original Message -----
> 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...

I'm not sure what you mean.  Similar to the saving of the vmcore file, the
script directs the output of vmcore-dmesg into vmcore-dmesg-incomplete.txt.
Then, only if vmcore-dmesg returns an exit status of 0, the script will 
rename the file to vmcore-dmesg.txt.

More information about the kexec mailing list