Manjaro Freezing

Hi, I’m having troubles with Manjaro randomly locking up, everything freezes, the cursor will not even move on screen, so I have to hard power it down. It mostly seems to do it when I’m running web browsers or steam, so I suspect it might have something to do with the graphics acceleration in the web browser / steam’s rendering engine.

I upgraded the kernel to 5.8.1-3, the newest available to me in the Manjaro Settings application and it seemed to sort of alleviate the frequency, but still it locks up randomly.

I just installed and would like to do some development work, but I fear it will lock up and lose my work all the time.

I’m using an AMD R9 380 card, I believe. Also, I installed with the XFCE desktop.

Please provide inxi -Fza output, and wrap the output via <code>, ```, or the </> button.

Kernel: 5.8.1-3-MANJARO x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.8-x86_64
root=UUID=02ed5c48-18da-443d-ad5b-b700691e4a09 rw quiet apparmor=1
security=apparmor resume=UUID=fb191141-8b05-40aa-a03d-e668d277fb7a
Desktop: Xfce 4.14.2 tk: Gtk 3.24.20 info: xfce4-panel wm: xfwm4
dm: LightDM 1.30.0 Distro: Manjaro Linux
Type: Desktop System: MSI product: MS-7900 v: 1.0 serial:
Mobo: MSI model: A88X-G45 GAMING (MS-7900) v: 1.0 serial:
UEFI: American Megatrends v: 1.5 date: 12/12/2014
Device-1: sony_controller_battery_dc:0c:2d:c8:fe:42 model: N/A serial: N/A
charge: N/A status: Full
Topology: Quad Core model: AMD A10-7700K Radeon R7 10 Compute Cores 4C+6G
bits: 64 type: MCP arch: Steamroller family: 15 (21) model-id: 30 (48)
stepping: 1 microcode: 6003104 L2 cache: 2048 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 27150
Speed: 1895 MHz min/max: 1900/3400 MHz boost: enabled Core speeds (MHz):
1: 1894 2: 1896 3: 1888 4: 1895
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, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: Micro-Star MSI
driver: radeon v: kernel alternate: amdgpu bus ID: 00:01.0
chip ID: 1002:1313
Device-2: AMD Tonga PRO [Radeon R9 285/380] vendor: Micro-Star MSI
driver: amdgpu v: kernel bus ID: 01:00.0 chip ID: 1002:6939
Display: x11 server: X.Org 1.20.8 driver: ati,radeon
unloaded: amdgpu,modesetting alternate: fbdev,vesa display ID: :0.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: HDMI-A-1 res: 1920x1080 hz: 60 dpi: 96
size: 509x286mm (20.0x11.3") diag: 584mm (23")
OpenGL: renderer: AMD Radeon R9 380 Series (TONGA DRM 3.38.0
5.8.1-3-MANJARO LLVM 10.0.1)
v: 4.6 Mesa 20.1.5 direct render: Yes
Device-1: AMD Kaveri HDMI/DP Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus ID: 00:01.1 chip ID: 1002:1308
Device-2: AMD FCH Azalia vendor: Micro-Star MSI driver: snd_hda_intel
v: kernel bus ID: 00:14.2 chip ID: 1022:780d
Device-3: AMD Tonga HDMI Audio [Radeon R9 285/380] vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 1002:aad8
Device-4: Sony DualShock 4 [CUH-ZCT2x] type: USB
driver: snd-usb-audio,sony,usbhid bus ID: 1-2:2 chip ID: 054c:09cc
Sound Server: ALSA v: k5.8.1-3-MANJARO
Device-1: Qualcomm Atheros Killer E220x Gigabit Ethernet
vendor: Micro-Star MSI driver: alx v: kernel port: d000 bus ID: 03:00.0
chip ID: 1969:e091
IF: enp3s0 state: up speed: 100 Mbps duplex: full mac:
Device-2: Qualcomm Atheros AR5212/5213/2414 Wireless Network Adapter
vendor: Accton driver: ath5k v: kernel port: d000 bus ID: 04:05.0
chip ID: 168c:0013
IF: wlp4s5 state: down mac:
Local Storage: total: 1.36 TiB used: 18.21 GiB (1.3%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/sda vendor: Seagate model: ST3500418AS size: 465.76 GiB
block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
rotation: 7200 rpm serial: rev: HP35 scheme: GPT
ID-2: /dev/sdb vendor: Western Digital model: WD2500AAKX-00ERMA0
size: 232.89 GiB block size: physical: 512 B logical: 512 B
speed: 6.0 Gb/s rotation: 7200 rpm serial: rev: 1H15 scheme: MBR
ID-3: /dev/sdc vendor: Seagate model: ST3250310AS size: 232.83 GiB
block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
serial: rev: A scheme: GPT
ID-4: /dev/sdd vendor: Western Digital model: WDBNCE5000PNC
size: 465.76 GiB block size: physical: 512 B logical: 512 B
speed: 6.0 Gb/s serial: rev: 00WD scheme: GPT
ID-1: / raw size: 216.41 GiB size: 212.01 GiB (97.97%)
used: 18.21 GiB (8.6%) fs: ext4 dev: /dev/sdc2
Kernel: swappiness: 60 (default) cache pressure: 100 (default)
ID-1: swap-1 type: partition size: 16.12 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sdc3
System Temperatures: cpu: 4.2 C mobo: N/A
Fan Speeds (RPM): N/A
GPU: device: amdgpu temp: 51 C fan: 1250 device: radeon temp: 4 C
Processes: 207 Uptime: 24m Memory: 14.66 GiB used: 1.89 GiB (12.9%)
Init: systemd v: 245 Compilers: gcc: 10.1.0 clang: 10.0.1 Packages:
pacman: 1130 lib: 319 flatpak: 0 Shell: Bash v: 5.0.18
running in: xfce4-terminal inxi: 3.1.05

Sorry for the double post, but bumpin’

I would recommend you to further analyse what’s going on with your system temperature as 4.2 °C is for sure not the correct temperature, could be e.g. wrong inxi read-out or defective sensor.



That motherboard has a newer BIOS

1 Like

This has been the case since I got this apu, no matter which utility I use the temperature sensor always reports incorrectly, I did a tiny bit of research back when I first got it and apparently AMD is known for this in certain cpus, but it begs the question whether or not the thermal shutdown features actually work correctly when the cpu goes far over nominal temperature range (which is like ~76 celsius max for this particular cpu, I think).

Thanks for the heads up on the newer BIOS, I’ll update my motherboard BIOS and report back on how it does after running the new BIOS for a while.

Using newest bios for my motherboard PC totally froze/locked up ~2 hours in use while using Firefox. I’m not sure how to look through log files to find exactly what is going on, any ideas?

journalctl can tell you what event happened

I faced an issue very similar to yours with the same DE. Try switching to some older kernels.