You are Here:
Download Linux Lite 5.6 Final today - See Release Announcements



X Close Ad
X Close Ad
[ ABANDONED ] System freeze-up

Author (Read 3400 times)

0 Members and 2 Guests are viewing this topic.

Re: System freeze-up
« Reply #15 on: May 07, 2021, 08:22:56 PM »
 

lintek

  • Occasional Poster
  • **
  • 85
    Posts
  • Country: us
  • Reputation: 2
  • Linux Lite Member

  • Linux Lite: 5.2 64bit

  • CPU: Intel Core i3-2120 CPU @ 3.30GHz

  • MEMORY: 8Gb

  • VIDEO CARD: EVGA GT710

  • Kernel: 5.x
Tried line 1 - got this

"Failed to add match 'priority': Invalid argument"

Also tried upgrading from 5.2 to 5.4

NO LUCK. I am about ready to just reinstall.

Last Edit: May 07, 2021, 08:53:18 PM by lintek
 


Re: System freeze-up
« Reply #16 on: May 07, 2021, 10:26:44 PM »
 

Moltke

  • Platinum Level Poster
  • **********
  • 1036
    Posts
  • Country: ve
  • Reputation: 120
  • Linux Lite Member

  • Linux Lite: 5.0 64bit

  • CPU: amd athlon 64 x2

  • MEMORY: 4Gb

  • VIDEO CARD: amd radeon hd 6750

  • Kernel: 5.x
Tried line 1 - got this

"Failed to add match 'priority': Invalid argument"

Also tried upgrading from 5.2 to 5.4

NO LUCK. I am about ready to just reinstall.

Oops! Sorry, my bad! I missed "--" before and  "=" after priority this is the correct command
Code: [Select]
sudo journalctl --priority=err --since "10 min ago"
Again, really sorry I didn't realize that earlier when I posted. Try again, it should work this time.
Last Edit: May 07, 2021, 10:28:51 PM by Moltke
Without each others help there ain't no hope for us :)
Need a translation service? https://www.deepl.com/es/translator
 

Re: System freeze-up
« Reply #17 on: May 08, 2021, 10:42:17 AM »
 

lintek

  • Occasional Poster
  • **
  • 85
    Posts
  • Country: us
  • Reputation: 2
  • Linux Lite Member

  • Linux Lite: 5.2 64bit

  • CPU: Intel Core i3-2120 CPU @ 3.30GHz

  • MEMORY: 8Gb

  • VIDEO CARD: EVGA GT710

  • Kernel: 5.x
I am about ready to shoot my Linux Lite.

Since I can barely try any of the things you suggest due to freezing up, I decided to drop in a new hard rive and load a fresh copy of 5.4 onto it.

AND IT STILL FROZE UP.  With Firefox on, with firefox off, with chromium on with chromium off, with a different mouse, etc etc.

At this point I cannot imagine what is causing this. 

But this is a dual boot computer and luckily my old copy of Windows 7 works.
 

Re: System freeze-up
« Reply #18 on: May 08, 2021, 11:26:11 AM »
 

Moltke

  • Platinum Level Poster
  • **********
  • 1036
    Posts
  • Country: ve
  • Reputation: 120
  • Linux Lite Member

  • Linux Lite: 5.0 64bit

  • CPU: amd athlon 64 x2

  • MEMORY: 4Gb

  • VIDEO CARD: amd radeon hd 6750

  • Kernel: 5.x
While in the desktop, xfce, press Ctrl + Alt + F1 to jump to a TTY(command line mode) login with your credentials; username and password. Then run the journalctl command, but since you can't copy/paste the output in that mode, you'll have to redirect it to a file, like this
Code: [Select]
sudo journalctl --priority=err --since "30 min ago" > journalctl_output name it whatever else you want to, the file will be saved in your home directory, if by any chance you get no output, or it is too short, like 3 lines short or something like that, you can, 1) increase the time, i.e. "60", 2) run without time which will print the whole thing in which case you'll have to attach the file in your reply since it'll be very long for coping/pasting, once you've done that,  press Ctrl + d to logout from that session, then press Ctrl + Alt + F7 to return to the desktop session, find the file, open it in a text editor and copy/paste the output here, or attach it if it is too long as explained above. The system shouldn't freeze in that mode, and if it does, then the problem might be a graphics related thing, I think. The output of journalctl might give us a hint whether it is or not.
Last Edit: May 08, 2021, 11:35:18 AM by Moltke
Without each others help there ain't no hope for us :)
Need a translation service? https://www.deepl.com/es/translator
 

Re: System freeze-up
« Reply #19 on: May 12, 2021, 12:54:12 AM »
 

lintek

  • Occasional Poster
  • **
  • 85
    Posts
  • Country: us
  • Reputation: 2
  • Linux Lite Member

  • Linux Lite: 5.2 64bit

  • CPU: Intel Core i3-2120 CPU @ 3.30GHz

  • MEMORY: 8Gb

  • VIDEO CARD: EVGA GT710

  • Kernel: 5.x
journalctl_output
Code: [Select]
-- Logs begin at Sat 2021-05-08 00:08:36 CDT, end at Tue 2021-05-11 23:47:25 CDT. --
May 11 23:42:54 linux-DX4860 systemd[1]: Failed to start Show Plymouth Boot Screen.
May 11 23:42:59 linux-DX4860 ntpd[1214]: error resolving pool 0.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:43:00 linux-DX4860 /hpfax[1260]: [1260]: error: Failed to create /var/spool/cups/tmp/.hplip
May 11 23:43:00 linux-DX4860 ntpd[1214]: error resolving pool 1.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:43:01 linux-DX4860 ntpd[1214]: error resolving pool 2.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:43:01 linux-DX4860 nmbd[1301]: [2021/05/11 23:43:01.784944,  0] ../../lib/util/become_daemon.c:147(daemon_status)
May 11 23:43:01 linux-DX4860 nmbd[1301]:   daemon_status: daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...
May 11 23:43:01 linux-DX4860 nmbd[1301]: [2021/05/11 23:43:01.785037,  0] ../../source3/nmbd/nmbd_subnetdb.c:253(create_subnets)
May 11 23:43:01 linux-DX4860 nmbd[1301]:   NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
May 11 23:43:02 linux-DX4860 ntpd[1214]: error resolving pool 3.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:43:03 linux-DX4860 ntpd[1214]: error resolving pool ntp.ubuntu.com: Temporary failure in name resolution (-3)
May 11 23:43:32 linux-DX4860 pulseaudio[1287]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
-- Reboot --
May 11 23:44:22 linux-DX4860 systemd[1]: Failed to start Show Plymouth Boot Screen.
May 11 23:44:26 linux-DX4860 ntpd[1169]: error resolving pool 0.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:44:27 linux-DX4860 ntpd[1169]: error resolving pool 1.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:44:27 linux-DX4860 /hpfax[1211]: [1211]: error: Failed to create /var/spool/cups/tmp/.hplip
May 11 23:44:28 linux-DX4860 ntpd[1169]: error resolving pool 2.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:44:29 linux-DX4860 nmbd[1227]: [2021/05/11 23:44:29.407539,  0] ../../lib/util/become_daemon.c:147(daemon_status)
May 11 23:44:29 linux-DX4860 nmbd[1227]:   daemon_status: daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...
May 11 23:44:29 linux-DX4860 nmbd[1227]: [2021/05/11 23:44:29.407610,  0] ../../source3/nmbd/nmbd_subnetdb.c:253(create_subnets)
May 11 23:44:29 linux-DX4860 nmbd[1227]:   NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
May 11 23:44:29 linux-DX4860 ntpd[1169]: error resolving pool 3.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:44:30 linux-DX4860 ntpd[1169]: error resolving pool ntp.ubuntu.com: Temporary failure in name resolution (-3)
May 11 23:45:00 linux-DX4860 pulseaudio[1245]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
-- Reboot --
May 11 23:45:57 linux-DX4860 systemd[1]: Failed to start Show Plymouth Boot Screen.
May 11 23:46:01 linux-DX4860 ntpd[1173]: error resolving pool 0.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:46:02 linux-DX4860 ntpd[1173]: error resolving pool 1.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:46:02 linux-DX4860 /hpfax[1222]: [1222]: error: Failed to create /var/spool/cups/tmp/.hplip
May 11 23:46:03 linux-DX4860 ntpd[1173]: error resolving pool 2.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:46:04 linux-DX4860 nmbd[1231]: [2021/05/11 23:46:04.320142,  0] ../../lib/util/become_daemon.c:147(daemon_status)
May 11 23:46:04 linux-DX4860 nmbd[1231]:   daemon_status: daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...
May 11 23:46:04 linux-DX4860 nmbd[1231]: [2021/05/11 23:46:04.320892,  0] ../../source3/nmbd/nmbd_subnetdb.c:253(create_subnets)
May 11 23:46:04 linux-DX4860 nmbd[1231]:   NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
May 11 23:46:04 linux-DX4860 ntpd[1173]: error resolving pool 3.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:46:05 linux-DX4860 ntpd[1173]: error resolving pool ntp.ubuntu.com: Temporary failure in name resolution (-3)
May 11 23:46:35 linux-DX4860 pulseaudio[1249]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
May 11 23:47:05 linux-DX4860 ntpd[1173]: error resolving pool 0.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:47:08 linux-DX4860 ntpd[1173]: error resolving pool 3.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:47:08 linux-DX4860 ntpd[1173]: error resolving pool 1.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:47:10 linux-DX4860 ntpd[1173]: error resolving pool 2.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:47:11 linux-DX4860 ntpd[1173]: error resolving pool ntp.ubuntu.com: Temporary failure in name resolution (-3)
 

