Apparently having the kernel image debug package installed is a good
idea when trying to do anything with crash dumps... After installing the
~2GB (unpacked) package I was able to use the crash utility to analyze
(to a degree) the crash dump file made by kdump-tools, however I am
unable to extract the kernel log from the dump.
When I run the 'log' command within crash I get this message:
"log: WARNING: log buf data structure(s) have changed"
I can, however, get a backtrace and the process status information from
the dump. If you think it would be useful, I can output what I am able
to get from crash to a file to send to you for you to look at.
Also, I have a few questions:
1) Is there any way at all to give the crash kernel more memory to work
with? kdump-tools does not work if I specify an amount greater than 128M
in the bootloader config file (the system does not reboot into the crash
kernel), which seems unnecessarily small for a system with 4GB of memory
available, and it seems like the small amount of memory available slows
things down considerably.
2) How long should the crash dump collection process normally take? I've
noticed that it usually takes about 4 or 5 minutes after the system
finishes rebooting for the dump and dmesg files to show up in the crash
dump folder specified (prior to which there's only one file,
dump_incomplete), however the makedumpfile process seems to continue
running even after 5 hours (watching it with top).
3) Is the system supposed to boot as normal when booting into the crash
kernel to collect the crash dump? I ask, because mine does, and the
severely limited amount of memory available doesn't seem to allow for a
full boot. (I suspect I may need to specifically tell kdump-tools to
boot into a more suitable runlevel, as it doesn't appear to do so on its
own.)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
