lately i noticed random crashes in the system no matter if the pc is on for a long or short time, or if the usage is intense or idle even
System: Kernel: 5.7.15-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.1.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.7-x86_64 root=UUID=ad685fd6-0b1e-4bf3-a5d1-ceb1fa66d3b0 rw quiet apparmor=1
security=apparmor udev.log_priority=3 iommu=pt idle=nomwait rcu_nocbs=0-15
Desktop: KDE Plasma 5.19.4 tk: Qt 5.15.0 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux
Machine: Type: Desktop Mobo: Gigabyte model: AX370-Gaming 5 serial: <filter> UEFI: American Megatrends v: F50e
date: 07/02/2020
CPU: Topology: 8-Core model: AMD Ryzen 7 1700X bits: 64 type: MT MCP arch: Zen family: 17 (23) model-id: 1 stepping: 1
microcode: 8001138 L2 cache: 4096 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 108623
Speed: 3492 MHz min/max: N/A Core speeds (MHz): 1: 3492 2: 3491 3: 3493 4: 3480 5: 3493 6: 3495 7: 3487 8: 2998
9: 3490 10: 3473 11: 3493 12: 3493 13: 3483 14: 3484 15: 3487 16: 3485
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
vendor: Micro-Star MSI driver: amdgpu v: kernel bus ID: 07:00.0 chip ID: 1002:67df
Display: x11 server: X.Org 1.20.8 compositor: kwin_x11 driver: amdgpu FAILED: ati unloaded: modesetting
alternate: fbdev,vesa display ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9")
Monitor-1: DisplayPort-1 res: 1920x1080 hz: 60 dpi: 92 size: 531x298mm (20.9x11.7") diag: 609mm (24")
OpenGL: renderer: Radeon RX 580 Series (POLARIS10 DRM 3.37.0 5.7.15-1-MANJARO LLVM 10.0.1) v: 4.6 Mesa 20.1.5
direct render: Yes
Audio: Device-1: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] vendor: Micro-Star MSI driver: snd_hda_intel
v: kernel bus ID: 07:00.1 chip ID: 1002:aaf0
Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
bus ID: 09:00.3 chip ID: 1022:1457
Sound Server: ALSA v: k5.7.15-1-MANJARO
Network: Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: 5.6.0-k port: e000 bus ID: 04:00.0
chip ID: 8086:1539
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Qualcomm Atheros Killer E2500 Gigabit Ethernet vendor: Gigabyte driver: alx v: kernel port: d000
bus ID: 05:00.0 chip ID: 1969:e0b1
IF: enp5s0 state: down mac: <filter>
Drives: Local Storage: total: 3.64 TiB used: 2.23 TiB (61.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB block size: physical: 4096 B logical: 512 B
speed: 6.0 Gb/s serial: <filter> rev: 023 scheme: GPT
ID-2: /dev/sdb vendor: Western Digital model: WD30EZRX-00DC0B0 size: 2.73 TiB block size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 0A80 scheme: GPT
Partition: ID-1: / raw size: 97.66 GiB size: 95.62 GiB (97.92%) used: 11.88 GiB (12.4%) fs: ext4 dev: /dev/sda1
ID-2: /home raw size: 833.37 GiB size: 819.29 GiB (98.31%) used: 159.72 GiB (19.5%) fs: ext4 dev: /dev/sda2
Swap: Alert: No Swap data was found.
Sensors: System Temperatures: cpu: 42.4 C mobo: N/A gpu: amdgpu temp: 34 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 1099
Info: Processes: 319 Uptime: 9m Memory: 31.31 GiB used: 1.93 GiB (6.2%) Init: systemd v: 245 Compilers: gcc: 10.1.0
Packages: pacman: 1331 lib: 391 flatpak: 0 Shell: Bash v: 5.0.18 running in: konsole inxi: 3.1.05 ```
check in journal log
sudo journalctl -b0 ( -b -1 boot before , etc ... )
[sudo] senha para eduardo:
-- Logs begin at Fri 2020-08-21 15:09:55 JST, end at Mon 2020-08-24 18:54:57 JST. --
ago 24 14:51:29 eduardo-ax370gaming5 kernel: Linux version 5.7.15-1-MANJARO (builduser@LEGION) (gcc version 10.1.0 (GCC), GNU ld (GNU Binutils) 2.34.0) #1 SMP PREEMPT Tue Aug 11 15:00:37 UTC 2020
ago 24 14:51:29 eduardo-ax370gaming5 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7-x86_64 root=UUID=ad685fd6-0b1e-4bf3-a5d1-ceb1fa66d3b0 rw quiet apparmor=1 security=apparmor udev.log_priority=3 iommu=pt idle=nomwait rcu_nocbs=0-15
ago 24 14:51:29 eduardo-ax370gaming5 kernel: KERNEL supported cpus:
ago 24 14:51:29 eduardo-ax370gaming5 kernel: Intel GenuineIntel
ago 24 14:51:29 eduardo-ax370gaming5 kernel: AMD AuthenticAMD
ago 24 14:51:29 eduardo-ax370gaming5 kernel: Hygon HygonGenuine
ago 24 14:51:29 eduardo-ax370gaming5 kernel: Centaur CentaurHauls
ago 24 14:51:29 eduardo-ax370gaming5 kernel: zhaoxin Shanghai
ago 24 14:51:29 eduardo-ax370gaming5 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
ago 24 14:51:29 eduardo-ax370gaming5 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
ago 24 14:51:29 eduardo-ax370gaming5 kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
ago 24 14:51:29 eduardo-ax370gaming5 kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
ago 24 14:51:29 eduardo-ax370gaming5 kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
ago 24 14:51:29 eduardo-ax370gaming5 kernel: BIOS-provided physical RAM map:
ago 24 14:51:29 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
ago 24 14:51:29 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
ago 24 14:51:29 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009e01fff] usable
ago 24 14:51:29 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x0000000009e02000-0x0000000009ffffff] reserved
ago 24 14:51:29 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
ago 24 14:51:29 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20afff] ACPI NVS
ago 24 14:51:29 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x000000000a20b000-0x000000000affffff] usable
ago 24 14:51:29 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved
ago 24 14:51:29 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x000000000b020000-0x00000000db48efff] usable
ago 24 14:51:29 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x00000000db48f000-0x00000000db61ffff] reserved
ago 24 14:51:29 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x00000000db620000-0x00000000db7a3fff] usable
ago 24 14:51:29 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x00000000db7a4000-0x00000000dbbc1fff] ACPI NVS
ago 24 14:51:29 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x00000000dbbc2000-0x00000000dca18fff] reserved
ago 24 14:51:29 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x00000000dca19000-0x00000000dcac0fff] type 20
ago 24 14:51:29 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x00000000dcac1000-0x00000000deffffff] usable
ago 24 14:51:29 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x00000000df000000-0x00000000dfffffff] reserved
ago 24 14:51:29 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
ago 24 14:51:29 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x00000000fd000000-0x00000000ffffffff] reserved
ago 24 14:51:29 eduardo-ax370gaming5 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000081f37ffff] usable
ago 24 14:51:29 eduardo-ax370gaming5 kernel: NX (Execute Disable) protection: active
ago 24 14:51:29 eduardo-ax370gaming5 kernel: efi: EFI v2.70 by American Megatrends
ago 24 14:51:29 eduardo-ax370gaming5 kernel: efi: ACPI 2.0=0xdbb3e000 ACPI=0xdbb3e000 SMBIOS=0xdc902000 SMBIOS 3.0=0xdc901000 ESRT=0xd9df3c98
ago 24 14:51:29 eduardo-ax370gaming5 kernel: SMBIOS 3.2.0 present.
ago 24 14:51:29 eduardo-ax370gaming5 kernel: DMI: Gigabyte Technology Co., Ltd. AX370-Gaming 5/AX370-Gaming 5, BIOS F50e 07/02/2020
ago 24 14:51:29 eduardo-ax370gaming5 kernel: tsc: Fast TSC calibration failed
ago 24 14:51:29 eduardo-ax370gaming5 kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
ago 24 14:51:29 eduardo-ax370gaming5 kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
ago 24 14:51:29 eduardo-ax370gaming5 kernel: last_pfn = 0x81f380 max_arch_pfn = 0x400000000
ago 24 14:51:29 eduardo-ax370gaming5 kernel: MTRR default type: uncachable
ago 24 14:51:29 eduardo-ax370gaming5 kernel: MTRR fixed ranges enabled:
ago 24 14:51:29 eduardo-ax370gaming5 kernel: 00000-9FFFF write-back
ago 24 14:51:29 eduardo-ax370gaming5 kernel: A0000-BFFFF write-through
ago 24 14:51:29 eduardo-ax370gaming5 kernel: C0000-FFFFF write-protect
ago 24 14:51:29 eduardo-ax370gaming5 kernel: MTRR variable ranges enabled:
ago 24 14:51:29 eduardo-ax370gaming5 kernel: 0 base 000000000000 mask FFFF80000000 write-back
ago 24 14:51:29 eduardo-ax370gaming5 kernel: 1 base 000080000000 mask FFFFC0000000 write-back
ago 24 14:51:29 eduardo-ax370gaming5 kernel: 2 base 0000C0000000 mask FFFFE0000000 write-back
ago 24 14:51:29 eduardo-ax370gaming5 kernel: 3 disabled
ago 24 14:51:29 eduardo-ax370gaming5 kernel: 4 disabled
ago 24 14:51:29 eduardo-ax370gaming5 kernel: 5 disabled
ago 24 14:51:29 eduardo-ax370gaming5 kernel: 6 disabled```
bourne
August 24, 2020, 10:22am
#4
This might be linked to my post Continuation of: Are there any NVME/SSD related bug fixes in Linux 5.6 vis-a-vis 5.4?
Try the following:
mv /boot/amd-ucode.img /boot/amd-ucode.bin
At the grub prompt, use e to edit the grub commandline and delete /boot/amd-ucode.img from the initrd argument list. Then press F10 to boot, and finally run:
update-grub
Let me know if this helps.
I didn’t understand how to edit the grub command line, can you post a photo?
bourne
August 24, 2020, 10:41am
#6
It’s very easy. Just press e when you get the grub prompt. Believe me, no photo is needed.
What command do I run at the grub prompt?
Eu rodei esse comando e o sistema não iniciou mais, tive que instalar de novo
bourne
August 24, 2020, 1:32pm
#9
At the grub prompt, you do not have to run any command. Instead, you have to edit the last line (beginning with initrd) to delete /boot/amd-ucode.img from the argument list.
After deleting /boot/amd-ucode.img from the argument list, press F10
bourne
August 24, 2020, 1:35pm
#10
Before booting to grub prompt, you should first run as root: mv /boot/amd-ucode.img /boot/amd-ucode.bin
Afterwards, you should run as root: update-grub
I’ve been seeing and in the case of the tip the person had an nvme, I use normal ssd
bourne
August 24, 2020, 3:09pm
#12
The post is my own. I earlier had a normal SSD, and Linux would show the same freeze symptoms. I then switched to NVME, where the problem continued. After spending immense amount of time and money, I zeroed in on the problem: /boot/amd-ucode.img
The fix worked for me. Perhaps it may work for you as well.
I found a tip to put GRUB_CMDLINE_LINUX_DEFAULT which is processor.max_cstate = 5, and it seems to make more sense on first generation processors which is my case, but I will test both
bourne
August 24, 2020, 3:37pm
#15
My processor is also Ryzen 1st gen. I am 90% sure my fix will work for you as well.