Re: System freeze-up
« Reply #20 on: May 12, 2021, 08:36:21 AM »
 

Moltke

  • Platinum Level Poster
  • **********
  • 1036
    Posts
  • Country: ve
  • Reputation: 120
  • Linux Lite Member

  • Linux Lite: 5.0 64bit

  • CPU: amd athlon 64 x2

  • MEMORY: 4Gb

  • VIDEO CARD: amd radeon hd 6750

  • Kernel: 5.x
Just to be clear, is that output from right after the system froze? If it is, there are some errors that might explain the freezing issue.
Without each others help there ain't no hope for us :)
Need a translation service? https://www.deepl.com/es/translator
 

Re: System freeze-up
« Reply #21 on: May 12, 2021, 11:43:02 AM »
 

lintek

  • Occasional Poster
  • **
  • 85
    Posts
  • Country: us
  • Reputation: 2
  • Linux Lite Member

  • Linux Lite: 5.2 64bit

  • CPU: Intel Core i3-2120 CPU @ 3.30GHz

  • MEMORY: 8Gb

  • VIDEO CARD: EVGA GT710

  • Kernel: 5.x
That is the output before the system had a chance to freeze.  If I hit Ctrl+Alt+F1 then the only thing that happens is I lose my cursor and can't do anything (much like when the system freezes) and I have to hold down power button to reboot.
 

Re: System freeze-up
« Reply #22 on: May 12, 2021, 03:04:04 PM »
 

j8a

  • New to Forums
  • *
  • 34
    Posts
  • Country: ar
  • Reputation: 3
  • Linux Lite Member

  • Linux Lite: 5.4 64bit

  • CPU: AMD FX-8320E Buldozer

  • MEMORY: 8Gb

  • VIDEO CARD: NVIDIA C61 [GeForce 7025 / nForce 630a]

  • Kernel: 5.x
Hi @lintek ,
I think you have the Network Manager down which can be solved whether you could type the folloswing command in a terminal:
systemctl status avahi-daemon.service

The output text on the terminal looks like this:

systemctl status avahi-daemon.service
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
     Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor >
     Active: active (running) since Wed 2021-05-12 15:43:13 -03; 12min ago
TriggeredBy: ● avahi-daemon.socket
   Main PID: 655 (avahi-daemon)
     Status: "avahi-daemon 0.7 starting up."
      Tasks: 2 (limit: 9042)
     Memory: 2.1M
     CGroup: /system.slice/avahi-daemon.service
             ├─655 avahi-daemon: running [jochoa-pc.local]
             └─730 avahi-daemon: chroot helper
.......

Then, go to your Network Manager icon on the task bar and click on it and disable Enable Networking (whichi is ticked).
Afterwards, click on the icon and check the Enable Networking.

 
Hope this help, regards
 

Re: System freeze-up
« Reply #23 on: May 12, 2021, 03:37:47 PM »
 

lintek

  • Occasional Poster
  • **
  • 85
    Posts
  • Country: us
  • Reputation: 2
  • Linux Lite Member

  • Linux Lite: 5.2 64bit

  • CPU: Intel Core i3-2120 CPU @ 3.30GHz

  • MEMORY: 8Gb

  • VIDEO CARD: EVGA GT710

  • Kernel: 5.x
I tried what you said - this is what happened.
Code: [Select]
May 12 14:24:42 linux-DX4860 avahi-daemon[906]: New relevant interface wlp3s0.IPv6 for mDNS.
May 12 14:24:42 linux-DX4860 avahi-daemon[906]: Registering new address record for fe80::7253:5e21:7b24:bc66 on wlp3s0.*.
May 12 14:24:43 linux-DX4860 avahi-daemon[906]: Joining mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.2.
May 12 14:24:43 linux-DX4860 avahi-daemon[906]: New relevant interface wlp3s0.IPv4 for mDNS.
May 12 14:24:43 linux-DX4860 avahi-daemon[906]: Registering new address record for 192.168.1.2 on wlp3s0.IPv4.
May 12 14:24:49 linux-DX4860 avahi-daemon[906]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fe80::7253:5e21:7b24:bc66.
May 12 14:24:49 linux-DX4860 avahi-daemon[906]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address 2600:100c:b01e:66ac:fd3a:2>
May 12 14:24:49 linux-DX4860 avahi-daemon[906]: Registering new address record for 2600:100c:b01e:66ac:fd3a:2c53:888e:fa8f on wlp3s0.*.
May 12 14:24:49 linux-DX4860 avahi-daemon[906]: Withdrawing address record for fe80::7253:5e21:7b24:bc66 on wlp3s0.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~

 linux  ~  130 

Not sure if it worked or not, because now Linux won't even log into the network connections that I have been using.  I have two and I have used both with Linux, now it fails to log into them.

Also, I really don't understand how I still have the same problem I started with considering I uploaded a complete fresh install of 5.4, on a NEW hard drive.    :shrug

Last Edit: May 12, 2021, 04:04:02 PM by lintek
 

Re: System freeze-up
« Reply #24 on: May 12, 2021, 11:05:30 PM »
 

Moltke

  • Platinum Level Poster
  • **********
  • 1036
    Posts
  • Country: ve
  • Reputation: 120
  • Linux Lite Member

  • Linux Lite: 5.0 64bit

  • CPU: amd athlon 64 x2

  • MEMORY: 4Gb

  • VIDEO CARD: amd radeon hd 6750

  • Kernel: 5.x
That is the output before the system had a chance to freeze.  If I hit Ctrl+Alt+F1 then the only thing that happens is I lose my cursor and can't do anything (much like when the system freezes) and I have to hold down power button to reboot.

Ok, I'll try to explain better this time:
1. By pressing Ctrl + Alt + F1 you'll be dropped to a console; a black screen with a blinking cursor, give it a few seconds and you'll see login type in your username and password, press enter and you'll be logged in a  TTY, you can issue commands from there, navigate the system, and do pretty much the same things you can in a terminal from the desktop, but the mouse won't work while in there, that's normal.
2. In that console run the journalctl command, because the messages you posted are from when you rebooted the machine.
3. It would be better if you did this when the system freezes, just be patient after pressing those keys and wait until the TTY starts, then proceed as explained above.
Without each others help there ain't no hope for us :)
Need a translation service? https://www.deepl.com/es/translator
 

