Hi,
On 2022-10-04 08:51, Aurelien Jarno wrote:
> Hi
>
> On 2022-09-25 13:43, Aurelien Jarno wrote:
> > > Running a quick diff against old procinfo reveals that "flags" has the
> > > following new entries now:
> > >
> > > tsc_deadline_timer ssbd ibrs ibpb stibp bmi1 bmi2 md_clear flush_l1d
> > >
Hi,
On 2022-10-04 19:44, debian-bug-rep...@p0358.net wrote:
> > Is there an easy way to unbrick a system affected by the issue? such as
> > a kernel-line option or a configuration file in /etc? I don't see how I
> > can set a GLIBC_TUNABLES environment variable for the whole system.
>
> I was
Hello,
Is there an easy way to unbrick a system affected by the issue? such as
a kernel-line option or a configuration file in /etc? I don't see how I
can set a GLIBC_TUNABLES environment variable for the whole system.
Samuel
Is there an easy way to unbrick a system affected by the issue? such as
a kernel-line option or a configuration file in /etc? I don't see how I
can set a GLIBC_TUNABLES environment variable for the whole system.
I was trying during my testing to set such option globally somehow, but
failed,
Hi
On 2022-09-25 13:43, Aurelien Jarno wrote:
> > Running a quick diff against old procinfo reveals that "flags" has the
> > following new entries now:
> >
> > tsc_deadline_timer ssbd ibrs ibpb stibp bmi1 bmi2 md_clear flush_l1d
> >
> > > it looks like that the BMI2
> > > instructions support
On 2022-09-25 12:02, debian-bug-rep...@p0358.net wrote:
> > Now that we understood the bug, I actually find strange that the
> > microcode update is fixing this, it looks like that the BMI2
> > instructions support has been added in a microcode update. Would it be
> > possible to give the output
Now that we understood the bug, I actually find strange that the
microcode update is fixing this, it looks like that the BMI2
instructions support has been added in a microcode update. Would it be
possible to give the output of /proc/cpuinfo with and without the
microcode update applied?
The
On 2022-09-25 00:35, debian-bug-rep...@p0358.net wrote:
> Hello, sorry for delayed response, I've managed to collect and analyze a few
> coredump files with valid symbols (I installed libc6-dbg and dpkg-dev, and
> pointed gdb at Debian's debuginfod server, also used apt-get source to get
> the
I can confirm updating the microcode by installing the intel-microcode
package and rebooting does indeed mitigate this issue. An LXC container
that was previously bricked due to update now starts and seems to behave
fully normally.
[0.00] microcode: microcode updated early to revision
Hello, sorry for delayed response, I've managed to collect and analyze a
few coredump files with valid symbols (I installed libc6-dbg and
dpkg-dev, and pointed gdb at Debian's debuginfod server, also used
apt-get source to get the sources for libc6).
It seems there are at least 3-4 distinct
Hi Aurelien,
On Tue, Sep 20, 2022 at 11:20:26PM +0200, Aurelien Jarno wrote:
> Have you been able to progress on that? Do you need some help for a
> specific step?
For what it’s worth, I’ve upgraded libc6 on my Haswell system (Xeon
E3-1245v3) and everything seems to be working fine.
Regards,
Hi,
Have you been able to progress on that? Do you need some help for a
specific step?
Regards
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
Hi,
On 2022-09-15 20:59, debian-bug-rep...@p0358.net wrote:
> > The first thing would be to provide the output of /proc/cpuinfo
>
> Pasting below (please **NOTE** that "avx2" would normally be there, but is
> currently missing due to this kernel option `clearcpuid=293` with which I
> booted the
> The first thing would be to provide the output of /proc/cpuinfo
Pasting below (please **NOTE** that "avx2" would normally be there, but
is currently missing due to this kernel option `clearcpuid=293` with
which I booted the PC now -- I can **100%** confirm "avx2" was there
before, but don't
Hi,
On 2022-09-15 01:37, debian-bug-rep...@p0358.net wrote:
> 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
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
16 matches
Mail list logo
