Your message dated Tue, 5 Feb 2013 23:08:15 -0800 with message-id <20130206070815.ga15...@callisto.home.lan> and subject line Re: Bug#696386: makedumpfile fails with elf_readall error : more information has caused the Debian Bug report #696386, regarding makedumpfile fails with elf_readall error to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 696386: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696386 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: makedumpfile Version: 1.5.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Testing packaging of new 1.5.1 version of makedumpfile. * What exactly did you do (or not do) that was effective (or ineffective)? Ran normal kernel panic test. * What was the outcome of this action? The following output came out when makedumpfile tried to run : Starting kdump-tools: [info] running makedumpfile -c -d 31 -x /usr/lib/debug/boot/vmlinux-3.2.0-4-amd64 /proc/vmcore /var/crash/201212201000/d ump-incomplete. makedumpfile: elf_readall.c:94: __libelf_readall: Unexpected error: Resource deadlock avoided. /usr/sbin/kdump-config: line 387: 2243 Aborted makedumpfile $MAKEDUMP_ARGS $vmcore_file $KDUMP_CORETEMP [FAIL] kdump-tools: makedumpfile failed, falling back to 'cp' ... failed! Since this was while testing makedumpfile 1.5.1 for packaging, I tested the current packaged 1.5.0-1 which tested successfully previously and it also fails. This might be a regression from another package. It is important to note that makedumpfile correctly runs on the dump file once the system is back to multi-user. * What outcome did you expect instead? makedumpfile correctly process the /proc/vmcore file -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages makedumpfile depends on: ii libbz2-1.0 1.0.6-4 ii libc6 2.13-37 ii libdw1 0.153-2 ii libelf1 0.153-2 ii perl 5.14.2-16 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages makedumpfile recommends: ii crash 6.1.0-1 ii kexec-tools 1:2.0.3-1 makedumpfile suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---tag 696386 + unreproducible thanks On Thu, Jan 31, 2013 at 05:46:18PM +0100, Bouchard Louis wrote: > Hello John, > > Well this is what happen when juggling with too many distros. I might > have tested with a .deb package built on Ubuntu instead of my normal > Debian/Sid build VM. > > After rebuilding the package on Sid, the makedumpfile command works as > expected. You can mark this bug as invalid. Tagging it unreproducible and closing. :) -- John Wright <j...@debian.org>
--- End Message ---
