makedumpfile failed for 2.6.36-rc2
caiqian at redhat.com
Wed Sep 1 01:16:20 EDT 2010
----- "Ken'ichi Ohmichi" <oomichi at mxs.nes.nec.co.jp> wrote:
> Hi Cai,
> On Tue, 31 Aug 2010 04:29:02 -0400 (EDT)
> CAI Qian <caiqian at redhat.com> wrote:
> > > > > I'd like to reproduce the same problem on my machine,
> > > > > could you please send your kernel .config file ?
> > > >
> > > > Attached.
> > >
> > > Thank you.
> > > The linux-2.6.36-rc2 kernel is building now with your .config
> > > After building, I will test makedumpfile on the kernel.
> I built linux-2.6.36-rc2 kernel with your .config file, but it gets a
> panic while 1st-kernel is booting. I'm not digging the cause.
Another pointer is that 2.6.35-rc1 worked fine for me, while 2.6.35-rc4 and beyond started to fail.
> So I built linux-2.6.36-rc2 kernel with my .config file instead, and
> can boot and the kdump is successful. But makedumpfile runs
> so I cannot reproduce the problem which you reported.
> I will try linux-2.6.36-rc3 kernel with your .config file later.
> BTW, do you have the way how I get the compressed copy of your
> /proc/vmcore ?
> I'd like to research the problem directly.
> > > >> readmem: Can't seek the dump memory(/proc/vmcore). Invalid
> > > argument
> > >
> > > lseek(2) failed with "Invalid argument", so the problem may be due
> > > an
> > > invalid offset. I'd like to know its value, so can you try the
> > > attached
> > > patch in the condition makedumpfile fails ?
> > > And can you send the output of `readelf -a /proc/vmcore` ?
> > Here you go,
> > readmem: Can't seek the dump memory(/proc/vmcore). Invalid argument
> > readmem: type_addr: 0, addr:ffff880480027000, size:32
> The above output does not include the offset value which should be
> printed by my previous patch. Could you check the patch is applied
> to right place (lseek(2) call in readmem() function) ?
> In addiction, could you operate makedumpfile with "-D" option ?
> Ken'ichi Ohmichi
> kexec mailing list
> kexec at lists.infradead.org
More information about the kexec