[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#993162: marked as done (libgcc-s1: i386 (Geode LX): latest push to Bookwork produces multiple sig ILL)

Your message dated Thu, 02 Sep 2021 14:34:23 +0000
with message-id <E1mLnnL-000Ajo-1r@fasolo.debian.org>
and subject line Bug#993162: fixed in gcc-11 11.2.0-4
has caused the Debian Bug report #993162,
regarding libgcc-s1: i386 (Geode LX): latest push to Bookwork produces multiple sig ILL
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 owner@bugs.debian.org
immediately.)


-- 
993162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993162
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libc6
Version: 2.31-17
Severity: grave
Justification: renders package unusable

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Since 2.31-17 trickled into Bookworm, a number of executables (including APT and GDB) die with sig ILL. An example:

$ sudo coredumpctl debug 1011
           PID: 1011 (apt-get)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 4 (ILL)
     Timestamp: Sat 2021-08-28 11:00:34 EEST (3min 22s ago)
  Command Line: apt-get --quiet --quiet update
    Executable: /usr/bin/apt-get
 Control Group: /user.slice/user-1000.slice/session-4.scope
          Unit: session-4.scope
         Slice: user-1000.slice
       Session: 4
     Owner UID: 1000 (perkelix)
       Boot ID: 77dfa6eb16584c02b84de4e2b8feb781
    Machine ID: 1063a9d1fb9df6e371ea9f94491345ed
      Hostname: geode
       Storage: /var/lib/systemd/coredump/core.apt-get.0.77dfa6eb16584c02b84de4e2b8feb781.1011.1630137634000000.zst
       Message: Process 1011 (apt-get) of user 0 dumped core.
                
                Stack trace of thread 1011:
                #0  0x00000000b7ad2ed0 __cpu_indicator_init (libgcc_s.so.1 + 0x2ed0)
                #1  0x00000000b7faf02c call_init (ld-linux.so.2 + 0x1102c)
                #2  0x00000000b7faf132 call_init (ld-linux.so.2 + 0x11132)
                #3  0x00000000b7f9f0fa _dl_start_user (ld-linux.so.2 + 0x10fa)

Stack trace for other executables show the same cause as above.

$ cat /proc/cpuinfo 
processor	: 0
vendor_id	: AuthenticAMD
cpu family	: 5
model		: 10
model name	: Geode(TM) Integrated Processor by AMD PCS
stepping	: 2
cpu MHz		: 497.996
cache size	: 128 KB
physical id	: 0
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 0
initial apicid	: 0
fdiv_bug	: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 1
wp		: yes
flags		: fpu de pse tsc msr cx8 sep pge cmov clflush mmx mmxext 3dnowext 3dnow cpuid 3dnowprefetch vmmcall
bugs		: sysret_ss_attrs spectre_v1 spectre_v2 spec_store_bypass
bogomips	: 995.99
clflush size	: 32
cache_alignment	: 32
address sizes	: 32 bits physical, 32 bits virtual
power management:

Feel free to reassign as appropriate.

Cheers!
Martin-Éric

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmEp8TIACgkQrh+Cd8S0
17YLcQ/9GU6jypIgCKXTN48qzbAbDZYiGnKmsRJ7vXmmKZOLH75SWsmT++NJi+lf
SPe0JCKRhBuRVBx+0kIRZ89KaTn/L4fWXMb1UF9wLQQEkvQfj0Vbnwi5lgQuLTTw
x99Zouh9s9OtRQ+SZhQnuTts2SeiYLN9xkmCVPlK4LUSYuNfXJ60dOmmCXvgzpoQ
7BAZ43XciA5jU2+SmK506oFCVjNQWstgncRKMVj2++apdXiSZXZ1cP2RLfIpurLU
OH6Ke3iifeOgcNuhPbLfva5rrdwFIEo0mEKzNzgpzIsOzBjow2EAmLehr24iAcoy
BkxGuTdGeUtF/rOQFEwhtPi2BwAqrgqSe0BFvy8D4rfY2wM0fprAV6/1xtMRAGCX
HBo+VQPbBjcfW91sKXIBMAolJcirV1HoiKGZCjjQpPzZUSe7oTnFmVFvsSiCkfAb
gNL4MTKnN6s5F4rGDmOcIxQ2B5h/AK/au8yB6gjPpyDWjQJ3812PpHlOoFUjrQzu
Mhdr+er8oWZc8Thq9IN+tv76CeV9FLWPwNs8Fs5yVi11Tj5SCJJrNEe3IqnUBKj6
ioxg3WLAY3V+dYrFCTycZuaE+3wO9uNDmJZWFOOKeBptgiMqxgGOuoDO/IFSBLst
kslWCmTguCn7EoHFGEK4Tlv8cSNZbZaIcsdDWNNgibFPqG12I8I=
=uPzL
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
Source: gcc-11
Source-Version: 11.2.0-4
Done: Matthias Klose <doko@debian.org>

