Linux Mint 20.2 Performance Issues and DE Locking Up SOLVED

Alexzee

Well-Known Member
Joined
Jun 1, 2019
Messages
4,183
Reaction score
2,291
Credits
25,718
I'm trying to figure out what is going on with my buddy's Linux Mint 20.2 Cinnamon install.

A few days ago the DE and FF locked up and CTRL + Alt + DEL or CTRL +Alt+ F1 or F2 was unresponsive.
A hard shut down was the only way to reboot.
Again today, while the FF browser was up and running the screen locked up. So he rebooted as the same above combo keys were unresponsive like before.

Approx, 15 minutes or so later FF locked up again. Seconds later there were small circle images on top of a black screen. The screen flashed moments later and showed FF and all the tabs open for 3-5 seconds. The screen then flashed and returned to a black screen with small squares about one inch by one inch images of different colors in various places on the DE.
Looked like screen tearing to me.

After telling my friend to try to drop to a TTY login was unresponsive. Waited a few minutes and the message about:
Code:
 Deauthentication by local choice 3=DEAUTH_LEAVING
appeared on a black screen that was also unresponsive and he had to perform a hard shut down.

I checked the system log and highlighted the Warning in the screenshot. Also the output from the dmesg log is on Pastebin here: https://pastebin.com/fNsJgXTx

Any assistance is greatly appreciated.
 

Attachments

  • Syslog.png
    Syslog.png
    386.7 KB · Views: 142
  • Deauth1.jpg
    Deauth1.jpg
    1 MB · Views: 97
  • Deauth2.jpg
    Deauth2.jpg
    1.2 MB · Views: 98


Has freedesktop been a part of the install for very long ?

Is the LM20.2 a recent install ?

When he first boots, have him right click and refresh/retart cinnamon....is he in the habit of updating everything....and regularly ?
 
Check specs and space on hdd/ssd
 
Has freedesktop been a part of the install for very long ?

Is the LM20.2 a recent install ?

When he first boots, have him right click and refresh/retart cinnamon....is he in the habit of updating everything....and regularly ?
I'm not sure and didn't know that freedesktop was installed:-

Yes, LM 20.2 has been installed for the last 3 years.
Yeah, he is in the habit of updating it pretty much every time he is on that machine.

I'll have him right click on refresh/restart Cinnamon tomorrow. It's late now.
 
Check specs and space on hdd/ssd
LM 20.2 is installed on a 128 GB SSD and he's got 38 gig's free.

By specs do you mean what CPU, GPU and the mobo manufacturer?
 
Last edited:
inxi -Fxz
 
He was able to restart Cinnamon so that's done.

Here's the specs:
Code:
~$ lspci
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d4)
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d4)
00:1c.7 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #8 (rev d4)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Z87 Express LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series]
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8192CE PCIe Wireless Network Adapter (rev 01)
04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 13)
05:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)
 
inxi -Fxz
Code:
nxi -Fxz
System:
  Kernel: 5.4.0-195-generic x86_64 bits: 64 compiler: gcc v: 9.4.0
  Desktop: Cinnamon 5.0.7 Distro: Linux Mint 20.2 Uma
  base: Ubuntu 20.04 focal
Machine:
  Type: Desktop System: MSI product: MS-7845 v: 1.0 serial: <filter>
  Mobo: MSI model: Z87-GD65 GAMING (MS-7845) v: 1.0 serial: <filter>
  BIOS: American Megatrends v: 1.2 date: 05/17/2013
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M325
  charge: 100% (should be ignored) status: Discharging
CPU:
  Topology: Quad Core model: Intel Core i7-4770K bits: 64 type: MT MCP
  arch: Haswell rev: 3 L2 cache: 8192 KiB
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  bogomips: 56000
  Speed: 1001 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 1001 2: 1000
  3: 1000 4: 1000 5: 1001 6: 1000 7: 1000 8: 1000
Graphics:
  Device-1: AMD Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]
  vendor: Micro-Star MSI driver: radeon v: kernel bus ID: 01:00.0
  Display: x11 server: X.Org 1.20.13 driver: ati,radeon
  unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz
  OpenGL: renderer: AMD PITCAIRN (DRM 2.50.0 5.4.0-195-generic LLVM 12.0.0)
  v: 4.5 Mesa 21.2.6 direct render: Yes
Audio:
  Device-1: Intel 8 Series/C220 Series High Definition Audio
  vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 00:1b.0
  Device-2: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000
  Series]
  vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 01:00.1
  Sound Server: ALSA v: k5.4.0-195-generic
Network:
  Device-1: Realtek RTL8192CE PCIe Wireless Network Adapter
  driver: rtl8192ce v: kernel port: d000 bus ID: 03:00.0
  IF: wlp3s0 state: up mac: <filter>
  Device-2: Qualcomm Atheros Killer E220x Gigabit Ethernet
  vendor: Micro-Star MSI driver: alx v: kernel port: c000 bus ID: 04:00.0
  IF: enp4s0 state: down mac: <filter>
Drives:
  Local Storage: total: 696.79 GiB used: 74.77 GiB (10.7%)
  ID-1: /dev/sda vendor: SanDisk model: SDSSDH2128G size: 119.24 GiB
  ID-2: /dev/sdb vendor: Western Digital model: WD5000BEVT-22A0RT0
  size: 465.76 GiB
  ID-3: /dev/sdc vendor: Hitachi model: HTS542512K9SA00 size: 111.79 GiB
Partition:
  ID-1: / size: 116.81 GiB used: 74.77 GiB (64.0%) fs: ext4 dev: /dev/sda1
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: radeon temp: 58 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 252 Uptime: 12m Memory: 15.57 GiB used: 1.93 GiB (12.4%)
  Init: systemd runlevel: 5 Compilers: gcc: 9.4.0 Shell: bash v: 5.0.17
  inxi: 3.0.38
 
Just out of sheer curiosity, I am wondering what the intended purpose of the freedesktop was.

It has many different uses : https://www.freedesktop.org/wiki/Software/

The effects on th epc appear to be mainly graphical with a side of netwok issues thrown in.....if this makes any sense to him.....and the install of whatever from freedesktop was in any way recent....perhaps shutting down/uninstalling freedesktop could make sense.

if he has Timeshift set up and the freedesktop was recent, perhaps a restore to a date prior to its installation could help

Using an earlier kernel may also be worth a try...

I would try the kernel first.
 
Just out of sheer curiosity, I am wondering what the intended purpose of the freedesktop was.

It has many different uses : https://www.freedesktop.org/wiki/Software/

The effects on th epc appear to be mainly graphical with a side of netwok issues thrown in.....if this makes any sense to him.....and the install of whatever from freedesktop was in any way recent....perhaps shutting down/uninstalling freedesktop could make sense.

if he has Timeshift set up and the freedesktop was recent, perhaps a restore to a date prior to its installation could help

Using an earlier kernel may also be worth a try...

I would try the kernel first.
My friend has gotta get up early in the morning.
He said thank you for the information on what he can try.

I'll be back sometime tomorrow to give you the details.
Alex
 
@Alexzee
Seems the problem is your loopback networking doesn't work as it should, but since many software requires loopback to function properly it will freeze otherwise if it can't communicate on loopback interface.

Question, do you use networking or systemd-networkd for networking?

To check which on is set on system run these commands and share status:

Bash:
sudo systemctl status networking
sudo systemctl status systemd-networkd

A preemptive solution I'd do if networking is the default is to switch to systemd-networkd.

But if systemd-networkd is already the default then check configuration, which is stored in:
Bash:
ls /etc/systemd/network
Then check each file.

See also status of the loopback NIC with ip link.

If there is firewall set up on that computer double verify loopback traffic is allowed, ex. do rule rules for loopback exist or is loopback blocked?
 
@Alexzee
Seems the problem is your loopback networking doesn't work as it should, but since many software requires loopback to function properly it will freeze otherwise if it can't communicate on loopback interface.

Question, do you use networking or systemd-networkd for networking?

To check which on is set on system run these commands and share status:

Bash:
sudo systemctl status networking
sudo systemctl status systemd-networkd

A preemptive solution I'd do if networking is the default is to switch to systemd-networkd.

But if systemd-networkd is already the default then check configuration, which is stored in:
Bash:
ls /etc/systemd/network
Then check each file.

See also status of the loopback NIC with ip link.

If there is firewall set up on that computer double verify loopback traffic is allowed, ex. do rule rules for loopback exist or is loopback blocked?
That makes sense as his wifi has been dropping out too lately he said.
I'll get that output to you soon.

For now he wants to rm the freedesktop pkg with elevated privileges.
Should that fail, then fall back to an older kernel.
 
@Alexzee
Seems the problem is your loopback networking doesn't work as it should, but since many software requires loopback to function properly it will freeze otherwise if it can't communicate on loopback interface.

Question, do you use networking or systemd-networkd for networking?

To check which on is set on system run these commands and share status:

Bash:
sudo systemctl status networking
sudo systemctl status systemd-networkd

A preemptive solution I'd do if networking is the default is to switch to systemd-networkd.

But if systemd-networkd is already the default then check configuration, which is stored in:
Bash:
ls /etc/systemd/network
Then check each file.

See also status of the loopback NIC with ip link.

If there is firewall set up on that computer double verify loopback traffic is allowed, ex. do rule rules for loopback exist or is loopback blocked?
Booting into Mint now and running those cmds so you can see the output regarding systemd-networkd.
Not sure if the firewall is set up or not. Be back in a few.
 
Here's the output from those cmds:

Code:
 sudo systemctl status systemd-networkd
[sudo] password for s:          
● systemd-networkd.service - Network Service
     Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; ve>
     Active: inactive (dead)
       Docs: man:systemd-networkd.service(8)
lines 1-4/4 (END)

$ sudo systemctl status networking
[sudo] password for s:          
● networking.service - Raise network interfaces
     Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor pr>
     Active: active (exited) since Mon 2024-09-16 12:02:47 EDT; 7min ago
       Docs: man:interfaces(5)
    Process: 554 ExecStart=/sbin/ifup -a --read-environment (code=exited, statu>
   Main PID: 554 (code=exited, status=0/SUCCESS)

Sep 16 12:02:47 sifu-MS-7845 systemd[1]: Starting Raise network interfaces...
Sep 16 12:02:47 sifu-MS-7845 systemd[1]: Finished Raise network interfaces.
lines 1-9/9 (END)

Checked on the Firewall.
There are no rules set at all.
 
@Alexzee
I'd also check if lo interface is correctly defined in:
Bash:
cat /etc/network/interfaces
After 5 minutes the LM20.2 system screen flashed and turned to a black screen. He booted into another distro on that machine to use the internet.
Be back in a little while he's booted into LMDE 6 doing things that he needs to get done.
I'll post the output of the network interfaces file when I can.
 
Last edited:
More bad news--

Now his LMDE 6 installation is going through the same performance issues and black screen as the LM 20.2 install.

The shot I took with my tablet is attatched that shows output from /etc/ network/interfaces file:
 

Attachments

  • Network Interfaces.jpg
    Network Interfaces.jpg
    902.4 KB · Views: 64

Members online


Top