Comment 6 for bug 1761999

I had an ugly instance of this problem on an EPYC processor. Not sure what it was related to.
It all started with errors during package upgrades.
sudo apt-get update >> success
sudo apt-get upgrade >> segmentation fault
The upgrade left several packages in a half-installed state (attach Part 1), and basic os command started to crash (attach Part 2).
In the syslog I had "general protection fault: 0000 [#1] SMP NOPTI" with multiple processes, see a detail failure log in attach Part 3 and Part 4. Attach Part 5 lists numerous processes that had the same failure as Part 4.
The system load started to climb, from idle, progressively by about 1 point per 3-5 min, until levels like 20-30, at this point it was very difficult to enter and reboot the system. I tried and managed to have it respond with reboot -f but it had the problem still and system did not come up correctly, until we performed a physical shutdown and restart. From then the system seems clean. I corrected the packages by reinstallation, and so far no problem.
Very frightening!
Can it be related to some problem between Ubuntu and the Ryzen/EPYC technology?

Please comment if you think this is a completely different bug.
Thanks!