Your message dated Sun, 19 Dec 2021 18:03:12 +0100
with message-id <[email protected]>
and subject line Re: Bug#998756: deal.ii: FTBFS on arm64: mpiexec noticed that
process rank 4 with PID 0 on node arm-ubc-02 exited on signal 4 (Illegal
instruction).
has caused the Debian Bug report #998756,
regarding deal.ii: FTBFS on arm64: mpiexec noticed that process rank 4 with PID
0 on node arm-ubc-02 exited on signal 4 (Illegal instruction).
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 [email protected]
immediately.)
--
998756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998756
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: deal.ii
Version: 9.3.0-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: [email protected]
Builds of deal.ii on arm64 currently fail with:
| cd /<<PKGBUILDDIR>>/obj-aarch64-linux-gnu/tests/quick_tests &&
/usr/bin/mpiexec -n 10 ./p4est.debug > p4est.debug-OK 2>&1 || ( echo
p4est.debug:\ RUN\ failed.\ Output: && cat p4est.debug-OK && rm p4est.debug-OK
&& exit 1 )
| p4est.debug: RUN failed. Output:
| --------------------------------------------------------------------------
| Primary job terminated normally, but 1 process returned
| a non-zero exit code. Per user-direction, the job has been aborted.
| --------------------------------------------------------------------------
| --------------------------------------------------------------------------
| mpiexec noticed that process rank 4 with PID 0 on node arm-ubc-02 exited on
signal 4 (Illegal instruction).
See
https://buildd.debian.org/status/fetch.php?pkg=deal.ii&arch=arm64&ver=9.3.0-1%2Bb1&stamp=1636272212&raw=0
I was able to reproduce it on amdahl, but I wasn't able to get any
useful information from gdb:
| Thread 1 received signal SIGILL, Illegal instruction.
| 0x0000000007919180 in ?? () from
/home/sramacher/deal.ii-9.3.0/obj-aarch64-linux-gnu/lib/aarch64-linux-gnu/libdeal.ii.g.so.9.3.0
| (gdb) bt full
| #0 0x0000000007919180 in ?? () from
/home/sramacher/deal.ii-9.3.0/obj-aarch64-linux-gnu/lib/aarch64-linux-gnu/libdeal.ii.g.so.9.3.0
| No symbol table info available.
| #1 0x000000000556ce68 in ?? () from
/home/sramacher/deal.ii-9.3.0/obj-aarch64-linux-gnu/lib/aarch64-linux-gnu/libdeal.ii.g.so.9.3.0
| No symbol table info available.
| #2 0x3f81111167a4d017 in ?? ()
| No symbol table info available.
| Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On 2021-11-07 18:39:10 +0100, Sebastian Ramacher wrote:
> Source: deal.ii
> Version: 9.3.0-1
> Severity: serious
> Tags: ftbfs sid bookworm
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: [email protected]
>
> Builds of deal.ii on arm64 currently fail with:
> | cd /<<PKGBUILDDIR>>/obj-aarch64-linux-gnu/tests/quick_tests &&
> /usr/bin/mpiexec -n 10 ./p4est.debug > p4est.debug-OK 2>&1 || ( echo
> p4est.debug:\ RUN\ failed.\ Output: && cat p4est.debug-OK && rm
> p4est.debug-OK && exit 1 )
> | p4est.debug: RUN failed. Output:
> | --------------------------------------------------------------------------
> | Primary job terminated normally, but 1 process returned
> | a non-zero exit code. Per user-direction, the job has been aborted.
> | --------------------------------------------------------------------------
> | --------------------------------------------------------------------------
> | mpiexec noticed that process rank 4 with PID 0 on node arm-ubc-02 exited on
> signal 4 (Illegal instruction).
>
> See
> https://buildd.debian.org/status/fetch.php?pkg=deal.ii&arch=arm64&ver=9.3.0-1%2Bb1&stamp=1636272212&raw=0
>
> I was able to reproduce it on amdahl, but I wasn't able to get any
> useful information from gdb:
> | Thread 1 received signal SIGILL, Illegal instruction.
> | 0x0000000007919180 in ?? () from
> /home/sramacher/deal.ii-9.3.0/obj-aarch64-linux-gnu/lib/aarch64-linux-gnu/libdeal.ii.g.so.9.3.0
> | (gdb) bt full
> | #0 0x0000000007919180 in ?? () from
> /home/sramacher/deal.ii-9.3.0/obj-aarch64-linux-gnu/lib/aarch64-linux-gnu/libdeal.ii.g.so.9.3.0
> | No symbol table info available.
> | #1 0x000000000556ce68 in ?? () from
> /home/sramacher/deal.ii-9.3.0/obj-aarch64-linux-gnu/lib/aarch64-linux-gnu/libdeal.ii.g.so.9.3.0
> | No symbol table info available.
> | #2 0x3f81111167a4d017 in ?? ()
> | No symbol table info available.
> | Backtrace stopped: previous frame identical to this frame (corrupt stack?)
9.3.0-1+b2 built fine
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
--- End Message ---
