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

Bug#1019855: marked as done (Fwd: libc6: immediately crashes with SIGILL on 4th gen Intel Core CPUs (seems related to AVX2 instructions), bricking the whole system)

Your message dated Sat, 15 Oct 2022 11:02:09 +0000
with message-id <E1ojevh-005COE-29@fasolo.debian.org>
and subject line Bug#1019855: fixed in glibc 2.31-13+deb11u5
has caused the Debian Bug report #1019855,
regarding Fwd: libc6: immediately crashes with SIGILL on 4th gen Intel Core CPUs (seems related to AVX2 instructions), bricking the whole system
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.)


-- 
1019855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019855
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libc6
Version: 2.31-13+deb11u4
Severity: critical

Dear Maintainer,

After an upgrade to version +deb11u4 on my system running Haswell
(4th gen Intel Core) CPU, most of the programs including bash or dpkg
are immediately crashing with SIGILL. The problem seems to be caused/
related to AVX2 and changes made to some functions utilizing this instruction set. I don't know much about Debian bug reporting, so forgive me any mistakes I've made. 
The issue is on both host, LXC and Docker.
I have described more on this link:
https://github.com/debuerreotype/docker-debian-artifacts/issues/175
where I also linked my coredump from example program and described stuff more thoroughly.
Coredump link directly just in case: https://github.com/debuerreotype/docker-debian-artifacts/files/9569748/core.bash.100000.2663c40e671041e6b40c882a70b83c3f.1480736.1663185824000000.zip 

Also log lines from kernel:
kernel: [834669.721253] traps: dpkg[1455373] trap invalid opcode ip:7fa39701951d sp:7ffc4ad26e58 error:0 in libc-2.31.so[7fa396edd000+15a000] kernel: [834669.732958] traps: dpkg[1455374] trap invalid opcode ip:7f529ca9551d sp:7fffb6f0a238 error:0 in libc-2.31.so[7f529c959000+15a000] kernel: [834669.840128] traps: dpkg[1455375] trap invalid opcode ip:7f1874cc951d sp:7fffc2c2f5d8 error:0 in libc-2.31.so[7f1874b8d000+15a000] kernel: [834669.907918] traps: dpkg[1455378] trap invalid opcode ip:7f3b4f8d851d sp:7fff3ec970f8 error:0 in libc-2.31.so[7f3b4f79c000+15a000] kernel: [834712.152139] traps: passwd[1455693] trap invalid opcode ip:7fefee4b52b7 sp:7ffffcb506b8 error:0 in libc-2.31.so[7fefee37d000+15a000]
Not sure what exactly might be causing the issue, but if these changes aren't pulled, potentially anyone with this or similar CPU as me will upgrade and end up with bricked system. I will proceed to try using `clearcpuid=293` kernel flag myself, but consider how many distros depend on Debian, live CDs etc, with people unable to figure out why their system became useless, unable to trace the source, and blaming it just on Linux...
I'm filling this bug report from my downgraded host system to the previous libc6 version. 

   * What led up to the situation? apt upgrade...
   * What exactly did you do (or not do) that was effective (or
     ineffective)? downgrade to +deb11u3
* What was the outcome of this action? everything works on the older version 
   * What outcome did you expect instead?


