If it is intel microcode (ucode), then one would need to replace the intel ucode for that specific cpu in the firmware directory that contains it. The last 2-3 years of ucode fixes on older cpus were for the various memory bleed bugs where one user could snoop root's and other users data. And intel did make a mess of several of those firmware updates and the solution was always to use the update prior to the issue until a new version was delivered. On Tue, Jan 11, 2022 at 7:02 AM George N. White III <gnwiii@xxxxxxxxx> wrote: > > On Tue, 11 Jan 2022 at 07:16, Eyal Lebedinsky <fedora@xxxxxxxxxxxxxx> wrote: >> >> I just had the system lock-up hard, requiring hitting the reset button. >> >> I now see in the system log: >> >> Jan 11 19:28:54 e7 kernel: BERT: Error records from previous boot: >> Jan 11 19:28:54 e7 kernel: [Hardware Error]: event severity: fatal >> Jan 11 19:28:54 e7 kernel: [Hardware Error]: Error 0, type: fatal >> Jan 11 19:28:54 e7 kernel: [Hardware Error]: section_type: Firmware Error Record Reference >> Jan 11 19:28:54 e7 kernel: [Hardware Error]: Firmware Error Record Type: SOC Firmware Error Record Type1 (Legacy CrashLog Support) >> Jan 11 19:28:54 e7 kernel: [Hardware Error]: Revision: 0 >> Jan 11 19:28:54 e7 kernel: [Hardware Error]: Record Identifier: 100300100000000 >> Jan 11 19:28:54 e7 kernel: [Hardware Error]: 00000000: 00000000 00000000 00000000 00000000 ................ >> ... continue until >> Jan 11 19:28:54 e7 kernel: [Hardware Error]: 00000c00: ffffffff ffffffff ffffffff ffffffff ................ >> >> I understand that this is related to the preceding crash. If so, what does it tell me? >> >> Doing a search suggests that if this happens rarely then it can be ignored- true?.\ > > > This is an Intel firmware issue. > See: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/44 > > For the benefit of others who may encounter the same issue you should report it with > details of the hardware. Intel has been declaring old hardware as "unsupported", so > there may not be any good solutions. > >> >> I now see that I had it also last Oct but not earlier. This hard lock-up happens at times (more than twice for sure) >> and if I can do something about it then I would. > > > -- > George N. White III > > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