Re: System freeze-up
« Reply #25 on: May 13, 2021, 12:59:57 AM »
 

lintek

  • Occasional Poster
  • **
  • 85
    Posts
  • Country: us
  • Reputation: 2
  • Linux Lite Member

  • Linux Lite: 5.2 64bit

  • CPU: Intel Core i3-2120 CPU @ 3.30GHz

  • MEMORY: 8Gb

  • VIDEO CARD: EVGA GT710

  • Kernel: 5.x
What I am saying is I did hit CTRL+ALT+F1 and I did NOT get the terminal.  The cursor disappeared and that was it.  I had to reboot.
 

Re: System freeze-up
« Reply #26 on: May 13, 2021, 09:20:31 AM »
 

Moltke

  • Platinum Level Poster
  • **********
  • 1036
    Posts
  • Country: ve
  • Reputation: 120
  • Linux Lite Member

  • Linux Lite: 5.0 64bit

  • CPU: amd athlon 64 x2

  • MEMORY: 4Gb

  • VIDEO CARD: amd radeon hd 6750

  • Kernel: 5.x
What I am saying is I did hit CTRL+ALT+F1 and I did NOT get the terminal.  The cursor disappeared and that was it.  I had to reboot.

Hmmm ... Well, try with Ctrl + Alt + F3 you have 6 TTYs to open from F1-F6. Maybe F1 was busy. However, like I said, give it a few seconds for the TTY to start, just don't reboot right away. If you can't do that, open a file manager, navigate to /var/log/, locate the messages file and copy it to your /home directory, and attach the file in your reply.
Without each others help there ain't no hope for us :)
Need a translation service? https://www.deepl.com/es/translator
 

Re: System freeze-up
« Reply #27 on: May 13, 2021, 09:54:51 AM »
 

lintek

  • Occasional Poster
  • **
  • 85
    Posts
  • Country: us
  • Reputation: 2
  • Linux Lite Member

  • Linux Lite: 5.2 64bit

  • CPU: Intel Core i3-2120 CPU @ 3.30GHz

  • MEMORY: 8Gb

  • VIDEO CARD: EVGA GT710

  • Kernel: 5.x
Ok - I will try when I have a bit of time.  I do appreciate all of your help!
 

Re: System freeze-up
« Reply #28 on: May 15, 2021, 03:09:47 PM »
 

lintek

  • Occasional Poster
  • **
  • 85
    Posts
  • Country: us
  • Reputation: 2
  • Linux Lite Member

  • Linux Lite: 5.2 64bit

  • CPU: Intel Core i3-2120 CPU @ 3.30GHz

  • MEMORY: 8Gb

  • VIDEO CARD: EVGA GT710

  • Kernel: 5.x
At least for now I am abandoning this thread - I fixed the problem by installing Linux Mint.

I haven't ever spent much time with Mint and since LL doesn't like my computer right now (and Mint does) I will see how this works for me.  I really appreciate all of the help from you guys and I'm not going anywhere because I have a few computers with  LL on them.

THANKS!
 

Re: System freeze-up
« Reply #29 on: May 15, 2021, 04:54:08 PM »
 

Artim

  • Always Learning
  • PayPal Supporter
  • I come here a lot
  • *****
  • 485
    Posts
  • Country: us
  • Reputation: 64
  • All the Cool Kids Use Linux Lite!
    • Confessions of a Technophobe

  • Linux Lite: 5.4 64bit

  • CPU: Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz

  • MEMORY: 3Gb

  • VIDEO CARD: Mobile GM965/GL960 Integrated Graphics Controller

  • Kernel: 5.x
Try out the Xfce flavor. It may be better on resources than the standard Mint. But I still think preserving the /home partition is what messed you up, @lintek . It has all your old desktop settings and stuff, and saving them from one distro to another can foul up any desktop.
 


Tags:
 

X Close Ad
X Close Ad

Download Linux Lite 5.6 Final today - See Release Announcements