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, tho
/proc/cpuinfo without microcode update is already attached somewhere
above in the bug report, the new one after update is as follows:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 60
model name : Intel(R) Core(TM) i3-4000M CPU @ 2.40GHz
stepping
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 pl
> 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
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
Hello Andrei:
True, the package is not from Debian, but the purpose of me filing a bug
report is to generate an RFP so that the package can be adapted by
Debian. Adapting the package by Debian is the first step in moving
things forward. So far I haven't found any issues, and the packa
Package: bitcoind
Version: 0.18.0~dfsg-1
Severity: important
Dear Maintainer,
after apt upgrade this week, bitcoin-qt does not start anymore.
It fails with both of this errors message:
bitcoind: symbol lookup error: bitcoind: undefined symbol:
_ZN7leveldb4port5Mutex4LockEv
bitcoin-qt: symbol lo
hi Russell,
its pretty unclear which syntax to use with the TLSCipherSuite parameter
of slapd.conf ...
The old SSL syntax used with 2.3x versions of slapd was pretty clear with
that and could be adapted from the openssl documentation.
Today I switched a testing platform from etch to lenny (fresh
9 matches
Mail list logo
