On Fri, Jan 12, 2007 at 09:52:36AM +0100, Welterlen Benoit wrote: > TCP: Hash tables configured (established 16384 bind 8192) > TCP reno registered > checking if image is initramfs... it is > Freeing initrd memory: 3776kB freed > perfmon: version 2.0 IRQ 238 > perfmon: Montecito PMU detected, 27 PMCs, 35 PMDs, 12 counters (47 bits) > PAL Information Facility v0.5 > perfmon: added sampling format default_format > perfmon_default_smpl: default_format v2.0 registered > Total HugeTLB memory allocated, 0 > VFS: Disk quotas dquot_6.5.1 > Dquot-cache hash table entries: 8192 (order 0, 65536 bytes) > _*Kdump: vmcore not initialized*_ > io scheduler noop registered > io scheduler anticipatory registered (default) > io scheduler deadline registered > io scheduler cfq registered > EFI Time Services Driver v0.4 > [drm] Initialized drm 1.1.0 20060810 > Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing > disabled > ... > > So I have no more error messages. The error can occurs anywhere. > I have dumped the old memory at the trusted elfcorehdr : 1572608K. > How can I analyse this data ? Where are define the ELF headers ? >
Elf headers are created in user space by kexec-tools utility. I am not sure where the problem is. I think to begin with you can put some printk() messages in fs/proc/vmcore.c file. Especially the code under parse_crash_elf_headers(). One suspect is read_from_oldmem(e_ident, EI_NIDENT, &addr, 0); Due to some problem reading the ELF header might have failed. If not then you need to continue to parse_crash_elf64_headers() to trace from where it is returning with an error code. Thanks Vivek _______________________________________________ fastboot mailing list [email protected] https://lists.osdl.org/mailman/listinfo/fastboot
