On Mon, Sep 10, 2007 at 11:35:21AM -0700, Randy Dunlap wrote: > On Fri, 7 Sep 2007 17:57:46 +0900 Ken'ichi Ohmichi wrote: > > > Hi, > > > I released a new makedumpfile (version 1.2.0) with vmcoreinfo support. > > I updated the patches for linux and kexec-tools. > > > > PATCH SET: > > [1/2] [linux-2.6.22] Add vmcoreinfo > > The patch is for linux-2.6.22. > > The patch adds the vmcoreinfo data. Its address and size are output > > to /sys/kernel/vmcoreinfo. > > > > [2/2] [kexec-tools] Pass vmcoreinfo's address and size > > The patch is for kexec-tools-testing-20070330. > > (http://www.kernel.org/pub/linux/kernel/people/horms/kexec-tools/) > > kexec command gets the address and size of the vmcoreinfo data from > > /sys/kernel/vmcoreinfo, and passes them to the second kernel through > > ELF header of /proc/vmcore. When the second kernel is booting, the > > kernel gets them from the ELF header and creates vmcoreinfo's PT_NOTE > > segment into /proc/vmcore. > > Hi, > When using the vmcoreinfo patches, what tool(s) are available for > analyzing the vmcore (dump) file? E.g., lkcd or crash or just gdb? > > gdb works for me, but I tried to use crash (4.0-4.6 from > http://people.redhat.com/anderson/) and crash complained: > > crash: invalid kernel virtual address: 0 type: "cpu_pda entry" > > Should crash work, or does it need to be modified? > Hi Randy, Crash should just work. It might broken on latest kernel. Copying it to crash-utility mailing list. Dave will be able to tell us better. > This is on a 2.6.23-rc3 kernel with vmcoreinfo patches and a dump file > with -l 31 (dump level 31, omitting all possible pages). > Thanks Vivek -- Crash-utility mailing list Crash-utility@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/crash-utility