LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Ubuntu
User Name
Password
Ubuntu This forum is for the discussion of Ubuntu Linux.

Notices


Reply
  Search this Thread
Old 04-28-2021, 07:55 AM   #1
Fabyo
LQ Newbie
 
Registered: Apr 2021
Posts: 8

Rep: Reputation: Disabled
Freezes on fresh install of Ubuntu mate 20.04 on Dell Vostro 3460


Ubuntu Mate used to work fine on my notebook, but maybe from after some upgrade it starts to freeze. Initially I thought it was Chrome, till it starts to freeze on Firefox too.

So, I've made a fresh install + couple of apps. Again: it freeezes, mouse pointer irresponsive but moves a little. After a lot of minutes, notebook backs to normality.

I've saved logs (just the part of today): system, kernel, dmesg, but I don't have the knowledge to find the problem. Thank you for any help.

Is there any proper way to attach the logs?

LSCPI:
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.4 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM77 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04)
01:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)
02:00.0 Ethernet controller: Qualcomm Atheros AR8161 Gigabit Ethernet (rev 10)
 
Old 04-28-2021, 09:29 AM   #2
jamison20000e
Senior Member
 
Registered: Nov 2005
Location: ...uncanny valley... infinity\1975; (randomly born:) Milwaukee, WI, US( + travel,) Earth( I wish,) END BORDER$!◣◢┌∩┐ Fe26-E,e...
Distribution: any GPL that works well on my cheapest; has been KDE or CLI but open... http://goo.gl/NqgqJx &c ;-)
Posts: 4,393
Blog Entries: 3

Rep: Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436
Hi.
Search example: Linux tests to see why laptop freezes
https://unix.stackexchange.com/quest...keeps-freezing
https://askubuntu.com/questions/2443...random-freezes
https://www.linuxquestions.org/quest...on-4175634643/
&c...

Last edited by jamison20000e; 04-28-2021 at 09:33 AM.
 
Old 04-28-2021, 10:19 AM   #3
Fabyo
LQ Newbie
 
Registered: Apr 2021
Posts: 8

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by jamison20000e View Post
Thanks Jamison,I'll take a look on these sites.
 
Old 04-28-2021, 11:05 AM   #4
onebuck
Moderator
 
Registered: Jan 2005
Location: Summer Midwest USA, Central Illinois, Winter Central Florida
Distribution: SlackwareŽ
Posts: 13,673
Blog Entries: 37

Rep: Reputation: 2862Reputation: 2862Reputation: 2862Reputation: 2862Reputation: 2862Reputation: 2862Reputation: 2862Reputation: 2862Reputation: 2862Reputation: 2862Reputation: 2862
Moderator Response

Moved: This thread is more suitable in <Ubuntu> and has been moved accordingly to help your thread/question get the exposure it deserves.
 
Old 04-28-2021, 09:13 PM   #5
jamison20000e
Senior Member
 
Registered: Nov 2005
Location: ...uncanny valley... infinity\1975; (randomly born:) Milwaukee, WI, US( + travel,) Earth( I wish,) END BORDER$!◣◢┌∩┐ Fe26-E,e...
Distribution: any GPL that works well on my cheapest; has been KDE or CLI but open... http://goo.gl/NqgqJx &c ;-)
Posts: 4,393
Blog Entries: 3

Rep: Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436Reputation: 1436
Thumbs up

If those links go nowhere I'd continue on that search example? Tho there's quite a lot of good suggestions there, maybe even some more [code]outputs[/code] you could post if no luck.
 
Old 04-28-2021, 09:23 PM   #6
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 17,397
Blog Entries: 27

Rep: Reputation: 5405Reputation: 5405Reputation: 5405Reputation: 5405Reputation: 5405Reputation: 5405Reputation: 5405Reputation: 5405Reputation: 5405Reputation: 5405Reputation: 5405
You could include relevant portions of the logs by including them in your posts within "code" tags, which become available when you click the "Go Advanced" button beneath the compose/edit post window. Also in the "Go Advanced" dialog, you have can attach files, but, given the volume of log files, it might be wise to narrow them down a bit. "Code" tags make terminal output much easier to read in a post.

