On donderdag 8 maart 2018 20:49:54 CET Elimar Riesebieter wrote: > Well, I reported the initial reportfor x86 only, though.
Correct. apt-listbug did show it for my amd64 system though and later on there were messages indicating that amd64 could also be affected. > > CONFIG_CGROUP_CPUACCT=y > As the bug is triggered if this config is not set, no surprise. When apt-listbug alerted me to a critical error and I then looked up the bug report, that part was not known. And later on there was a *suspicion* that that could be the problem. I still think that my report added value as I used 2 systems to see whether my whole system would break. And with the then present messages, I had potential solutions/workaround ready (thanks for that!) so I could unbreak my system if needed. Other people who are alerted by this *critical( bug may also find it useful to know that not every single system would break. And lastly, when trying to narrow down the exact cause, it's also useful to know which systems/kernel configs do work. _sigh_
signature.asc
Description: This is a digitally signed message part.