We believe that the bug you reported is fixed in the latest version of
gcc-11, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 993162@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose <doko@debian.org> (supplier of updated gcc-11 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 02 Sep 2021 12:23:43 +0200
Source: gcc-11
Architecture: source
Version: 11.2.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers <debian-gcc@lists.debian.org>
Changed-By: Matthias Klose <doko@debian.org>
Closes: 993162 993172
Changes:
 gcc-11 (11.2.0-4) unstable; urgency=medium
 .
   * Update to git 20210902 from the gcc-11 branch.
     - Fix PR target/101472 (x86), PR target/99744 (x86), PR target/101492 (x86),
       PR target/101549 (x86), PR target/101471 (x86), PR target/102035 (ARM),
       PR target/102035 (ARM), PR middle-end/101949, PR ipa/97565,
       PR debug/101905, PR gcov-profile/89961, PR fortran/87737,
       PR fortran/46691, PR fortran/99819, PR fortran/98411, PR libstdc++/101965,
       PR libstdc++/100682, PR libstdc++/100285, PR libstdc++/100180,
       PR libstdc++/100286, PR libstdc++/100351, PR libstdc++/100286,
       PR libstdc++/100285, PR libstdc++/100180, PR c++/101592,
       PR tree-optimization/102124, PR target/101472 (x86),
       PR target/99744 (x86), PR target/101492 (x86), PR target/101549 (x86),
       PR target/101471 (x86), PR target/102035 (ARM), PR target/102035 (ARM),
       PR middle-end/101949, PR ipa/97565, PR debug/101905,
       PR gcov-profile/89961, PR fortran/87737, PR fortran/46691,
       PR fortran/99819, PR fortran/98411, PR libstdc++/101965,
       PR libstdc++/100682, PR libstdc++/100285, PR libstdc++/100180,
       PR libstdc++/100286, PR libstdc++/100351, PR libstdc++/100286,
       PR libstdc++/100285, PR libstdc++/100180.
   * Again, for armhf configure --with-arch=<arch>+fp, dropping the --with-fpu=
     option; keep the old configure options for backports.
   * Update libgcc-s1 symbols file for sh4.
   * Remove trailing spaces in symbols files.
   * Don't configure with --enable-cet on x86 for Debian (old hardware is more
     valued than recent security features).  Closes: #993162, #993172.
   * Don't run the tests with the installed libstdc++ on slow buildds.
   * Build again for mipsel and mips64el, too much hassle with separate sources.
   * Disable the lto build on sparc64, memory issues on the buildd.
Checksums-Sha1:
 d8a969dbdcc879b62ae8e2ce6a6b22e2b8d251c5 27453 gcc-11_11.2.0-4.dsc
 eb2a6855c4d1ffbb049aa37bf466a6587138d0d9 1773932 gcc-11_11.2.0-4.debian.tar.xz
 94a590b05c7784b827f1b448fb9cf04f6c68a2fd 8519 gcc-11_11.2.0-4_source.buildinfo
Checksums-Sha256:
 f4e8d3990915550274b1daaad4776a9d15ded0038fa049274b81f3c0a472384e 27453 gcc-11_11.2.0-4.dsc
 0f2f76372131d97ca943bf68c9193b939e254f77c788efce4888486591c0b8cf 1773932 gcc-11_11.2.0-4.debian.tar.xz
 e4882556a0d95e0d157ed4d015f1f92279f461b0b21e4306455bd2cd2245b2f9 8519 gcc-11_11.2.0-4_source.buildinfo
Files:
 4db7d137087527ea0d137c117ab64310 27453 devel optional gcc-11_11.2.0-4.dsc
 f28a98e0eefe73cd5f125b5a92faa7f1 1773932 devel optional gcc-11_11.2.0-4.debian.tar.xz
 c5e183f7aa97d142f35d32d05df759d8 8519 devel optional gcc-11_11.2.0-4_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmEw12MQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9ZSoEACd1jfvjkJarNkmU3CtYycp4WaYAyIAw30k
LDBklv/ZdXOf0NeGfyIZPYjM1zaMQhz5/KQLeRUPXk0XQ0w1Oh4I2i0jf4vMXIrF
3dg4zILtymsGZYoiRoowrghgsjZXX3mqsbq2HguwTMVvaEdFF9LEDMSRwQp9Wp/j
TJxm2bqSJsn82vFbjEDT4MNXEhvDKRywNlgE9Hxwxdh88xg/9sD24RihwJg+9ruB
Fusn61AMSx3gnXvUjYKZ314feBAxmmh+G+58qmZleSaov0IMRTcQA0g/LshirBfo
ISIBU+xNBqRd6BQJutTNZwWGWMnNfvMC3VdfWaeX2n9VQ6e3t51QAPtALzPIPLwO
eU4rzktX0HTQdBYfRxm2fhvy3ZO3tWbUfj0mK7iky6H4vvz1BWIM48PiqFVaKyJ5
N0ZUeSvkv24xZmDMQJxhxvzkRLZ4hsvU7ZDpUXviVkQHcnVW0fUt9vNC3ddESDrR
n/ADRDVUzp4gbdeD5wp9rw9TeybTnW8bnhc2pEV9c9yT0aID6TRQx4cKKwQJOmSI
ZvQMpLcWIREe4PVoTL2LNKD3Wr2aR+q7gJqoGv3kQNWa/jNUs+DTK7jj93QE3tZJ
aahBQ3kYe2GLitSDpaziDr4DJI7A13rwchipRjJuKSipP2CUdHKZmqxI1YjP/uw4
L2Pi+n9y3w==
=xzyI
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: