[SOLVED]Arch randomly locking up

Alopex · 2021-05-07 21:24:37

New HDD
I recently bought a new hdd to replace my old one and after successfully installing Arch and all the packages and Drivers. (12th march 21)

The problem
I recently (4 days ago) started to notice random Freezes on some applications. This really started a week after the installation but it wasn't that frequent so I brushed it off but now the system will hang/freeze from 40 mins of use too 3 hours max. I've read that this happens on other users as far as 9 years ago so it's nothing new.

Research that I did before posting
1) https://bbs.archlinux.org/viewtopic.php?id=261565
2) https://bbs.archlinux.org/viewtopic.php?id=262422
3) https://bbs.archlinux.org/viewtopic.php?id=236686
4) https://wiki.archlinux.org/title/Intel_graphics

Tried

journalctl -b-1

Here is the output (At least some of it couldn't copy all) https://pastebin.com/SQVDrP0c

smartctl -H

Checked if xf86-video-intel was installed, the answer is no. Plus after reading through https://bbs.archlinux.org/viewtopic.php?id=262283 post #12 has the same GPU with the same problem even after removing xf86-video-intel. Question should I install xf86-video-intel or should I leave it uninstalled?

Possible causes

The GPU I have is the Intel HD Graphics 4000 but neofetch shows
https://imgur.com/8eA565K.png
which is not right.

Specs and other maybe useful stuff
CPU: Intel Pentium N3540 (4) @ 2.665GHz
Intel HD Graphics 4000
DE: Xfce 4.16
Kernel: 5.11.16-arch1-1

Thanks for reading my post!

Last edited by Alopex (2021-05-10 18:43:58)

Lone_Wolf · 2021-05-08 11:28:28

There are alternatives for pastebin.com, see https://wiki.archlinux.org/title/List_o … in_clients .

Several things that stand out

May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.1: BAR 15: no space for [mem size 0x00200000 64bit pref]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.1: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.2: BAR 14: no space for [mem size 0x00200000]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.2: BAR 14: failed to assign [mem size 0x00200000]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.2: BAR 15: no space for [mem size 0x00200000 64bit pref]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.2: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.3: BAR 14: no space for [mem size 0x00200000]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.3: BAR 14: failed to assign [mem size 0x00200000]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.3: BAR 15: no space for [mem size 0x00200000 64bit pref]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.3: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.2: BAR 13: assigned [io  0x1000-0x1fff]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.3: BAR 13: assigned [io  0x2000-0x2fff]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.3: BAR 14: no space for [mem size 0x00200000]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.3: BAR 14: failed to assign [mem size 0x00200000]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.3: BAR 15: no space for [mem size 0x00200000 64bit pref]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.3: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.2: BAR 14: no space for [mem size 0x00200000]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.2: BAR 14: failed to assign [mem size 0x00200000]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.2: BAR 15: no space for [mem size 0x00200000 64bit pref]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.2: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.1: BAR 15: no space for [mem size 0x00200000 64bit pref]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.1: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
May 07 20:30:18 mamalakis kernel: pci 0000:00:1c.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]


May 07 20:30:18 mamalakis kernel: hpet: number irqs doesn't agree with number of timers

May 07 20:47:05 mamalakis upowerd[523]: energy 7.962400 bigger than full 6.926400
May 07 20:48:21 mamalakis kernel: perf: interrupt took too long (3188 > 3187), lowering kernel.perf_event_max_sample_rate to 62700
May 07 20:48:30 mamalakis upowerd[523]: energy 8.406400 bigger than full 7.962400
May 07 20:50:46 mamalakis upowerd[523]: energy 8.421200 bigger than full 8.406400
May 07 20:55:04 mamalakis kernel: perf: interrupt took too long (4039 > 3985), lowering kernel.perf_event_max_sample_rate to 49500

Not sure what they mean, but combining those with the linked thread and the bug report in its #14 suggests kernel / firmware issues.

Let's start with some basic stuff :

Is microcode early loading configured ?

output of lspci -k

what brand / model is your motherboard / system ?

Please boot with systemd.unit=multi-user.target appended to the boot line.
it will give you a text console, log in as root and upload dmesg and journalctl -b .

Alopex · 2021-05-08 13:53:12

Output of lspci -k

00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e)
	Subsystem: CLEVO/KAPOK Computer Device 5470
	Kernel driver in use: iosf_mbi_pci
00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e)
	DeviceName:  Onboard IGD
	Subsystem: CLEVO/KAPOK Computer Device 5470
	Kernel driver in use: i915
	Kernel modules: i915
00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0e)
	Subsystem: CLEVO/KAPOK Computer Device 5470
	Kernel driver in use: ahci
