as another update, just had another crash - more or less same error, but this time with the latest bios (3002) and latest amd-ucode (20230404.2e92a49f-1), but this time it reset and showed the “Hardware Error” log on boot, but today it didnt progress beyond showing “Hardware Error” (so i cannot post the full error after the reset), but the following was the last line in journalctl before the reset happened:
May 11 10:50:12 Meicoo-Manjaro kernel: igc 0000:06:00.0 enp6s0: PCIe link lost, device now detached
enp6s0 is for the build-in ethernet port (not a extra PCI device)
also note that this time it reset just right after boot (before i could even login)
for now i am just gonna revert back to 20230210.bf4115c-1 and ignore updates for amd-ucode
EDIT: the amd-ucode update (20230404.2e92a49f-1) definitely runs more stably on bios version 3002 than 2803 did, but still not fully stable
It seems I voted “No issues…” to early, because I just noticed that Audacity is broken with this update!
It opens and you can still import then play an audio file, but there is no visible waveform anymore, so there’s no way to edit anything!
Starting it from the terminal, I only see the same 3 error messages about GDK as in this thread Cannot Open Audacity.
As stated there, I deleted the legacy configuration folder ~/.audacity-data/ and Audacity created a new configuration folder ~/.config/audacity/, but that didn’t change a thing.
Didn’t want to mess more with AUR package as what I have to, so I uninstalled it and downloaded the Appimage from Audacity’s website, which works flawlessly…
After the upgrade a login on the console would produce a coredump of login:
systemd-coredump: Process 6473 (login) of user *redacted* dumped core.
I use ecryptfs and had modified my /etc/pam.d/system-auth accordingly, I noticed a system-auth.pacnew dating back to 2022, so i guess the file wasn’t updates as intended during the update due to my changes.
After restoring system-auth to system-auth.pacnew (without my patches) and updating pambase and systemd I re-applied my patches and everything worked fine. I diffed the old and the new file:
Thanks. It does seem to be something specific to my user profile: shotwell works fine if I log in under a different user. I’ve no idea how to track down the issue from here. Maybe I can try resetting all the shotwell preferences to defaults.
I updated the BIOS on my two latest PC’s, both AMD Ryzen-based and then did the Stable 2023-05-07 update, including the amd-ucode update. Both PCs are running without problems on kernel 6.1.26 LTS.
Thanks for bringing this amd-ucode issue up. I had originally planned to ignore BIOS updates because one of the PCs can only be updated from within Windows (Lenovo offers ONLY Windows-based BIOS updates) and I refuse to install Windows. But reading past posts by @bogdancovaciu and @straycat tipped me off to using Hiren’s BootCD PE to do the BIOS update. Easy peasy!!