Hi Kevin, Thank you for reporting. I guess that the problem depends on kernel configuration, and I want to reproduce it on my machine for investigating. Could you send me your kernel .config file ? And please let me know the kernel version. Thanks Ken'ichi Ohmichi Worth, Kevin wrote: > Hello, > > I have a couple errors that also happened on 1.2.6 and I wondered if anyone might have a suggestion why. > > The one thing I know might be strange about my system is that my first kernel (the one that panics) is compiled with CONFIG_VMSPLIT_1G, meaning that it is set to have 3GB of kernel space and 1GB of user space. I believe this does things to CONFIG_PAGE_OFFSET, but the depth of my kernel knowledge is not so great. > > > # makedumpfile -E -d 31 -i /boot/vmcoreinfo vmcore dumpoutput2 > check_release: /boot/vmcoreinfo and vmcore don't match. > > makedumpfile Failed. > > The release numbers of the vmcore and vmcoreinfo files should be identical. This happens if I specify anything greater than "-d 1". > > I tried a quick addition to the printf to include the values that generate the above error. It looks like "system_utsname.release" is NULL coming into the strcmp on line 340 of makedumpfile.c . Unfortunately I don't know enough about the kernel to go further than this. > > > Additionally (potentially a separate issue), on an identical piece of hardware, but with 4GB of memory instead of 2GB, using "-d 1", I get the following error: > > Excluding zero pages : [ 38 %] readmem: Can't seek the dump memory(/proc/vmcore). Invalid argument > create_2nd_bitmap: Can't exclude pages filled with zerocreate_2nd_bitmap: for creating an ELF dumpfile. > > makedumpfile Failed. > > I can cp the file just fine and it loads up in crash, but I can't seem to use makedumpfile to trim the vmcore down at all on this system with more memory. > > Any suggestions? Thanks! > > > Kevin Worth > Network Security > Software Engineer > kevin.worth at hp.com<mailto:kevin.worth at hp.com> > ph 916.785.4528 > fx 916.785.1196 > > [cid:image003.jpg at 01C91999.C5AF4AE0]
