We are using the linux kernel 2.4.18-14 for development
of a networking product and have used the lkcd for
generation of core dumps is case the linux kernel
crashes. The system has about one gig of RAM, but the
amount of memory visible to the kernel is passed as 128
MB to the kernel at boot time in the "mem" parameter
for lilo. Till now, the crash dumps that we were
getting were readable by the lcrash and everything was
running fine. Recently we have increased the amount of
memory visible to the kernel from 128 to 384 MB. After
this change the crash dumps created were unreadable by
the lcrash util and we get "invalid memory mapping"
errors in lcrash. Can u help us in here (like pointing
to some fix in lkcd or some special cfg to be done). I
am pasting the device stats and the /ect/sysconfig/dump
file in the mail.
Device stats:
Disk /dev/sda: 255 heads, 63 sectors, 4462 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 131 1052226 83 Linux
/dev/sda2 132 2742 20972857+ 83 Linux
/dev/sda3 2743 3264 4192965 82 Linux
swap (second swap)
/dev/sda4 3265 4462 9622935 f Win95
Ext'd (LBA)
/dev/sda5 3265 3786 4192933+ 83 Linux
/dev/sda6 3787 4047 2096451 83 Linux
/dev/sda7 4048 4462 3333456 82 Linux
swap (first swap)
------------------------------------------------------------------------------------------------------------
/etc/sysconfig/dump:
DUMP_ACTIVE=1
DUMPDEV=/dev/vmdump
DUMPDIR=/var/log/dump
DUMP_SAVE=1
DUMP_LEVEL=8
DUMP_FLAGS=0
DUMP_COMPRESS=0
PANIC_TIMEOUT=600
------------------------------------------------------------------------------
Seekig help desparately,
Anurag Mathur