00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e)
	Subsystem: CLEVO/KAPOK Computer Device 5470
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e)
	Subsystem: CLEVO/KAPOK Computer Device 5470
	Kernel driver in use: mei_txe
	Kernel modules: mei_txe
00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e)
	Subsystem: CLEVO/KAPOK Computer Device 5470
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e)
	Kernel driver in use: pcieport
00:1c.1 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 2 (rev 0e)
	Kernel driver in use: pcieport
00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 0e)
	Kernel driver in use: pcieport
00:1c.3 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 4 (rev 0e)
	Kernel driver in use: pcieport
00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e)
	Subsystem: CLEVO/KAPOK Computer Device 5470
	Kernel driver in use: lpc_ich
	Kernel modules: lpc_ich
00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e)
	Subsystem: CLEVO/KAPOK Computer Device 5470
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801
01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5286 PCI Express Card Reader (rev 01)
	Subsystem: CLEVO/KAPOK Computer Device 5470
	Kernel driver in use: rtsx_pci
	Kernel modules: rtsx_pci
01:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller (rev 06)
	Subsystem: CLEVO/KAPOK Computer Device 5470
	Kernel driver in use: r8169
	Kernel modules: r8169
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter
	Subsystem: Realtek Semiconductor Co., Ltd. Device b729
	Kernel driver in use: rtl8723be
	Kernel modules: rtl8723be

Microcode is configured!

System
A quick neofetch shows the Host as W54_W94_W955TU,-T,-C which after putting it on a search engine shows it as a Clevo laptop or manufactured by Clevo, both is correct.

dmesg output
http://ix.io/3mba
Thanks for this https://wiki.archlinux.org/title/List_o … in_clients made it easier!

journalctl -b output
http://ix.io/3mbb

Lone_Wolf · 2021-05-09 11:12:51

May 07 20:31:02 mamalakis tumblerd[500]: Failed to load plugin "tumbler-odf-thumbnailer.so": libgsf-1.so.114: cannot open shared objec>
May 07 20:31:02 mamalakis tumblerd[500]: Failed to load plugin "tumbler-raw-thumbnailer.so": libopenrawgnome.so.9: cannot open shared >

I doubt that causes the issue, you probably don't have libopenraw and libgsf installed ?

The upowerd messages led me to a askubuntu post[1] where they pointed to a faulty battery .

May 07 20:47:05 mamalakis upowerd[523]: energy 7.962400 bigger than full 6.926400
May 07 20:48:30 mamalakis upowerd[523]: energy 8.406400 bigger than full 7.962400
May 07 20:50:46 mamalakis upowerd[523]: energy 8.421200 bigger than full 8.406400

Analysing those numbers
7.962400 / 6.926400 = 15 % bigger
8.406400 / 7.962400 = 5.5 %
8.421200 / 8.406400 = 0.17 % , so very small .
Those numbers look very different then in the askubuntu post, probably something else.

Seems this is a Bay Trail processor[2] , which has an entry in archwiki , https://wiki.archlinux.org/title/Intel_ … ete_freeze

In the linked kernel bugreport[3] it's claimed to be fixed since kernel 5.4 but comment 1099 is from someone who encountered the issue on archlinux with kernel 5.8 .

Try adding intel_idle.max_cstate=1 as boot parameter .

[1] https://askubuntu.com/questions/1256993 … us#1263150
[2] https://ark.intel.com/content/www/us/en … 6-ghz.html
[3] https://bugzilla.kernel.org/show_bug.cgi?id=109051

seth · 2021-05-09 13:54:01

Also, how "bad" is the "freeze"?
Can you switch to a different VT or ssh into the "frozen" system?

Alopex · 2021-05-09 14:10:54

Lone_Wolf wrote:

May 07 20:31:02 mamalakis tumblerd[500]: Failed to load plugin "tumbler-odf-thumbnailer.so": libgsf-1.so.114: cannot open shared objec>
May 07 20:31:02 mamalakis tumblerd[500]: Failed to load plugin "tumbler-raw-thumbnailer.so": libopenrawgnome.so.9: cannot open shared >
I doubt that causes the issue, you probably don't have libopenraw and libgsf installed ?
The upowerd messages led me to a askubuntu post[1] where they pointed to a faulty battery .
May 07 20:47:05 mamalakis upowerd[523]: energy 7.962400 bigger than full 6.926400
May 07 20:48:30 mamalakis upowerd[523]: energy 8.406400 bigger than full 7.962400
May 07 20:50:46 mamalakis upowerd[523]: energy 8.421200 bigger than full 8.406400
Analysing those numbers
7.962400 / 6.926400 = 15 % bigger
8.406400 / 7.962400 = 5.5 %
8.421200 / 8.406400 = 0.17 % , so very small .
Those numbers look very different then in the askubuntu post, probably something else.

Seems this is a Bay Trail processor[2] , which has an entry in archwiki , https://wiki.archlinux.org/title/Intel_ … ete_freeze
In the linked kernel bugreport[3] it's claimed to be fixed since kernel 5.4 but comment 1099 is from someone who encountered the issue on archlinux with kernel 5.8 .
Try adding intel_idle.max_cstate=1 as boot parameter .

[1] https://askubuntu.com/questions/1256993 … us#1263150
[2] https://ark.intel.com/content/www/us/en … 6-ghz.html
[3] https://bugzilla.kernel.org/show_bug.cgi?id=109051

[1] Correct, the battery is faulty or it's on it's last legs.
[2] libopenraw nor libgsf installed, should I install those?
Question about [1], should I remove the battery? I doubt it causes the freezes but it doesn't hurt to try.

Alopex · 2021-05-09 14:12:02

seth wrote:

Also, how "bad" is the "freeze"?
Can you switch to a different VT or ssh into the "frozen" system?

Next time it freezes I will try to ssh from an other machine I have in my possession and I will report back. Thanks for the suggestion!

EDIT: It didn't crash yet, but having htop open in an other screen while showed some unusual ram usage (I have 4Gigs [3.8 because I give 200MB to my integrated GPU]). Is there any way that I can enable swap after the installation? I didn't create a swap partition in the first place because I said "It was enough for windows 8.1, I'll be running the same applications anyways", looking back at this, it was a mistake. Looking in the Arch wiki didn't help me that much, I know how to make a swap file/partition and how to enable it but can it be done after the installation?

Last edited by Alopex (2021-05-09 20:29:29)

seth · 2021-05-09 20:47:08

A swap partition will likely require you to alter the partition scheme, but you can easily add swap files whenever you feel like.

Lone_Wolf · 2021-05-10 12:37:31

[2] libopenraw nor libgsf installed, should I install those?

They're optional dependencies, if you don't encounter the filetypes the're needed for you don't need them.

Last edited by Lone_Wolf (2021-05-10 12:37:56)

Alopex · 2021-05-10 12:50:45

seth wrote:

A swap partition will likely require you to alter the partition scheme, but you can easily add swap files whenever you feel like.

Added a swapfile (8GB). I did a small test ram was near limit but swap was 2.53MB/8191MB, checked swappiness, seems about right at 60. It hasn't crashed yet thought. Should I increase swappiness to 80 or even 100? Or it's usual for that low usage on nearly max ram usage? Note: This is my first time using swap on any distro that I've used.

Lone_Wolf wrote:

They're optional dependencies, if you don't encounter the filetypes the're needed for you don't need them.

Thanks for the info.

-------------

Will mark this as [SOLVED] after some testing, to be sure.

seth · 2021-05-10 13:02:41

The kernel won't use the swap unless it (somewhat) has to.
The swappines controls whether to rather discard file caches or swap out - if theoretically all RAM was taken by the file cache, vm.swappiness had no impact whatsoever.
=> Leave it be and wait and see what happens w/ swap - obviously there seems some memory pressure and you may want to figure the cause of that (/proc/meminfo as well as simply sorting "top" by memory)

Alopex · 2021-05-10 18:43:43

After hours of testing, it hasn't crashed yet. So I'm marking it as solved!

Thanks to everyone that posted!

Arch Linux

#1 2021-05-07 21:24:37

[SOLVED]Arch randomly locking up

#2 2021-05-08 11:28:28

Re: [SOLVED]Arch randomly locking up

#3 2021-05-08 13:53:12

Re: [SOLVED]Arch randomly locking up

#4 2021-05-09 11:12:51

Re: [SOLVED]Arch randomly locking up

#5 2021-05-09 13:54:01

Re: [SOLVED]Arch randomly locking up

#6 2021-05-09 14:10:54

Re: [SOLVED]Arch randomly locking up

#7 2021-05-09 14:12:02

Re: [SOLVED]Arch randomly locking up

#8 2021-05-09 20:47:08

Re: [SOLVED]Arch randomly locking up

#9 2021-05-10 12:37:31

Re: [SOLVED]Arch randomly locking up

#10 2021-05-10 12:50:45

Re: [SOLVED]Arch randomly locking up

#11 2021-05-10 13:02:41

Re: [SOLVED]Arch randomly locking up

#12 2021-05-10 18:43:43

Re: [SOLVED]Arch randomly locking up

Board footer