Random freezes on lubuntu 18.04.3 LTS

I am using lubuntu on Intel corporation Atom processor Z36xxx/Z37xxx series Graphics and running chromium version on it.
Problem Statement : Our system freezes randomly and only solution left is to restart and its not very good solution.Can anyone help with it.

Nov 26 02:54:20 wdtsadmin NetworkManager[559]: [1606330460.5896] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 26 02:54:20 wdtsadmin dbus-daemon[505]: [system] Activating via systemd: service name=‘org.freedesktop.UPower’ unit=‘upower.service’ requested by ‘:1.20’ (uid=1000 pid=728 comm="/usr/lib/chromium-browser/chromium-browser --enabl" label=“unconfined”)
Nov 26 02:54:20 wdtsadmin NetworkManager[559]: [1606330460.5965] manager: NetworkManager state is now CONNECTED_SITE
Nov 26 02:54:20 wdtsadmin NetworkManager[559]: [1606330460.5969] policy: set ‘netplan-enp3s0’ (enp3s0) as default for IPv4 routing and DNS
Nov 26 02:54:20 wdtsadmin NetworkManager[559]: [1606330460.5971] device (enp3s0): Activation: successful, device activated.
Nov 26 02:54:20 wdtsadmin nm-dispatcher: req:2 ‘up’ [enp3s0]: new request (2 scripts)
Nov 26 02:54:20 wdtsadmin NetworkManager[559]: [1606330460.6012] manager: NetworkManager state is now CONNECTED_GLOBAL
Nov 26 02:54:20 wdtsadmin nm-dispatcher: req:2 ‘up’ [enp3s0]: start running ordered scripts…
Nov 26 02:54:20 wdtsadmin systemd[1]: Starting Daemon for power management…
Nov 26 02:54:20 wdtsadmin nm-dispatcher: req:3 ‘connectivity-change’: new request (2 scripts)
Nov 26 02:54:20 wdtsadmin ntpdate[996]: the NTP socket is in use, exiting
Nov 26 02:54:20 wdtsadmin systemd[1]: Reloading OpenBSD Secure Shell server.
Nov 26 02:54:20 wdtsadmin nm-dispatcher: req:3 ‘connectivity-change’: start running ordered scripts…
Nov 26 02:54:20 wdtsadmin systemd[1]: Reloaded OpenBSD Secure Shell server.
Nov 26 02:54:20 wdtsadmin dbus-daemon[505]: [system] Successfully activated service ‘org.freedesktop.UPower’
Nov 26 02:54:20 wdtsadmin systemd[1]: Started Daemon for power management.
Nov 26 02:54:21 wdtsadmin avahi-daemon[541]: Joining mDNS multicast group on interface enp3s0.IPv6 with address fe80::72b3:d5ff:fe66:631a.
Nov 26 02:54:21 wdtsadmin avahi-daemon[541]: New relevant interface enp3s0.IPv6 for mDNS.
Nov 26 02:54:21 wdtsadmin avahi-daemon[541]: Registering new address record for fe80::72b3:d5ff:fe66:631a on enp3s0.*.
Nov 26 02:54:21 wdtsadmin set-cpufreq[556]: Setting powersave scheduler for all CPUs
Nov 26 02:54:22 wdtsadmin NetworkManager[559]: [1606330462.8132] arping[0x2214f40,2]: arping could not be found; no ARPs will be sent
Nov 26 02:54:22 wdtsadmin kernel: [ 17.163556] e1000e: enp3s0 NIC Link is Down
Nov 26 02:54:26 wdtsadmin NetworkManager[559]: [1606330466.5708] manager: startup complete
Nov 26 02:54:26 wdtsadmin systemd[1]: Started Network Manager Wait Online.
Nov 26 02:54:26 wdtsadmin systemd[1]: Reached target Network is Online.
Nov 26 02:54:26 wdtsadmin systemd[1]: Starting Tool to automatically collect and submit kernel crash signatures…
Nov 26 02:54:26 wdtsadmin systemd[1]: Started crash report submission daemon.
Nov 26 02:54:26 wdtsadmin systemd[1]: kerneloops.service: Found left-over process 1035 (kerneloops) in control group while starting unit. Ignoring.
Nov 26 02:54:26 wdtsadmin systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Nov 26 02:54:26 wdtsadmin systemd[1]: Started Tool to automatically collect and submit kernel crash signatures.
Nov 26 02:54:26 wdtsadmin systemd[1]: Reached target Multi-User System.
Nov 26 02:54:26 wdtsadmin systemd[1]: Reached target Graphical Interface.
Nov 26 02:54:26 wdtsadmin systemd[1]: Started Stop ureadahead data collection 45s after completed startup.
Nov 26 02:54:26 wdtsadmin systemd[1]: Starting Update UTMP about System Runlevel Changes…
Nov 26 02:54:26 wdtsadmin whoopsie[1034]: [02:54:26] Using lock path: /var/lock/whoopsie/lock
Nov 26 02:54:26 wdtsadmin systemd[1]: Started Update UTMP about System Runlevel Changes.
Nov 26 02:54:26 wdtsadmin systemd[1]: Startup finished in 7.757s (kernel) + 13.074s (userspace) = 20.832s.
Nov 26 02:54:26 wdtsadmin whoopsie[1034]: [02:54:26] The default IPv4 route is: /org/freedesktop/NetworkMan

Freezing? or is it thrashing? (is the disk light solid or near solid on during what you call freeze?)
What do you mean by restart? SysRq commands telling kernel to restart or something else? Are you logging into text terminal and telling it to reboot or what?

Your system is behind on upgrades I suspect, an fully updated 18.04 system should report itself as 18.04.5

I currently aren’t sure if you’re describing a thrashing situation;

  • how much RAM is there?
  • do you have swap enabled?
  • is the machine getting hot? (cpus can slow down when they get hot as they add pause states in attempt to reduce heat, and appear to be frozen, once cooler they’ll continue if you wait long enough but you should feel the heat, some cpus just turn off - I don’t know the behavior of your cpu).

You’re also describing hardware issues (esp. warning signs), so have you checked your hardware itself? via use of a live system? Does it act the same there doing the same thing?

What did you paste? It’s best if we’re told, rather than guessing what we’re looking at.

1 Like

Thanks for your response …
When i say freeing means we are not able to perform any action on UI .Also i did mention graphics just for refrence so that you guys have system information.
Restart means i have to power cycle my system.

Ram- : 4GB
Swap -: yes
SwapTotal: 359928 kB
SwapFree: 359928 kB
No we did not observe any heat issue and I have added few suspected line from syslog as i was not able to add complete log here.

When the system is frozen…

  1. what were you doing just before?
  2. how many applications were you running?
  3. how much RAM was left (keep the process manager open and on top while using the computer and you’ll be able to figure that out)?
  4. can you move the mouse?
  5. can you open a virtual terminal (e.g. CtrlAltF3)?
  6. is the light indicating disk activity lit, especially if constant or near constant?

Also, you said:

Which ones do you suspect? Which ones coincide withe the time of the freeze?

Please find my input inline.

  1. what were you doing just before?
    MS : Running a chromium browser offline.
  2. how many applications were you running?
    MS : Just one
  3. how much RAM was left (keep the process manager open and on top while using the computer and you’ll be able to figure that out)?
    MS : More than half of ram was there.
  4. can you move the mouse?
    MS : No and also touch screen doesn’t work.
  5. can you open a virtual terminal (e.g. CtrlAltF3)?
    MS : yes
  6. is the light indicating disk activity lit, especially if constant or near constant?
    MS : How can we check it as it looks good to me.

I was suspectecting these line, as TZ was difference still working to figure out exact time stamp but we do see these lines during same time of incident.

Nov 26 02:54:19 wdtsadmin systemd[696]: Started Virtual filesystem service.
Nov 26 02:54:19 wdtsadmin ModemManager[560]: Couldn’t check support for device ‘/sys/devices/pci0000:00/0000:00:1c.2/0000:03:00.0’: not supported by any plugin
Nov 26 02:54:19 wdtsadmin ModemManager[560]: Couldn’t check support for device ‘/sys/devices/pci0000:00/0000:00:1c.3/0000:04:00.0’: not supported by any plugin
Nov 26 02:54:19 wdtsadmin dbus-daemon[505]: [system] Activating via systemd: service name=‘org.bluez’ unit=‘dbus-org.bluez.service’ requested by ‘:1.19’ (uid=1000 pid=728 comm="/usr/lib/chromium-browser/chromium-browser --enabl" label=“unconfined”)
Nov 26 02:54:20 wdtsadmin dbus-daemon[747]: [session uid=1000 pid=747] Activating via systemd: service name=‘org.freedesktop.Notifications’ unit=‘xfce4-notifyd.service’ requested by ‘:1.6’ (uid=1000 pid=728 comm="/usr/lib/chromium-browser/chromium-browser --enabl" label=“unconfined”)
Nov 26 02:54:20 wdtsadmin systemd[696]: Starting XFCE notifications service…
Nov 26 02:54:20 wdtsadmin xfce4-notifyd[847]: Unable to init server: Could not connect: Connection refused
Nov 26 02:54:20 wdtsadmin xfce4-notifyd[847]: cannot open display:
Nov 26 02:54:20 wdtsadmin systemd[696]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE
Nov 26 02:54:20 wdtsadmin systemd[696]: xfce4-notifyd.service: Failed with result ‘exit-code’.
Nov 26 02:54:20 wdtsadmin systemd[696]: Failed to start XFCE notifications service.

  1. What does that mean you were running Chromium offline? Be more specific. It seems strange to use an Internet browser offline.
  2. So the keyboard works, which tells us that your machine is actually NOT frozen. You could log into the virtual terminal and run sudo service lightdm restart and it would basically kill your X session and start a new one. So you certainly don’t need to restart the computer.
  3. How can you check if a light is lit? Um. You look at it? You could also use the process manager to monitor disk i/o.
  4. So which lines do you see in common every time this happens? I really don’t see anything particularly problematic here except for the fact that Chromium seems to want to send notifications and the basic service cannot start. This may be helped by retracting notification permissions. I don’t think this is the case, but are you using the Chromium Snap package?
  1. What does that mean you were running Chromium offline? Be more specific. It seems strange to use an Internet browser offline.

MS : it’s requirement, where I am supposed to run angular based application on internal network using chromium .

  1. So the keyboard works, which tells us that your machine is actually NOT frozen. You could log into the virtual terminal and run sudo service lightdm restart and it would basically kill your X session and start a new one. So you certainly don’t need to restart the computer.

MS: No keywords does not work it’s just we are able to ssh most of time.i will try to restart it but eventually it will impact my operation.

  1. How can you check if a light is lit? Um. You look at it? You could also use the process manager to monitor disk i/o.

Ms: Ok I will look into it and update you.

  1. So which lines do you see in common every time this happens? I really don’t see anything particularly problematic here except for the fact that Chromium seems to want to send notifications and the basic service cannot start. This may be helped by retracting notification permissions. I don’t think this is the case, but are you using the Chromium Snap package?

Ms: That’s only line I was suspecting and there is nothing common in sys log .Could you please, suggest anything which can help to debug this issue.

What is this application you’re using? Specifics, please. That may be your problem right there. Do you have any problems using Chromium with the regular internet? If not, then I would be inclined to blame that application first.

Also: if you’re using an application with any network, regardless of how connected you may or may not be with the wider internet, you’re not working offline.

If you can open a virtual terminal with the keyboard (remember, that’s what I suggested), then the keyboard works. Now if you decided to ignore what I suggested and tried using ssh, that’s testing something else, but if you can get in with ssh at all (even to the point that you can connect or authenticate), then the computer is also not frozen. Stalled or overtaxed might be the right word.

You didn’t answer me: are you using the Chromium Snap package?

And turn those notifications off like I said.

Thanks for you consistant response.I am using a web application developed on angular and hosted on nginx webserver and through internal network i do access it from a box running on lubuntu and i use chromium kiosk mode to access it.

As i do use a full screen in kiosk mode and no touch is working on screen for that particular time.How do i access terminal ?

my bad i missed that question. I am using .deb package.

I will turn off all chromium notification and update you.

So this application is something that you can’t tell us about? If that’s the case, I assume it’s not something that’s public and something developed on your own or via whatever organization you’re with or whatever. In any case, if you have no problems with anything else except when you’re using that, then it’s reasonable to conclude the problem is with the application.

As i mentioned this application is not accesible to internet and as i shared its very simple web based application developed in angular.
Can you suggest any step which can help me to debug and rule out os issue, i do have syslog, kernel.log but unfortunately i cant add it here ?

A very simple application can still cause massive problems. You should talk to the developer of the application.

Agree but it is developed by me only and we figured out we did observed issue because of hardware driver was not correct.
Thanks for your support .

This topic was automatically closed 60 minutes after the last reply. New replies are no longer allowed.