On 12 May 2017 at 15:30, Louis Bouchard <bouchard.lo...@gmail.com> wrote: > Hello, > > Well, this is to be expected as the postinst script will only change the > target of the symlink if the architecture is ppc64EL and not ppc64LE ( > EL != LE). > > Now if both are interchangeable (I must admit my ignorance of this > architecture), I don't mind fixing the script to apply to both EL and > LE. >
linux / GNU toolchain / etc use the names "le" for the little endian architectures. Debian / dpkg architecture tags use "el" as a tongue-in-cheeck pun that it is endian little ordered. Thus there must be a missmatch of values: dpkg vs toolchain architecture: $ dpkg-architecture -appc64el dpkg-architecture: warning: specified GNU system type powerpc64le-linux-gnu does not match CC system type x86_64-linux-gnu, try setting a correct CC environment variable ... DEB_HOST_ARCH=ppc64el DEB_HOST_ARCH_BITS=64 DEB_HOST_ARCH_CPU=ppc64el DEB_HOST_ARCH_ENDIAN=little DEB_HOST_ARCH_OS=linux DEB_HOST_GNU_CPU=powerpc64le DEB_HOST_GNU_SYSTEM=linux-gnu DEB_HOST_GNU_TYPE=powerpc64le-linux-gnu DEB_HOST_MULTIARCH=powerpc64le-linux-gnu ... Note the ARCH tag which is dpkg tag, and the GNU_ tags which are what are used by binutils/gcc/etc tooling. CPU tag is what kernel uses in uname -a. -- Regards, Dimitri. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1676884 Title: kdump-tools uses the wrong crashkernel command line parameter in ppc64le Status in The Ubuntu-power-systems project: New Status in makedumpfile package in Ubuntu: New Bug description: == Comment: #0 - Thiago Jung Bauermann <thiag...@br.ibm.com> - 2017-03-24 11:44:39 == ---Problem Description--- kdump-tools uses the wrong crashkernel command line parameter in ppc64le: u1704le?? grep crashkernel /boot/grub/grub.cfg linux /boot/vmlinux-4.10.0-13-generic root=UUID=2d6f73c7-b463-4f02-9ec4-8d4afed0635d ro crashkernel=384M-:128M 128M of reserved memory is too small for ppc64le. That happens because /etc/default/grub.d/kdump-tools.cfg links to the wrong file: u1704le?? ls -l /etc/default/grub.d/ total 8.0K lrwxrwxrwx 1 root root 39 Mar 24 13:34 kdump-tools.cfg -> /etc/default/grub.d/kdump-tools.default -rw-r--r-- 1 root root 80 Jan 5 08:07 kdump-tools.default -rw-r--r-- 1 root root 137 Jan 5 08:07 kdump-tools..ppc64el u1704le?? As can be seen, it should be pointing to kdump-tools..ppc64el but isn't. Also, kdump-tools..ppc64el has two dots in it. That doesn't seem right. Possibly just a cosmetic issue, but it would be nice if that was fixed. Contact Information = thiag...@br.ibm.com ---uname output--- Linux u1704le 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = Any ppc64le machine. In this case, a KVM guest hosted on an 8286-42A. ---Debugger--- A debugger is not configured ---Steps to Reproduce--- sudo apt intall kdump-tools Select 'Yes' when asked whether kdump should be enabled. Userspace tool common name: kdump The userspace tool has the following bit modes: 64 bit Userspace rpm: kdump-tools Userspace tool obtained from project website: na *Additional Instructions for thiag...@br.ibm.com: -Attach ltrace and strace of userspace application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1676884/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