This article includes a nice section on how to journalctl to sort SystemD logs by time. The relevant section is a little more than halfway down the page. I'd suggest searching for the times shortly before the freezes.

How much RAM does this machine have?

Last edited by frankbell; 04-28-2021 at 09:25 PM. Reason: clarity, more information
 
Old 05-01-2021, 05:06 PM   #7
Fabyo
LQ Newbie
 
Registered: Apr 2021
Posts: 8

Original Poster
Rep: Reputation: Disabled
Jamison, I just had another "recoverable crash". It's above my knowledge, but it seems it's related to ALSA, at timestamp 17:36:24 :
I just followed this https://askubuntu.com/questions/257940/12-04-alsa-error, but I'm not sure it'll work. Tks!

Code:
ProblemType: Crash
CurrentDesktop: MATE
Date: Sat May  1 17:50:42 2021
ExecutablePath: /usr/share/apport/recoverable_problem
ExecutableTimestamp: 1611663706
InterpreterPath: /usr/bin/python3.8
ProcCmdline: /usr/bin/python3 /usr/share/apport/recoverable_problem
ProcCwd: /home/fabyo

PythonArgs: ['/usr/share/apport/recoverable_problem']
Traceback:
Traceback (most recent call last):
  File "/usr/share/apport/recoverable_problem", line 78, in <module>
    main()
  File "/usr/share/apport/recoverable_problem", line 71, in main
    with apport.fileutils.make_report_file(report) as f:
  File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 305, in make_report_file
    raise ValueError('report has neither ExecutablePath nor Package attribute')
ValueError: report has neither ExecutablePath nor Package attribute
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_LogindSession: c2
ApportLog:
ERROR: apport (pid 6615) Sat May  1 17:50:42 2021: Unhandled exception:
Traceback (most recent call last):
  File "/usr/share/apport/apport", line 588, in <module>
    get_pid_info(pid)
  File "/usr/share/apport/apport", line 70, in get_pid_info
    proc_pid_fd = os.open('/proc/%s' % pid, os.O_RDONLY | os.O_PATH | os.O_DIRECTORY)