-- System Information:
Debian Release: 11.4
  APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') 
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.39-1-pve (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set 
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libc6 depends on:
ii  libcrypt1  1:4.4.18-4
ii  libgcc-s1  10.2.1-6

Versions of packages libc6 recommends:
ii  libidn2-0       2.3.0-5
pn  libnss-nis      <none>
pn  libnss-nisplus  <none>

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.77
pn  glibc-doc              <none>
ii  libc-l10n              2.31-13+deb11u3
ii  locales                2.31-13+deb11u3

-- debconf information:
  glibc/disable-screensaver:
  glibc/restart-services:
  glibc/kernel-not-supported:
  glibc/kernel-too-old:
  libraries/restart-without-asking: false
  glibc/restart-failed:
  glibc/upgrade: true

--- End Message ---
--- Begin Message --- 
Source: glibc
Source-Version: 2.31-13+deb11u5
Done: Aurelien Jarno <aurel32@debian.org>

We believe that the bug you reported is fixed in the latest version of
glibc, 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 1019855@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno <aurel32@debian.org> (supplier of updated glibc 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: SHA512

Format: 1.8
Date: Fri, 14 Oct 2022 21:35:00 +0200
Source: glibc
Architecture: source
Version: 2.31-13+deb11u5
Distribution: bullseye
Urgency: medium
Maintainer: GNU Libc Maintainers <debian-glibc@lists.debian.org>
Changed-By: Aurelien Jarno <aurel32@debian.org>
Closes: 1019855
Changes:
 glibc (2.31-13+deb11u5) bullseye; urgency=medium
 .
   * debian/patches/local-require-bmi-in-avx2-ifunc.diff: new patch extracted
     from an upstream commit, to change the AVX2 ifunc selector to require the
     BMI2 feature. It happened that the wmemchr and wcslen changes backported
     in 2.31-13+deb11u4 relied on that commit which got forgotten.
     Closes: #1019855.
Checksums-Sha1:
 793d3a4830a94088e32ec86d1820b79a135ec5f5 8347 glibc_2.31-13+deb11u5.dsc
 458aee83d736e7a0929093e63c50a0ebe10c35c8 954032 glibc_2.31-13+deb11u5.debian.tar.xz
 5eca6478a33c9b7aa5f283bd78bc6bfadc11958c 9113 glibc_2.31-13+deb11u5_source.buildinfo
Checksums-Sha256:
 77e3760f65a2f850bf492c8248690aed6eaec2eb988a261e0439cdcada110487 8347 glibc_2.31-13+deb11u5.dsc
 bb679f8e65d5b692f4479848848ec60e6eaa40e40b7eba7f5c2cf7bc79e3a415 954032 glibc_2.31-13+deb11u5.debian.tar.xz
 6cd3cb26bef6b8c89cd0a04131f06e5cb1df77089123096c1bf4c6d80140ecd2 9113 glibc_2.31-13+deb11u5_source.buildinfo
Files:
 b229b01fa28840a3f781fbc1f742da6e 8347 libs required glibc_2.31-13+deb11u5.dsc
 ddb1999673c49df3f930faf1426ea9ad 954032 libs required glibc_2.31-13+deb11u5.debian.tar.xz
 252f5e99cf6ef0682c7b918d43f5f7bb 9113 libs required glibc_2.31-13+deb11u5_source.buildinfo

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

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmNJun4ACgkQE4jA+Jno
M2tSFg//Qzw5786BVC5m5YfQIneii/1zQUjJ7u6k7DfBRmJ1D3VGSXpfuRd3sN+X
+U3YoCm0AQeBnyYFA9JZ8PHX65jYKdZEXvpLpd+kt0K7600meJBu0uweMFX4VJ0M
MB4k6Wt+M4GOn+Yao05yoNbohreKvJI8cus0HrR0N0zSvQexIqNd3bLZsybotRwZ
V0N5p+DVBERyQgj/RWnimGyt9SZ3MHAFJ0a3pKFvq+/B0aUtPAt2+Iv23aqxWHiy
QfghX1GMAF3FQ8n1AtT4JXL2A+4pQMggJOT9I83i5iQUJRRy/xdQpO2XVyPrZy2Q
5LSg05xBe9UonNqNOtHFIRzv1iRR//80ODL7kwDbG6+FRbnVxs+K6bRw3ZUc0Md/
5OUm00NoOwHEnVMANY8dQ4flEXESkpkPWIPWLv8GJUANTyQ+J5ALcXLjEbDn81PC
R+v9EMsMwbhmRZm09AcpouwES1YkPPVAhhLoG4QcjKkngUrwffClQuggfBDUvLu5
X7P/FlEDPg2LUXnqPrcIbGHBSa+avpbR67rdDjG/d9dDzbfHF/CISsbZlzqdYhXi
vfdo8OXRVxM7raU1cGOSdP7nZr12ilwpNSHY+a1Sg4kH3m0IPn+Txs+1jKaFTEP/
RaI1dp0F1BR1OtvacE/Hq8/hoM2GeRQZ2i5nKlNa+Dvs5QA4uNI=
=T6Qb
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: