Random system freeze and journal errors?

Hello!
Could someone please help me fix these errors?
I’ve been having random system freezes and I found all this.
I’ve already modified thinkfan.conf to run cooler but I don’t know how to fix the rest.
Is is possible that system is randomly freezing because of them?
Thanks.
Best,
Facundo

journalctl -p err -b
– Logs begin at Fri 2019-04-05 14:00:21 -03, end at Fri 2019-04-05 15:56:54 -03. –
abr 05 14:00:21 pafa-pc systemd-udevd[247]: /etc/udev/rules.d/51-android.rules:2: Invalid key/value pair, starting at character 1 (‘S’)
abr 05 14:00:21 pafa-pc systemd-udevd[247]: /etc/udev/rules.d/51-android.rules:5: Invalid key/value pair, starting at character 1 (‘S’)
abr 05 14:00:22 pafa-pc systemd[1]: man-db-mbb.timer: Refusing to start, unit to trigger not loaded.
abr 05 14:00:22 pafa-pc systemd[1]: Failed to start Daily man-db regeneration.
abr 05 14:00:30 pafa-pc systemd-logind[470]: Cannot find the ESP partition mount point.
abr 05 14:59:44 pafa-pc kernel: CPU0: Package temperature above threshold, cpu clock throttled (total events = 1)
abr 05 14:59:44 pafa-pc kernel: CPU2: Core temperature above threshold, cpu clock throttled (total events = 1)
abr 05 14:59:44 pafa-pc kernel: CPU3: Core temperature above threshold, cpu clock throttled (total events = 1)
abr 05 14:59:44 pafa-pc kernel: CPU1: Package temperature above threshold, cpu clock throttled (total events = 1)
abr 05 14:59:44 pafa-pc kernel: CPU2: Package temperature above threshold, cpu clock throttled (total events = 1)
abr 05 14:59:44 pafa-pc kernel: CPU3: Package temperature above threshold, cpu clock throttled (total events = 1)

your cpu is too hot and go above the limit treshhold
any disk so close that can suffers from heat ?

can you report

inxi -Fxxxz

install lm_sensors

sudo pacman -S lm_sensors
lm_sensors-setting
and follow all UPPERCASE YES or NO

Hi Stephane.
Thanks for your reply and assistance.
Here is the result:

System:    Host: pafa-pc Kernel: 4.19.32-1-MANJARO x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: Xfce 4.13.3git-UNKNOWN 
           tk: Gtk 3.24.7 info: xfce4-panel wm: xfwm4 dm: LightDM 1.28.0 Distro: Manjaro Linux 
Machine:   Type: Laptop System: LENOVO product: 2349PS5 v: ThinkPad T430 serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: LENOVO model: 2349PS5 serial: <filter> UEFI [Legacy]: LENOVO v: G1ETB9WW (2.79 ) date: 02/19/2019 
Battery:   ID-1: BAT0 charge: 40.3 Wh condition: 40.5/56.2 Wh (72%) volts: 12.6/10.8 model: SANYO 45N1013 type: Li-ion 
           serial: <filter> status: Charging 
           Device-1: hid-34:88:5d:88:3b:6d-battery model: Bluetooth Mouse M336/M337/M535 serial: N/A charge: N/A 
           status: Discharging 
CPU:       Topology: Dual Core model: Intel Core i5-3320M bits: 64 type: MT MCP arch: Ivy Bridge rev: 9 L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20761 
           Speed: 2836 MHz min/max: 1200/3300 MHz Core speeds (MHz): 1: 2836 2: 2783 3: 2432 4: 2779 
Graphics:  Device-1: Intel 3rd Gen Core processor Graphics vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:0166 
           Display: x11 server: X.Org 1.20.4 driver: intel unloaded: modesetting alternate: fbdev,vesa 
           resolution: 1600x900~60Hz 
           OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 4.2 Mesa 18.3.5 compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 chip ID: 8086:1e20 
           Sound Server: ALSA v: k4.19.32-1-MANJARO 
Network:   Device-1: Intel 82579LM Gigabit Network vendor: Lenovo driver: e1000e v: 3.2.6-k port: 6080 bus ID: 00:19.0 
           chip ID: 8086:1502 
           IF: enp0s25 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi v: kernel port: efa0 bus ID: 03:00.0 
           chip ID: 8086:0085 
           IF: wlp3s0 state: up mac: <filter> 
Drives:    Local Storage: total: 447.13 GiB used: 92.97 GiB (20.8%) 
           ID-1: /dev/sda vendor: Kingston model: SA400S37480G size: 447.13 GiB speed: 6.0 Gb/s serial: <filter> rev: B1C2 
           scheme: MBR 
Partition: ID-1: / size: 439.11 GiB used: 92.93 GiB (21.2%) fs: ext4 dev: /dev/sda1 
Sensors:   System Temperatures: cpu: 59.0 C mobo: N/A 
           Fan Speeds (RPM): cpu: 5080 
Info:      Processes: 228 Uptime: 8m Memory: 7.50 GiB used: 2.72 GiB (36.2%) Init: systemd v: 241 Compilers: gcc: 8.2.1 
           Shell: bash v: 5.0.2 running in: xfce4-terminal inxi: 3.0.32 

FYI I just managed to fix the cpu temp by editing the thinkfan.conf file.
I still have these errors:

-- Logs begin at Fri 2019-04-05 17:00:13 -03, end at Fri 2019-04-05 17:09:09 -03. --
abr 05 17:00:13 pafa-pc systemd-udevd[249]: /etc/udev/rules.d/51-android.rules:2: Invalid key/value pair, starting at character 1 ('S')
abr 05 17:00:13 pafa-pc systemd-udevd[249]: /etc/udev/rules.d/51-android.rules:5: Invalid key/value pair, starting at character 1 ('S')
abr 05 17:00:30 pafa-pc systemd[1]: man-db-mbb.timer: Refusing to start, unit to trigger not loaded.
abr 05 17:00:30 pafa-pc systemd[1]: Failed to start Daily man-db regeneration.
abr 05 17:00:38 pafa-pc systemd-logind[498]: Cannot find the ESP partition mount point.
abr 05 17:09:09 pafa-pc sudo[8785]:     pafa : a password is required ; TTY=pts/1 ; PWD=/home/pafa ; USER=root ; COMMAND=/sbin/hddtemp -nq -u C /dev/sda

I also installed package lenovo-throttling-fix-git but service is not loading. Maybe it’s not compatible with T430 from what I read on the git page.

What do you think.

Thanks for your time.

Best,

Facundo

you can use [ code ] and [/ code ] for your report ( suppress blanks )
or

test

Thanks Stephane. I got it now.

why is you cpu so hot ?
have you check with top / htop ?

can you report

sudo journalctl -b0 -p err ( current boot )

Here is the output of sudo journalctl -b0 -p err

-- Logs begin at Fri 2019-04-05 17:00:13 -03, end at Fri 2019-04-05 17:09:09 -03. --
abr 05 17:00:13 pafa-pc systemd-udevd[249]: /etc/udev/rules.d/51-android.rules:2: Invalid key/value pair, starting at character 1 ('S')
abr 05 17:00:13 pafa-pc systemd-udevd[249]: /etc/udev/rules.d/51-android.rules:5: Invalid key/value pair, starting at character 1 ('S')
abr 05 17:00:30 pafa-pc systemd[1]: man-db-mbb.timer: Refusing to start, unit to trigger not loaded.
abr 05 17:00:30 pafa-pc systemd[1]: Failed to start Daily man-db regeneration.
abr 05 17:00:38 pafa-pc systemd-logind[498]: Cannot find the ESP partition mount point.
abr 05 17:09:09 pafa-pc sudo[8785]:     pafa : a password is required ; TTY=pts/1 ; PWD=/home/pafa ; USER=root ; COMMAND=/sbin/hddtemp -nq -u C /dev/sda

I really don’t know, probably I work under heavy load?

Hi everybody,
I'm still experiencing random system freezing.
I suspect its some kind of configuration problem.
Can anyone help me fix this please?
Thanks
Best,
Facundo

I suspect this is the problem. Do

sudo pacman-mirrors -f5
sudo pacman -Syyuu

If/when asked to 'downgrade' Mesa to version 19.0.1-2 (and related packages) answer yes. (Really an upgrade but package manager sees it as a downgrade. :slightly_smiling_face:)

Looking at the other errors in your log (since I am replying):

Do you sync android devices to your machine? If no remove android-udev, if yes try reinstalling it. If no change you will need someone else to help :relaxed: but it can probably be ignored. (Or look for the problem yourself in the '51-android.rules' file...)

'man-db-mbb.timer` looks non-standard, did you alter this yourself? Normally this is called 'man-db.timer' and I suspect systemd is looking for a matching service, generally called 'man-db.service'. Try renaming (or adjusting the contents if you have manually edited). This one is worth fixing.

The freezes are most likely due to Mesa though. :wink:

1 Like

Hi Grinner,
First of all, thanks for your support.
I already erased the android-udevso that's been solved.
I've run the commands you've indicated and so far so good.
I will try stressing my system a little under my usual workload to check.

On the other hand, I followed the tutorial for man db timer here but was unsuccesfull to complete it. I sent the author mbb a message but haven't heard back from him yet. Do you have any idea how I can rename and get back to normal?

On the other hand I have a journal error that says:

abr 10 13:46:36 pafa-pc systemd-logind[495]: Cannot find the ESP partition mount point.

Do you know how to correct this?

Thanks a million!
Best,
Facundo

PS= System is snappy as hell with the Mesa modification you suggested! I'm running my browser and 3 vms on virtualbox with no issues. I get some freezing when swap has to increase with systemd-swap only. After that, no issues. Thanks a lot for this suggestion.

1 Like

See here

1 Like

Hi bogdancovaciu,
Thanks for your reply. Ok, I'll ignore it then.

Do you know if there's some way to make size of systemd-swap default larger?
It takes some time and freezes when it has to increase swap size.
Thanks.

Best,
Facundo

I use a swapfile on my SSD.
Reading about systemd-swap on here
https://wiki.archlinux.org/index.php/Swap#systemd-swap
and here


didn't make it very clear for me and i will have to investigate/test what is all about.
I'm also looking trough this post to see if there is something i didn't get

not quite clear for me yet :slight_smile:

Hi! Sorry about that.

  1. Try rebooting or issuing sudo systemctl daemon-reload
  2. Make sure both timer and service are present in /etc/systemd/system/
  3. I don't think you need to apply the change in the link I proposed on the other post (try without it first.

Hi mbb thanks for your reply.
This doesn't work. Could you possibly help me revert man db timer to stock?
Thanks.
Best,
Facundo

  1. Disable and stop the timer you created:
sudo systemctl stop man-db-mbb.timer
sudo systemctl disable man-db-mbb.timer
  1. Delete the files:
sudo rm /etc/systemd/system/man-db-mbb*
  1. Start and enable man-db timer:
sudo systemctl start man-db.timer
sudo systemctl enable man-db.timer
  1. Check the links if you changed them:
[mbb@mbb-laptop ~]$ ls -la  /usr/lib/systemd/system/multi-user.target.wants/man-db.timer 
lrwxrwxrwx 1 root root 15 fev 27 16:11 /usr/lib/systemd/system/multi-user.target.wants/man-db.timer -> ../man-db.timer

If the link isn't correct change it to match the timer file.

I don't understand why it didn't work. I tested it and it worked here.

2 Likes

Thanks a lot mbb!
Everything is back to normal now.

journalctl -p err -b
-- Logs begin at Thu 2019-04-11 10:04:25 -03, end at Thu 2019-04-11 10:04:37 -03. --
abr 11 10:04:33 pafa-pc systemd-logind[510]: Cannot find the ESP partition mount point.

Have a nice day.
Best,
Facundo

1 Like

Hi everyone,
Journal errors fixed. Mesa drivers updated. Still freezing sometimes. I suspect its systemd-swap when I run out of ram and it has to increase.
I'm considering creating a swap partition to discard this.
Any suggestions?
Thanks,
Best,
Facundo

You could try this. :grin:

https://wiki.manjaro.org/index.php?title=Add_a_/swapfile

1 Like

Thanks grinner.
I just created the swap and disabled systemd-swap.
Performance has improved a little:

free -h
              total        used        free      shared  buff/cache   available
Mem:          7,5Gi       2,7Gi       2,9Gi       460Mi       2,0Gi       4,1Gi
Swap:         8,0Gi       815Mi       7,2Gi

Best,
Facundo