FileNotFoundError: [Errno 2] No such file or directory: '/proc/1295'
ERROR: apport (pid 6615) Sat May  1 17:50:42 2021: pid: 6615, uid: 0, gid: 0, euid: 0, egid: 0
ERROR: apport (pid 6615) Sat May  1 17:50:42 2021: environment: environ({'LC_CTYPE': 'C.UTF-8'})
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
** I supressed a lot of things here"
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]: snd_pcm_avail() returned a value that is exceptionally large: 2023328 bytes (10538 ms).
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]: snd_pcm_dump():
mai 01 17:36:54 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=37104 PROTO=2 
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]: Soft volume PCM
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]: Control: PCM Playback Volume
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]: min_dB: -51
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]: max_dB: 0
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]: resolution: 256
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]: Its setup is:
mai 01 17:37:54 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=37236 PROTO=2 
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   stream       : PLAYBACK
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   access       : MMAP_INTERLEAVED
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   format       : S16_LE
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   subformat    : STD
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   channels     : 2
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   rate         : 48000
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   exact rate   : 48000 (48000/1)
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   msbits       : 16
mai 01 17:38:54 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=37368 PROTO=2 
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   buffer_size  : 88200
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   period_size  : 44100
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   period_time  : 918750
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   tstamp_mode  : ENABLE
mai 01 17:40:00 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=37500 PROTO=2 
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   tstamp_type  : MONOTONIC
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   period_step  : 1
mai 01 17:40:53 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=37568 PROTO=2 
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   avail_min    : 61513
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   period_event : 0
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   start_threshold  : -1
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   stop_threshold   : 6206523236469964800
mai 01 17:41:53 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=37700 PROTO=2 
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   silence_threshold: 0
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   silence_size : 0
mai 01 17:42:56 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=37832 PROTO=2 
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   boundary     : 6206523236469964800
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]: Slave: Hardware PCM card 0 'HDA Intel PCH' device 0 subdevice 0
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]: Its setup is:
mai 01 17:43:53 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=37964 PROTO=2 
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   stream       : PLAYBACK
mai 01 17:44:53 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=38096 PROTO=2 
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   access       : MMAP_INTERLEAVED
mai 01 17:46:08 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=38196 PROTO=2 
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   format       : S16_LE
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   subformat    : STD
mai 01 17:46:59 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=38296 PROTO=2 
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   channels     : 2
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   rate         : 48000
mai 01 17:47:54 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=38428 PROTO=2 
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   exact rate   : 48000 (48000/1)
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   msbits       : 16
mai 01 17:48:57 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=38560 PROTO=2 
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   buffer_size  : 88200
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   period_size  : 44100
mai 01 17:49:56 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=38692 PROTO=2 
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   period_time  : 918750
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   tstamp_mode  : ENABLE
mai 01 17:50:41 fabyo-Vostro-3460 kernel: Xorg invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0
mai 01 17:50:41 fabyo-Vostro-3460 kernel: CPU: 1 PID: 1426 Comm: Xorg Not tainted 5.8.0-50-generic #56~20.04.1-Ubuntu
mai 01 17:50:41 fabyo-Vostro-3460 kernel: Hardware name: Dell Inc.          Vostro 3460/013M3W, BIOS A13 10/18/2012
mai 01 17:50:41 fabyo-Vostro-3460 kernel: Call Trace:
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  dump_stack+0x74/0x92
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  dump_header+0x4f/0x1eb
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  oom_kill_process.cold+0xb/0x10
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  out_of_memory.part.0+0x1df/0x430
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  out_of_memory+0x6d/0xd0
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  __alloc_pages_slowpath.constprop.0+0xd02/0xe20
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  ? get_page_from_freelist+0x68/0x370
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  __alloc_pages_nodemask+0x2bc/0x2f0
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  alloc_pages_current+0x87/0xe0
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  __page_cache_alloc+0x72/0x90
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  pagecache_get_page+0xbf/0x300
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  filemap_fault+0x6ec/0xa70
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  ? clockevents_program_event+0x8f/0xe0
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  ? hrtimer_start_range_ns+0x1aa/0x310
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  ? xas_load+0x9/0x80
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  ? xas_find+0x183/0x1b0
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  ? filemap_map_pages+0x1d5/0x3b0
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  ext4_filemap_fault+0x32/0x50
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  __do_fault+0x3c/0xe0
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  do_fault+0x256/0x520
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  __handle_mm_fault+0x547/0x930
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  handle_mm_fault+0xca/0x200
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  do_user_addr_fault+0x1e2/0x440
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  exc_page_fault+0x86/0x1b0
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  ? asm_exc_page_fault+0x8/0x30
mai 01 17:50:41 fabyo-Vostro-3460 kernel:  asm_exc_page_fault+0x1e/0x30
mai 01 17:50:41 fabyo-Vostro-3460 kernel: RIP: 0033:0x56532fb72f90
mai 01 17:50:41 fabyo-Vostro-3460 kernel: Code: Unable to access opcode bytes at RIP 0x56532fb72f66.
mai 01 17:50:41 fabyo-Vostro-3460 kernel: RSP: 002b:00007ffc450687f8 EFLAGS: 00010202
mai 01 17:50:41 fabyo-Vostro-3460 kernel: RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000
mai 01 17:50:41 fabyo-Vostro-3460 kernel: RDX: 00007ffc45068800 RSI: 00007ffc45068930 RDI: 000000000000000e
mai 01 17:50:41 fabyo-Vostro-3460 kernel: RBP: 000056532fc1e830 R08: 0000000000000000 R09: 0000000000000000
mai 01 17:50:41 fabyo-Vostro-3460 kernel: R10: 00000000000000ff R11: 0000000000000005 R12: 000056532fc0a544
mai 01 17:50:41 fabyo-Vostro-3460 kernel: R13: 000000000009699c R14: 00007fe9b445f6c0 R15: 00007ffc45068db4
mai 01 17:50:41 fabyo-Vostro-3460 kernel: Mem-Info:
mai 01 17:50:41 fabyo-Vostro-3460 kernel: active_anon:1199245 inactive_anon:193188 isolated_anon:0
                                           active_file:100 inactive_file:63 isolated_file:0
                                           unevictable:1358 dirty:0 writeback:0
                                           slab_reclaimable:13200 slab_unreclaimable:29541
                                           mapped:2739 shmem:22174 pagetables:8093 bounce:0
                                           free:23174 free_pcp:1812 free_cma:0
mai 01 17:50:41 fabyo-Vostro-3460 kernel: Node 0 active_anon:4796980kB inactive_anon:772752kB active_file:400kB inactive_file:252kB unevictable:5432kB isolated(anon):0kB isolated(file):0kB mapped:10956kB dirty:0kB writeback:0kB shmem:88696kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB all_unreclaimable? no
mai 01 17:50:41 fabyo-Vostro-3460 kernel: Node 0 DMA free:14336kB min:176kB low:220kB high:264kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15984kB managed:15360kB mlocked:0kB kernel_stack:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
mai 01 17:50:41 fabyo-Vostro-3460 kernel: lowmem_reserve[]: 0 2775 5694 5694 5694
mai 01 17:50:41 fabyo-Vostro-3460 kernel: Node 0 DMA32 free:44184kB min:32848kB low:41060kB high:49272kB reserved_highatomic:0KB active_anon:2525776kB inactive_anon:336436kB active_file:540kB inactive_file:372kB unevictable:0kB writepending:0kB present:2990916kB managed:2925380kB mlocked:0kB kernel_stack:500kB pagetables:7216kB bounce:0kB free_pcp:4068kB local_pcp:1108kB free_cma:0kB
mai 01 17:50:41 fabyo-Vostro-3460 kernel: lowmem_reserve[]: 0 0 2919 2919 2919
mai 01 17:50:41 fabyo-Vostro-3460 kernel: Node 0 Normal free:34176kB min:34556kB low:43192kB high:51828kB reserved_highatomic:2048KB active_anon:2271204kB inactive_anon:436316kB active_file:40kB inactive_file:448kB unevictable:5432kB writepending:0kB present:3135488kB managed:2997132kB mlocked:48kB kernel_stack:11964kB pagetables:25156kB bounce:0kB free_pcp:3180kB local_pcp:836kB free_cma:0kB
mai 01 17:50:41 fabyo-Vostro-3460 kernel: lowmem_reserve[]: 0 0 0 0 0
mai 01 17:50:41 fabyo-Vostro-3460 kernel: Node 0 DMA: 0*4kB 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 1*2048kB (M) 3*4096kB (M) = 14336kB
mai 01 17:50:41 fabyo-Vostro-3460 kernel: Node 0 DMA32: 98*4kB (UME) 213*8kB (UME) 193*16kB (UME) 110*32kB (UME) 26*64kB (UME) 23*128kB (UME) 30*256kB (UE) 11*512kB (ME) 3*1024kB (UE) 7*2048kB (UME) 0*4096kB = 44032kB
mai 01 17:50:41 fabyo-Vostro-3460 kernel: Node 0 Normal: 1466*4kB (UMEH) 1235*8kB (UME) 592*16kB (UMEH) 259*32kB (UMEH) 18*64kB (UM) 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 34656kB
mai 01 17:50:41 fabyo-Vostro-3460 kernel: 22583 total pagecache pages
mai 01 17:50:41 fabyo-Vostro-3460 kernel: 133 pages in swap cache
mai 01 17:50:41 fabyo-Vostro-3460 kernel: Swap cache stats: add 693026, delete 692890, find 31789/88477
mai 01 17:50:41 fabyo-Vostro-3460 kernel: Free swap  = 0kB
mai 01 17:50:41 fabyo-Vostro-3460 kernel: Total swap = 2097148kB
mai 01 17:50:41 fabyo-Vostro-3460 kernel: 1535597 pages RAM
mai 01 17:50:41 fabyo-Vostro-3460 kernel: 0 pages HighMem/MovableOnly
mai 01 17:50:41 fabyo-Vostro-3460 kernel: 51129 pages reserved
mai 01 17:50:41 fabyo-Vostro-3460 kernel: 0 pages hwpoisoned
mai 01 17:50:41 fabyo-Vostro-3460 kernel: Out of memory: Killed process 2270 (indicator-datet) total-vm:8187620kB, anon-rss:4879688kB, file-rss:0kB, shmem-rss:0kB, UID:1000 pgtables:12712kB oom_score_adj:0
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   tstamp_type  : MONOTONIC
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   period_step  : 1
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   avail_min    : 61513
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   period_event : 0
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   start_threshold  : -1
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   stop_threshold   : 6206523236469964800
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   silence_threshold: 0
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   silence_size : 0
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   boundary     : 6206523236469964800
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   appl_ptr     : 24231584
mai 01 17:36:24 fabyo-Vostro-3460 pulseaudio[1893]:   hw_ptr       : 24649216
mai 01 17:36:38 fabyo-Vostro-3460 pulseaudio[1893]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
mai 01 17:36:38 fabyo-Vostro-3460 pulseaudio[1893]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
mai 01 17:36:38 fabyo-Vostro-3460 pulseaudio[1893]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
mai 01 17:36:57 fabyo-Vostro-3460 systemd[1]: snapd.service: Watchdog timeout (limit 5min)!
mai 01 17:38:12 fabyo-Vostro-3460 geoclue[2410]: Failed to query location: Error resolving : Temporary failure in name resolution
mai 01 17:39:50 fabyo-Vostro-3460 geoclue[2410]: Failed to query location: Error resolving : Temporary failure in name resolution
mai 01 17:39:54 fabyo-Vostro-3460 systemd[1]: snapd.service: State 'stop-watchdog' timed out. Terminating.
mai 01 17:40:25 fabyo-Vostro-3460 geoclue[2410]: Failed to query location: Error resolving : Temporary failure in name resolution
mai 01 17:40:31 fabyo-Vostro-3460 pulseaudio[1893]: snd_pcm_delay() returned a value that is exceptionally large: -3983680 bytes (-20748 ms).
mai 01 17:40:31 fabyo-Vostro-3460 pulseaudio[1893]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
mai 01 17:40:33 fabyo-Vostro-3460 pulseaudio[1893]: snd_pcm_dump():
mai 01 17:40:33 fabyo-Vostro-3460 pulseaudio[1893]: Soft volume PCM
mai 01 17:40:33 fabyo-Vostro-3460 pulseaudio[1893]: Control: PCM Playback Volume
mai 01 17:40:34 fabyo-Vostro-3460 pulseaudio[1893]: min_dB: -51
mai 01 17:40:35 fabyo-Vostro-3460 pulseaudio[1893]: max_dB: 0
mai 01 17:40:36 fabyo-Vostro-3460 pulseaudio[1893]: resolution: 256
mai 01 17:40:36 fabyo-Vostro-3460 pulseaudio[1893]: Its setup is:
mai 01 17:40:37 fabyo-Vostro-3460 pulseaudio[1893]:   stream       : PLAYBACK
mai 01 17:40:37 fabyo-Vostro-3460 pulseaudio[1893]:   access       : MMAP_INTERLEAVED
mai 01 17:40:38 fabyo-Vostro-3460 pulseaudio[1893]:   format       : S16_LE
mai 01 17:40:38 fabyo-Vostro-3460 pulseaudio[1893]:   subformat    : STD
mai 01 17:40:39 fabyo-Vostro-3460 pulseaudio[1893]:   channels     : 2
mai 01 17:40:40 fabyo-Vostro-3460 pulseaudio[1893]:   rate         : 48000
mai 01 17:40:40 fabyo-Vostro-3460 pulseaudio[1893]:   exact rate   : 48000 (48000/1)
mai 01 17:40:41 fabyo-Vostro-3460 pulseaudio[1893]:   msbits       : 16
mai 01 17:40:41 fabyo-Vostro-3460 pulseaudio[1893]:   buffer_size  : 88200
mai 01 17:40:42 fabyo-Vostro-3460 pulseaudio[1893]:   period_size  : 44100
mai 01 17:40:42 fabyo-Vostro-3460 pulseaudio[1893]:   period_time  : 918750
mai 01 17:40:43 fabyo-Vostro-3460 pulseaudio[1893]:   tstamp_mode  : ENABLE
mai 01 17:40:45 fabyo-Vostro-3460 pulseaudio[1893]:   tstamp_type  : MONOTONIC
mai 01 17:40:46 fabyo-Vostro-3460 pulseaudio[1893]:   period_step  : 1
mai 01 17:40:47 fabyo-Vostro-3460 pulseaudio[1893]:   avail_min    : 45673
mai 01 17:40:48 fabyo-Vostro-3460 pulseaudio[1893]:   period_event : 0
mai 01 17:40:48 fabyo-Vostro-3460 pulseaudio[1893]:   start_threshold  : -1
mai 01 17:40:49 fabyo-Vostro-3460 pulseaudio[1893]:   stop_threshold   : 6206523236469964800
mai 01 17:40:50 fabyo-Vostro-3460 pulseaudio[1893]:   silence_threshold: 0
mai 01 17:40:51 fabyo-Vostro-3460 pulseaudio[1893]:   silence_size : 0
mai 01 17:40:52 fabyo-Vostro-3460 pulseaudio[1893]:   boundary     : 6206523236469964800
mai 01 17:40:53 fabyo-Vostro-3460 pulseaudio[1893]: Slave: Hardware PCM card 0 'HDA Intel PCH' device 0 subdevice 0
mai 01 17:40:53 fabyo-Vostro-3460 pulseaudio[1893]: Its setup is:
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   stream       : PLAYBACK
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   access       : MMAP_INTERLEAVED
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   format       : S16_LE
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   subformat    : STD
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   channels     : 2
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   rate         : 48000
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   exact rate   : 48000 (48000/1)
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   msbits       : 16
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   buffer_size  : 88200
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   period_size  : 44100
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   period_time  : 918750
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   tstamp_mode  : ENABLE
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   tstamp_type  : MONOTONIC
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   period_step  : 1
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   avail_min    : 45673
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   period_event : 0
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   start_threshold  : -1
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   stop_threshold   : 6206523236469964800
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   silence_threshold: 0
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   silence_size : 0
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   boundary     : 6206523236469964800
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   appl_ptr     : 35458856
mai 01 17:40:54 fabyo-Vostro-3460 pulseaudio[1893]:   hw_ptr       : 36454776
mai 01 17:41:25 fabyo-Vostro-3460 systemd[1]: snapd.service: State 'stop-sigterm' timed out. Killing.
mai 01 17:41:39 fabyo-Vostro-3460 systemd[1]: snapd.service: Main process exited, code=killed, status=9/KILL
mai 01 17:41:39 fabyo-Vostro-3460 systemd[1]: snapd.service: Failed with result 'watchdog'.
mai 01 17:43:50 fabyo-Vostro-3460 geoclue[2410]: Failed to query location: Error resolving : Temporary failure in name resolution
mai 01 17:44:58 fabyo-Vostro-3460 lightdm[1384]: Error updating user /org/freedesktop/Accounts/User1000: Timeout was reached
mai 01 17:45:05 fabyo-Vostro-3460 geoclue[2410]: Scanning of WiFi networks failed: Timeout was reached
mai 01 17:45:25 fabyo-Vostro-3460 lightdm[1384]: Error updating user /org/freedesktop/Accounts/User1000: Timeout was reached
mai 01 17:46:30 fabyo-Vostro-3460 geoclue[2410]: Failed to query location: Error resolving : Temporary failure in name resolution
mai 01 17:46:32 fabyo-Vostro-3460 systemd[1]: snapd.service: start operation timed out. Terminating.
mai 01 17:47:01 fabyo-Vostro-3460 systemd[1]: snapd.service: Failed with result 'timeout'.
mai 01 17:47:02 fabyo-Vostro-3460 geoclue[2410]: Failed to query location: Error resolving : Temporary failure in name resolution
mai 01 17:47:04 fabyo-Vostro-3460 systemd[1]: Failed to start Snap Daemon.
mai 01 17:47:59 fabyo-Vostro-3460 geoclue[2410]: Failed to query location: Error resolving : Temporary failure in name resolution
mai 01 17:49:58 fabyo-Vostro-3460 geoclue[2410]: Failed to query location: Error resolving : Temporary failure in name resolution
mai 01 17:50:51 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=38824 PROTO=2 
mai 01 17:51:51 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=38892 PROTO=2 
mai 01 17:52:51 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=39024 PROTO=2 
mai 01 17:53:51 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=39156 PROTO=2 
mai 01 17:54:51 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=39288 PROTO=2 
mai 01 17:55:51 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=39420 PROTO=2 
mai 01 17:56:51 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=39520 PROTO=2 
mai 01 17:57:51 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=39620 PROTO=2 
mai 01 17:58:50 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=39752 PROTO=2 
mai 01 17:59:50 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=39884 PROTO=2 
mai 01 18:00:50 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=40016 PROTO=2 
mai 01 18:01:50 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=40148 PROTO=2 
mai 01 18:02:50 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=40216 PROTO=2 
mai 01 18:03:50 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=40348 PROTO=2 
mai 01 18:04:50 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=40480 PROTO=2 
mai 01 18:05:50 fabyo-Vostro-3460 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=e0:06:e6:dd:26:95:18:0f:76:91:3e:de:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=40612 PROTO=2
Package: apport 2.20.11-0ubuntu27.16
PackageArchitecture: all
ProcCpuinfoMinimal:
processor	: 3
vendor_id	: GenuineIntel
cpu family	: 6
model		: 42
model name	: Intel(R) Core(TM) i3-2370M CPU @ 2.40GHz
stepping	: 7
microcode	: 0x2f
cpu MHz		: 2394.559
cache size	: 3072 KB
physical id	: 0
siblings	: 4
core id		: 1
cpu cores	: 2
apicid		: 3
initial apicid	: 3
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx lahf_lm epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid xsaveopt dtherm arat pln pts md_clear flush_l1d
vmx flags	: vnmi preemption_timer invvpid ept_x_only flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest
bugs		: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit
bogomips	: 4789.12
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
SourcePackage: apport
Tags:  focal
Title: recoverable_problem crashed with ValueError in make_report_file(): report has neither ExecutablePath nor Package attribute
Uname: Linux 5.8.0-50-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
_MarkForUpload: True
 
Old 05-01-2021, 05:08 PM   #8
Fabyo
LQ Newbie
 
Registered: Apr 2021
Posts: 8

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by frankbell View Post
You could include relevant portions of the logs by including them in your posts within "code" tags, which become available when you click the "Go Advanced" button beneath the compose/edit post window. Also in the "Go Advanced" dialog, you have can attach files, but, given the volume of log files, it might be wise to narrow them down a bit. "Code" tags make terminal output much easier to read in a post.

This article includes a nice section on how to journalctl to sort SystemD logs by time. The relevant section is a little more than halfway down the page. I'd suggest searching for the times shortly before the freezes.

How much RAM does this machine have?
Thanks Frankbell the article helped me. I had no previous knowledge about using journalctl. My machine is 6Gb ram.
 
Old 05-01-2021, 05:28 PM   #9
Fabyo
LQ Newbie
 
Registered: Apr 2021
Posts: 8

Original Poster
Rep: Reputation: Disabled
Not solved yet: just had another recoverable crash. Any help will be appreciated.
 
Old 05-01-2021, 06:18 PM   #10
!!!
Member
 
Registered: Jan 2017
Location: Fremont, CA, USA
Distribution: Trying any&ALL on old/minimal
Posts: 748

Rep: Reputation: 323Reputation: 323Reputation: 323Reputation: 323
sysreq+t? (Or ...)
I would send the output of top to a file every minute and (maybe reboot after a minute, to) capture the file when it hangs.
My thought here is to: see what's running (consuming resources) when it's hung.

I've seen lots of cases where a web browser temporarily freezes the system (for minutes) because it's eating up all the CPU and/or memory (especially on one of my underpowered old netbooks).

"Xorg invoked oom-killer" is interesting...
Does anything running disappear when it recovers from the freeze?

Last edited by !!!; 05-01-2021 at 06:35 PM.
 
Old 05-01-2021, 06:37 PM   #11
Fabyo
LQ Newbie
 
Registered: Apr 2021
Posts: 8

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by !!! View Post
sysreq+t? (Or ...)
I would send the output of top to a file every minute and (maybe reboot after a minute, to) capture the file when it hangs.
My thought here is to: see what's running (consuming resources) when it's hung.

I've seen lots of cases where a web browser temporarily freezes the system (for minutes) because it's eating up all the CPU and/or memory (especially on one of my underpowered old netbooks).
I see, but it uses to work fine all past year. Problem started now on April. I've tested all chromIum based browsers, Firefox and others...

I don't have a clue on how to do this file output monitoring you mentioned. I'll search about how to do it, it seems a good idea. Tks.
 
Old 05-01-2021, 06:45 PM   #12
Fabyo
LQ Newbie
 
Registered: Apr 2021
Posts: 8

Original Poster
Rep: Reputation: Disabled
Maybe I should downgrade Ubuntu to 19.04...
 
Old 05-01-2021, 06:59 PM   #13
!!!
Member
 
Registered: Jan 2017
Location: Fremont, CA, USA
Distribution: Trying any&ALL on old/minimal
Posts: 748

Rep: Reputation: 323Reputation: 323Reputation: 323Reputation: 323
I wouldn't try to revert.
Edit: but since you just did a reinstall (vs 'downgrade'), you could easily reinstall 19.04
* as a temporary experiment, to collect another data point, BUT Ubuntu 19.04 has reached the end of life on 23rd January 2020

Here's a good thing I found, from this websearch:
Linux hang|freeze mouse|pointer slow|sluggish
https://www.fosslinux.com/39434/5-th...ui-freezes.htm
And from: Ubuntu mate 20.04 freezes for intitle:"minutes"
https://unix.stackexchange.com/quest...rtain-websites
(looks really good!!!)

Sorry I was still editing-in another question while you replied.
Could you watch top in another window while it freezes? Can you force it to freeze, maybe with a certain web page?
Did this only happen after the upgrade?
More specific details are always useful:
Does the mouse stay almost but not quite totally
Frozen the whole time, until it recovers?

(Other LQ'ers are definitely welcome to jump in:
I'm not familiar with all those errors and crash log in systemd.)

Do the time stamps correlate exactly with the hang, and similar messages always happen?

Last edited by !!!; 05-01-2021 at 07:39 PM.
 
Old 05-04-2021, 08:04 AM   #14
Fabyo
LQ Newbie
 
Registered: Apr 2021
Posts: 8

Original Poster
Rep: Reputation: Disabled
Well, after spending some time trying to analyze the journals, trying some changes and still having freezes, I just gave up Ubuntu Mate and installed linux Pop!_OS.

Since then there are no freezes anymore.

I which I had the knowledge to fix my Ubuntu Mate installation, but I'm not an advanced user or technician, so I just hope it works for long time now.

Thank for all your help you generously provide!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Ubuntu MATE 15.04 Arrives With MATE Desktop 1.8.2 and MATE Tweak LXer Syndicated Linux News 0 05-15-2015 09:30 AM
Install the modem on a Dell Vostro 1500 and Ubuntu 9.04 gonvaro Linux - Newbie 4 01-23-2011 08:33 AM
Big problem with Ubuntu 10.10 on Dell Vostro v13 tdnguyenitvn Linux - Laptop and Netbook 6 10-19-2010 11:50 PM
Ubuntu on Dell Vostro nbhat Ubuntu 8 11-29-2009 01:57 AM
Ubuntu Hardy on Dell Vostro 1520 Snigger Linux - Laptop and Netbook 5 07-17-2009 07:24 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Ubuntu

All times are GMT -5. The time now is 01:38 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration