Package: makedumpfile Version: 1.5.4-1 Severity: grave Justification: renders package unusable
Dear Maintainer, There seems to be a serious issue with makedumpfile that causes it to fail to dump the kernel log when collecting crash dump information. Instead, the program continues to run indefinitely, continually appending the line "[ 0.000000] " to the file as it seems to attempt to dump the log, which, if left alone for any considerable length of time, can rapidly result in a very large, entirely useless dmesg dump file. I have been trying to collect crash dump information for a crash that's triggered whenever Folding@Home's FahCore_a4 attempts to resume an in-progress work unit, however, every crash dump I've collected has had this problem. The main dump file seems to be dumped without a problem (though crash identifies it as a partial dump, possibly due to the kernel log being dumped into a separate file). I hope you can look into this issue and hopefully it can be sorted out soon. -- System Information: Debian Release: jessie/sid APT prefers experimental APT policy: (650, 'experimental'), (650, 'unstable'), (600, 'testing'), (500, 'saucy-updates'), (500, 'saucy-security'), (500, 'saucy') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-rc4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages makedumpfile depends on: ii libbz2-1.0 1.0.6-5 ii libc6 2.17-92 ii libdw1 0.156-1 ii libelf1 0.156-1 ii perl 5.14.2-21 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages makedumpfile recommends: ii crash 7.0.1-3 ii kexec-tools 1:2.0.3-4 makedumpfile suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
