1. Forum
  2. Usenet
  3. LINUX.DEBIAN.PORTS.SPARC

  • mmdebstrap'ping sparc64 failure on amd64 host

    From John Paul Adrian Glaubitz@21:1/5 to Ryutaroh Matsumoto on Mon Nov 30 02:00:02 2020
    On 11/30/20 1:02 AM, Ryutaroh Matsumoto wrote:
    Specifically,

    mmdebstrap --include=debian-ports-archive-keyring --architectures=sparc64 sid /tmp/some-dir - <<EOF
    deb http://deb.debian.org/debian-ports/ sid main
    deb http://deb.debian.org/debian-ports/ unreleased main
    EOF

    fails with

    Preparing to unpack .../perl-base_5.32.0-5_sparc64.deb ...
    *** longjmp causes uninitialized stack frame ***: terminated

    I wonder if it is caused by incomplete emulation by qemu-user-static package, but I am unsure.

    I have not obvserved that particular issue on real hardware for Perl, but I have
    seen OpenJDK Zero crash that way on sparc64 on real hardware.

    Adrian

    --
    .''`. John Paul Adrian Glaubitz
    : :' : Debian Developer - glaubitz@debian.org
    `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
    `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ryutaroh Matsumoto@21:1/5 to All on Mon Nov 30 01:40:01 2020
    Hi everyone,

    I am investigating how we can extend autopkgtest-virt-qemu's support to
    more architectures, and found that creation of a root filesystem of sparc64
    by mmdebstrap on an Debian testing amd64 host fails.
    John told me that I should report it to this list at https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/97#note_205337

    Specifically,

    mmdebstrap --include=debian-ports-archive-keyring --architectures=sparc64 sid /tmp/some-dir - <<EOF
    deb http://deb.debian.org/debian-ports/ sid main
    deb http://deb.debian.org/debian-ports/ unreleased main
    EOF

    fails with

    Preparing to unpack .../perl-base_5.32.0-5_sparc64.deb ...
    *** longjmp causes uninitialized stack frame ***: terminated

    I wonder if it is caused by incomplete emulation by qemu-user-static package, but I am unsure.

    Best regards, Ryutaroh Matsumoto

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Gregor Riepl@21:1/5 to All on Mon Nov 30 14:00:02 2020
    fails with

    Preparing to unpack .../perl-base_5.32.0-5_sparc64.deb ...
    *** longjmp causes uninitialized stack frame ***: terminated

    I wonder if it is caused by incomplete emulation by qemu-user-static package, but I am unsure.

    Searching for that error reveals a possibly similar issue with the
    native DNS resolver in libcurl[1]. I'm not sure if this is applicable to
    the case here, but it could be a general longjump/signal
    handler/multithreading issue rather than something on the machine level.

    Other results indicate that the error message is generated by the libc
    stack checker when _FORTIFY_SOURCE is 2. Maybe there is some mishandling
    going on here.

    A backtrace would be helpful.

    [1] https://curl.se/mail/lib-2008-09/0197.html

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)