I’m having a problem with occasional crashes and when I went to see the journal the errors were related to amd-ucode, is there a problem uninstalling it? And how can I do it the right way?
What CPU do you have?
If it’s AMD based, you should not uninstall the ucode.
If it’s Intel based, I can’t see why you would have/need amd ucode.
I have a Ryzen 7 1700x, but I noticed that the crashes are related to amd-ucode
I have a Ryzen 7 1700x on two computers and they both use the ucode without issues.
Are you sure it’s related?
They are both stability/bug fixes and security updates for the processor
I’m sure why if I turn off the PC and turn it on in a short time it crashes and I need to restart by the button, and when I go to see the journal the error is related to amd-ucode
Please post your system info as well as the output of journalctl -p 3 -xb
as outlined here:
-- Journal begins at Sat 2021-03-06 12:08:40 JST, ends at Fri 2021-04-09 05:35:55 JST. --
abr 08 07:09:00 eduardo-ax370gaming5 kernel: kvm: disabled by bios
abr 08 07:09:00 eduardo-ax370gaming5 kernel: kvm: disabled by bios
abr 08 07:09:00 eduardo-ax370gaming5 kernel: kvm: disabled by bios
abr 08 07:09:00 eduardo-ax370gaming5 kernel: kvm: disabled by bios
abr 08 07:09:01 eduardo-ax370gaming5 kernel: kvm: disabled by bios
abr 08 07:09:01 eduardo-ax370gaming5 kernel: kvm: disabled by bios
abr 08 07:09:01 eduardo-ax370gaming5 kernel: kvm: disabled by bios
abr 08 07:09:01 eduardo-ax370gaming5 kernel: kvm: disabled by bios
abr 08 07:09:01 eduardo-ax370gaming5 kernel: kvm: disabled by bios
abr 08 07:09:02 eduardo-ax370gaming5 kernel: kvm: disabled by bios
abr 08 07:09:09 eduardo-ax370gaming5 systemd-coredump[1521]: Process 1210 (baloo_file) of user 1000 dumped core.
Stack trace of thread 1511:
#0 0x00007f4ebff9d396 n/a (liblmdb.so + 0x4396)
#1 0x00007f4ebff9fefe n/a (liblmdb.so + 0x6efe)
#2 0x00007f4ebffa0644 n/a (liblmdb.so + 0x7644)
#3 0x00007f4ebffa0c50 mdb_get (liblmdb.so + 0x7c50)
#4 0x00007f4ec147c355 _ZN5Baloo12IdFilenameDB3getEy (libKF5BalooEngine.so.5 + 0x15355)
#5 0x00007f4ec14763ac _ZNK5Baloo13DocumentUrlDB3getEy (libKF5BalooEngine.so.5 + 0xf3ac)
#6 0x00007f4ec1487135 _ZNK5Baloo11Transaction11documentUrlEy (libKF5BalooEngine.so.5 + 0x20135)
#7 0x000055894ecdae44 n/a (baloo_file + 0x1de44)
#8 0x00007f4ec148e59f _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x2759f)
#9 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#10 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#11 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#12 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#13 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#14 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#15 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#16 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#17 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#18 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#19 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#20 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#21 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#22 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#23 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#24 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#25 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#26 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#27 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#28 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#29 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#30 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#31 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#32 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#33 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#34 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#35 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#36 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#37 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#38 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#39 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
#40 0x00007f4ec148e5f7 _ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE (libKF5BalooEngine.so.5 + 0x275f7)
That doesn’t show anything about amd-ucode
. What command did you run when you saw the errors? Maybe it actually said amd_uncore
?
[sudo] senha para eduardo:
-- Journal begins at Sat 2021-03-06 12:08:40 JST, ends at Sat 2021-04-10 05:53:47 JST. --
mar 27 06:06:38 eduardo-ax370gaming5 kernel: Linux version 5.12.0-1-MANJARO (builduser@LEGION) (gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Sun Mar 14 21:56:45 UTC 2021
mar 27 06:06:38 eduardo-ax370gaming5 kernel: Command line: BOOT_IMAGE=/vmlinuz-5.12-x86_64 root=UUID=a9392a2a-8179-4bce-8613-be5336db83fe ro rootflags=subvol=@ quiet udev.log_priority=3
mar 27 06:06:38 eduardo-ax370gaming5 kernel: KERNEL supported cpus:
mar 27 06:06:38 eduardo-ax370gaming5 kernel: Intel GenuineIntel
mar 27 06:06:38 eduardo-ax370gaming5 kernel: AMD AuthenticAMD
mar 27 06:06:38 eduardo-ax370gaming5 kernel: Hygon HygonGenuine
mar 27 06:06:38 eduardo-ax370gaming5 kernel: Centaur CentaurHauls
mar 27 06:06:38 eduardo-ax370gaming5 kernel: zhaoxin Shanghai
mar 27 06:06:38 eduardo-ax370gaming5 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
mar 27 06:06:38 eduardo-ax370gaming5 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
mar 27 06:06:38 eduardo-ax370gaming5 kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
mar 27 06:06:38 eduardo-ax370gaming5 kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
mar 27 06:06:38 eduardo-ax370gaming5 kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
mar 27 06:06:38 eduardo-ax370gaming5 kernel: BIOS-provided physical RAM map:
mar 27 06:06:38 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d3ff] usable
mar 27 06:06:38 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x000000000009d400-0x000000000009ffff] reserved
mar 27 06:06:38 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
mar 27 06:06:38 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009e01fff] usable
mar 27 06:06:38 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x0000000009e02000-0x0000000009ffffff] reserved
mar 27 06:06:38 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
mar 27 06:06:38 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20afff] ACPI NVS
mar 27 06:06:38 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x000000000a20b000-0x000000000affffff] usable
mar 27 06:06:38 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved
mar 27 06:06:38 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x000000000b020000-0x00000000db48cfff] usable
mar 27 06:06:38 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x00000000db48d000-0x00000000db61dfff] reserved
mar 27 06:06:38 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x00000000db61e000-0x00000000db7a1fff] usable
mar 27 06:06:38 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x00000000db7a2000-0x00000000dbbbffff] ACPI NVS
mar 27 06:06:38 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x00000000dbbc0000-0x00000000dcac0fff] reserved
mar 27 06:06:38 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x00000000dcac1000-0x00000000deffffff] usable
mar 27 06:06:38 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x00000000df000000-0x00000000dfffffff] reserved
mar 27 06:06:38 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
mar 27 06:06:38 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x00000000fd000000-0x00000000ffffffff] reserved
mar 27 06:06:38 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000081f37ffff] usable
mar 27 06:06:38 eduardo-ax370gaming5 kernel: NX (Execute Disable) protection: active
mar 27 06:06:38 eduardo-ax370gaming5 kernel: SMBIOS 3.2.0 present.
mar 27 06:06:38 eduardo-ax370gaming5 kernel: DMI: Gigabyte Technology Co., Ltd. AX370-Gaming 5/AX370-Gaming 5, BIOS F50e 07/02/2020
mar 27 06:06:38 eduardo-ax370gaming5 kernel: tsc: Fast TSC calibration failed
mar 27 06:06:38 eduardo-ax370gaming5 kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
mar 27 06:06:38 eduardo-ax370gaming5 kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
mar 27 06:06:38 eduardo-ax370gaming5 kernel: last_pfn = 0x81f380 max_arch_pfn = 0x400000000
mar 27 06:06:38 eduardo-ax370gaming5 kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
mar 27 06:06:38 eduardo-ax370gaming5 kernel: e820: update [mem 0xe0000000-0xffffffff] usable ==> reserved
mar 27 06:06:38 eduardo-ax370gaming5 kernel: last_pfn = 0xdf000 max_arch_pfn = 0x400000000
mar 27 06:06:38 eduardo-ax370gaming5 kernel: check: Scanning 1 areas for low memory corruption
mar 27 06:06:38 eduardo-ax370gaming5 kernel: Using GB pages for direct mapping
mar 27 06:06:38 eduardo-ax370gaming5 kernel: RAMDISK: [mem 0x3713d000-0x37895fff]
mar 27 06:06:38 eduardo-ax370gaming5 kernel: ACPI: Early table checksum verification disabled
mar 27 06:06:38 eduardo-ax370gaming5 kernel: ACPI: RSDP 0x00000000000F05A0 000024 (v02 ALASKA)
mar 27 06:06:38 eduardo-ax370gaming5 kernel: ACPI: XSDT 0x00000000DBB3C0A0 0000BC (v01 ALASKA A M I 01072009 AMI 00010013)
mar 27 06:06:38 eduardo-ax370gaming5 kernel: ACPI: FACP 0x00000000DBB43098 000114 (v06 ALASKA A M I 01072009 AMI 00010013)
mar 27 06:06:38 eduardo-ax370gaming5 kernel: ACPI: DSDT 0x00000000DBB3C1F0 006EA4 (v02 ALASKA A M I 01072009 INTL 20160930)
mar 27 06:06:38 eduardo-ax370gaming5 kernel: ACPI: FACS 0x00000000DBBA8E00 000040
mar 27 06:06:38 eduardo-ax370gaming5 kernel: ACPI: APIC 0x00000000DBB431B0 00015E (v03 ALASKA A M I 01072009 AMI 00010013)
mar 27 06:06:38 eduardo-ax370gaming5 kernel: ACPI: FPDT 0x00000000DBB43310 000044 (v01 ALASKA A M I 01072009 AMI 00010013)
lines 1-55
There’s not a single error there and you didn’t answer my question.
You still haven’t posted any errors related to amd-ucode
for us to see…
mar 27 06:06:38 eduardo-ax370gaming5 kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
mar 27 06:06:38 eduardo-ax370gaming5 kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
mar 27 06:06:38 eduardo-ax370gaming5 kernel: e820: update [mem 0xe0000000-0xffffffff] usable ==> reserved
I am confused about what you’re trying to tell me… these are memory maps that are being reported by e820
, and they look like they are operating correctly. They are able to reserve without issue. I don’t see any errors. I don’t know how these are related to amd-ucode
.
When a ucode
loads, it typically says something like:
[ 0.292893] microcode: CPU0 sig=0x306c3, pf=0x2, revision=0x1c
[ 0.292899] microcode: CPU1 sig=0x306c3, pf=0x2, revision=0x1c
[ 0.292906] microcode: CPU2 sig=0x306c3, pf=0x2, revision=0x1c
[ 0.292912] microcode: CPU3 sig=0x306c3, pf=0x2, revision=0x1c
[ 0.292956] microcode: Microcode Update Driver: v2.2.
To assist you further, we actually need to see the errors from journalctl
so that we know what we need to look into to fix.
which command should I run?