Regarding the inexplicable automatic restart problem

ling · 28 September 2023 01:23

My laptop occasionally reboots or freezes inexplicably. I suspect it may be due to an issue with the Nvidia driver. I use an external monitor and manage the switching between the discrete and integrated graphics using Optimus Manager (because my external monitor is directly connected to the discrete GPU). However, yesterday, I disabled the PCI reset feature in Optimus Manager, and I was able to use my laptop without any issues throughout the day. So now I’m not sure what the exact problem is. I tried checking the boot logs using “journalctl -rb” and “journalctl -rb -1,” but there is no information about any errors. I also checked the logs using “sudo dmesg -T,” and I found an “Out of memory” error. Could this be causing the reboots?

The following is the result of “journalctl -rb -1”

9月 28 01:01:02 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 01:01:02 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 01:01:01 ling-20ym anacron[12128]: Anacron started on 2023-09-28
9月 28 01:01:01 ling-20ym CROND[12119]: (root) CMD (run-parts /etc/cron.hourly)
9月 28 01:00:58 ling-20ym plasmashell[3412]: 01f4:fixme:winsock:setsockopt Ignoring SO_RANDOMIZE_PORT
9月 28 01:00:55 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 01:00:55 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 01:00:48 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 01:00:48 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 01:00:41 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 01:00:41 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 01:00:34 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 01:00:34 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 01:00:27 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 01:00:27 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 01:00:20 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 01:00:20 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 01:00:13 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 01:00:13 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 01:00:06 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 01:00:06 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 01:00:01 ling-20ym CROND[12042]: (root) CMDEND (timeshift --check --scripted)
9月 28 01:00:01 ling-20ym systemd[1]: run-timeshift-12043-backup.mount: Deactivated successfully.
9月 28 01:00:01 ling-20ym crontab[12073]: (root) LIST (root)
9月 28 01:00:01 ling-20ym crontab[12072]: (root) LIST (root)
9月 28 01:00:01 ling-20ym CROND[12042]: (root) CMDOUT (------------------------------------------------------------------------------)
9月 28 01:00:01 ling-20ym CROND[12042]: (root) CMDOUT (Last daily snapshot is 9 hours old)
9月 28 01:00:01 ling-20ym CROND[12042]: (root) CMDOUT (Daily snapshots are enabled)
9月 28 01:00:01 ling-20ym CROND[12042]: (root) CMDOUT (Mounted '/dev/nvme1n1p6' at '/run/timeshift/12043/backup')
9月 28 01:00:01 ling-20ym CROND[12043]: (root) CMD (timeshift --check --scripted)
9月 28 00:59:59 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 00:59:59 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 00:59:52 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 00:59:52 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 00:59:45 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 00:59:45 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 00:59:38 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 00:59:38 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 00:59:31 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 00:59:31 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 00:59:24 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 00:59:24 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 00:59:17 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 00:59:17 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 00:59:10 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 00:59:10 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 00:59:03 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class
9月 28 00:59:03 ling-20ym plasmashell[3412]: 02f4:fixme:virtual:NtQueryVirtualMemory (0xffffffff,(nil),info_class=1,0x19758d60,16392,(nil)) Unknown information class

and then the laptop reboot.
The following is the result of " sudo dmesg -T"

[四 9月 28 01:07:08 2023] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/system.slice/v2raya.service,task=v2ray,pid=940,uid=0
[四 9月 28 01:07:08 2023] Out of memory: Killed process 940 (v2ray) total-vm:60046432kB, anon-rss:18645572kB, file-rss:164kB, shmem-rss:0kB, UID:0 pgtables:86028kB oom_score_adj:0
[四 9月 28 01:07:18 2023] oom_reaper: reaped process 940 (v2ray), now anon-rss:976kB, file-rss:164kB, shmem-rss:0kB
[四 9月 28 01:13:03 2023] v2ray invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0
[四 9月 28 01:13:03 2023] CPU: 14 PID: 1963 Comm: v2ray Tainted: P           OE      6.5.3-1-MANJARO #1 6391e71545040710026529a97e4fbb6ca4044529
[四 9月 28 01:13:03 2023] Hardware name: LENOVO 20YM/LNVNB161216, BIOS GXCN43WW 06/15/2022
[四 9月 28 01:13:03 2023] Call Trace:
[四 9月 28 01:13:03 2023]  <TASK>
[四 9月 28 01:13:03 2023]  dump_stack_lvl+0x47/0x60
[四 9月 28 01:13:03 2023]  dump_header+0x4a/0x240
[四 9月 28 01:13:03 2023]  oom_kill_process+0xf9/0x190
[四 9月 28 01:13:03 2023]  out_of_memory+0x246/0x590
[四 9月 28 01:13:03 2023]  __alloc_pages_slowpath.constprop.0+0xa5f/0xd90
[四 9月 28 01:13:03 2023]  __alloc_pages+0x32d/0x350
[四 9月 28 01:13:03 2023]  __folio_alloc+0x1b/0x50
[四 9月 28 01:13:03 2023]  vma_alloc_folio+0xa0/0x380
[四 9月 28 01:13:03 2023]  ? srso_alias_return_thunk+0x5/0x7f
[四 9月 28 01:13:03 2023]  __read_swap_cache_async+0x143/0x2b0
[四 9月 28 01:13:03 2023]  swapin_readahead+0x374/0x4c0
[四 9月 28 01:13:03 2023]  do_swap_page+0x1ad/0xbb0
[四 9月 28 01:13:03 2023]  __handle_mm_fault+0x78d/0xbb0
[四 9月 28 01:13:03 2023]  handle_mm_fault+0x155/0x350
[四 9月 28 01:13:03 2023]  do_user_addr_fault+0x203/0x640
[四 9月 28 01:13:03 2023]  exc_page_fault+0x7f/0x180
[四 9月 28 01:13:03 2023]  asm_exc_page_fault+0x26/0x30
[四 9月 28 01:13:03 2023] RIP: 0033:0x55f6dc2eaaab
[四 9月 28 01:13:03 2023] Code: Unable to access opcode bytes at 0x55f6dc2eaa81.
[四 9月 28 01:13:03 2023] RSP: 002b:00007f4a3fffed10 EFLAGS: 00010202
[四 9月 28 01:13:03 2023] RAX: 000000c3a13df2f0 RBX: 0000000000000010 RCX: 0000000000000000
[四 9月 28 01:13:03 2023] RDX: 000000c3a13df2f0 RSI: 0000000000000010 RDI: 0000000000000002
[四 9月 28 01:13:03 2023] RBP: 00007f4a3fffed90 R08: 0000000000000008 R09: 000000c3a13df2f8
[四 9月 28 01:13:03 2023] R10: 0000000000000002 R11: 0000000000000057 R12: 00007f4a3fffed90
[四 9月 28 01:13:03 2023] R13: 0000000000000000 R14: 000000c0012181a0 R15: 000000c81d42e000
[四 9月 28 01:13:03 2023]  </TASK>
[四 9月 28 01:13:03 2023] Mem-Info:
[四 9月 28 01:13:03 2023] active_anon:2551688 inactive_anon:2170521 isolated_anon:0
                             active_file:0 inactive_file:848 isolated_file:0
                             unevictable:0 dirty:1 writeback:0
                             slab_reclaimable:15688 slab_unreclaimable:156810
                             mapped:2554 shmem:5 pagetables:22552
                             sec_pagetables:0 bounce:0
                             kernel_misc_reclaimable:0
                             free:42737 free_pcp:692 free_cma:0
[四 9月 28 01:13:03 2023] Node 0 active_anon:10206752kB inactive_anon:8682084kB active_file:0kB inactive_file:3028kB unevictable:0kB isolated(anon):0kB isolated(file):0kB mapped:10216kB dirty:4kB writeback:0kB shmem:20kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 15282176kB writeback_tmp:0kB kernel_stack:14016kB pagetables:90208kB sec_pagetables:0kB all_unreclaimable? no
[四 9月 28 01:13:03 2023] Node 0 DMA free:11264kB boost:0kB min:40kB low:52kB high:64kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15992kB managed:15360kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
[四 9月 28 01:13:03 2023] lowmem_reserve[]: 0 3123 23355 23355 23355
[四 9月 28 01:13:03 2023] Node 0 DMA32 free:90084kB boost:0kB min:9032kB low:12228kB high:15424kB reserved_highatomic:0KB active_anon:2470456kB inactive_anon:293512kB active_file:0kB inactive_file:320kB unevictable:0kB writepending:0kB present:3280768kB managed:3214248kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
[四 9月 28 01:13:03 2023] lowmem_reserve[]: 0 0 20232 20232 20232
[四 9月 28 01:13:03 2023] Node 0 Normal free:69600kB boost:6144kB min:64648kB low:85364kB high:106080kB reserved_highatomic:2048KB active_anon:7736088kB inactive_anon:8388668kB active_file:0kB inactive_file:2544kB unevictable:0kB writepending:4kB present:21203968kB managed:20724336kB mlocked:0kB bounce:0kB free_pcp:2768kB local_pcp:528kB free_cma:0kB
[四 9月 28 01:13:03 2023] lowmem_reserve[]: 0 0 0 0 0
[四 9月 28 01:13:03 2023] Node 0 DMA: 0*4kB 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 1*1024kB (U) 1*2048kB (M) 2*4096kB (M) = 11264kB
[四 9月 28 01:13:03 2023] Node 0 DMA32: 273*4kB (UME) 123*8kB (UME) 63*16kB (UME) 24*32kB (UME) 8*64kB (UME) 109*128kB (UME) 65*256kB (UME) 39*512kB (M) 35*1024kB (ME) 0*2048kB 0*4096kB = 90764kB
[四 9月 28 01:13:03 2023] Node 0 Normal: 1076*4kB (UME) 189*8kB (UME) 215*16kB (UME) 52*32kB (UME) 13*64kB (UME) 4*128kB (ME) 4*256kB (ME) 3*512kB (UM) 51*1024kB (M) 0*2048kB 0*4096kB = 67048kB
[四 9月 28 01:13:03 2023] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB
[四 9月 28 01:13:03 2023] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
[四 9月 28 01:13:03 2023] 4284 total pagecache pages
[四 9月 28 01:13:03 2023] 3403 pages in swap cache
[四 9月 28 01:13:03 2023] Free swap  = 8kB
[四 9月 28 01:13:03 2023] Total swap = 24000508kB
[四 9月 28 01:13:03 2023] 6125182 pages RAM
[四 9月 28 01:13:03 2023] 0 pages HighMem/MovableOnly
[四 9月 28 01:13:03 2023] 136696 pages reserved
[四 9月 28 01:13:03 2023] 0 pages cma reserved
[四 9月 28 01:13:03 2023] 0 pages hwpoisoned
[四 9月 28 01:13:03 2023] Tasks state (memory values in pages):
[四 9月 28 01:13:03 2023] [  pid  ]   uid  tgid total_vm      rss pgtables_bytes swapents oom_score_adj name
[四 9月 28 01:13:03 2023] [    344]     0   344     8497      256    81920      352          -250 systemd-journal
[四 9月 28 01:13:03 2023] [    345]     0   345     8991      209    90112      768         -1000 systemd-udevd
[四 9月 28 01:13:03 2023] [    680]     0   680     3146      242    69632      160             0 bluetoothd
[四 9月 28 01:13:03 2023] [    681]     0   681     2545      316    53248       96             0 crond
[四 9月 28 01:13:03 2023] [    682]    81   682     2443      288    57344      192          -900 dbus-daemon
[四 9月 28 01:13:03 2023] [    684]   102   684    77167      247    94208      736             0 polkitd
[四 9月 28 01:13:03 2023] [    685]     0   685     4524      192    73728      256             0 systemd-logind
[四 9月 28 01:13:03 2023] [    718]     0   718    86008      279   167936     1248             0 NetworkManager
[四 9月 28 01:13:03 2023] [    739]     0   739    97824      280   131072     1024             0 ModemManager
[四 9月 28 01:13:03 2023] [    771]     0   771     4653      214    81920      416             0 wpa_supplicant
[四 9月 28 01:13:03 2023] [    782]     0   782     7754      320    98304      416             0 cupsd
[四 9月 28 01:13:03 2023] [    797]     0   797     2716      397    69632      192             0 EasyMonitor
[四 9月 28 01:13:03 2023] [    804]     0   804    64850      288   176128      640             0 ECAgent
[四 9月 28 01:13:03 2023] [    810]   209   810     4223      251    73728      192             0 dbus
[四 9月 28 01:13:03 2023] [    869]     0   869     5732      241    81920     1696             0 python3
[四 9月 28 01:13:03 2023] [    870]     0   870    39029      345   172032      992             0 sddm
[四 9月 28 01:13:03 2023] [    872]     0   872  6517394     3982   618496    12288             0 Xorg
[四 9月 28 01:13:03 2023] [    882]     0   882   252891      696   294912     5216             0 ToDesk_Service
[四 9月 28 01:13:03 2023] [   1028]     0  1028    19697      309   151552      448             0 sddm-helper
[四 9月 28 01:13:03 2023] [   1032]   963  1032     5268      247    77824      544           100 systemd
[四 9月 28 01:13:03 2023] [   1033]   963  1033     6480      241    77824      928           100 (sd-pam)
[四 9月 28 01:13:03 2023] [   1044]   963  1044   349012     1119   847872    12704             0 sddm-greeter
[四 9月 28 01:13:03 2023] [   1047]   963  1047     2233      264    57344       96           200 dbus-daemon
[四 9月 28 01:13:03 2023] [   1818]     0  1818   612690     3712   348160     5184             0 v2raya
[四 9月 28 01:13:03 2023] [   1850]     0  1850 15063350  4712360 88526848  5951296             0 v2ray
[四 9月 28 01:13:03 2023] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/system.slice/v2raya.service,task=v2ray,pid=1850,uid=0
[四 9月 28 01:13:03 2023] Out of memory: Killed process 1850 (v2ray) total-vm:60253400kB, anon-rss:18848804kB, file-rss:636kB, shmem-rss:0kB, UID:0 pgtables:86452kB oom_score_adj:0
[四 9月 28 01:13:13 2023] oom_reaper: reaped process 1850 (v2ray), now anon-rss:728kB, file-rss:636kB, shmem-rss:0kB
[四 9月 28 08:11:39 2023] systemd-journald[344]: File /var/log/journal/f993508270894493b75f29fdf5676bad/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.

soundofthunder · 28 September 2023 03:13

It seems you have already identified the reset feature as triggering your issue.

I suggest that optimus-manager (AUR) and/or optimus-manager (Github) might be worth visiting for known bugs and possible workarounds. There are also other builds such as optimus-manager-plasma (qt) that you could consider as an alternative.

ling · 28 September 2023 03:14

Is there any other way to view the logs from the previous crash? Right now, I’m not sure what’s causing these random freezes. The keyboard and mouse become unresponsive, and the whole system suddenly freezes. Checking the boot logs didn’t show any error messages either.

ling · 28 September 2023 03:17

I just experienced another unexplained system freeze. I couldn’t do anything, but Optimus Manager has already removed the PCI reset feature, and yet it still froze.

soundofthunder · 28 September 2023 03:41

These guides: HowTo Find error logs and Checking for errors by reading logs or shell output should be useful.

As already suggested, optimus-manager-plasma may be worth trying instead of optimus-manager, considering you’re apparently using KDE Plasma. Try that and see if it makes a difference – if not, then the issue is something else; likely graphics-related. You can also try removing any plasmoids/widgets/extensions you have loaded. Cheers.

ling · 28 September 2023 04:20

Thank you very much for your assistance！ I will carefully read the steps on how to identify the error. I have just installed “optimus-manager-plasma,” but running it has no response, and there are no relevant error outputs from the commands.

megavolt · 28 September 2023 06:28

Well… that simply explains it. No RAM left → process killed. Most liklely you have no swap partition/file configured.

ling · 28 September 2023 06:45

I have configured a 24g swap partition. Here are some commands. It should be a bug in v2ray that causes high memory usage. I just want to ask if the restart problem is caused by too high memory.

megavolt · 28 September 2023 07:06

Usually not. No memory can lead to a less responsive system and in case of oom-kill: The application which tries to allocate memory, but couldn’t, will be killed.

What do you exactly mean by a reboot? Does it crash completely and then you see the boot logo? That would be more a hardware related problem: UEFI, firmware, driver, phyiscal hardware.

In case of memory: It could be a faulty RAM-Module, which cannot be corrected anymore on access. Usually Linux can correct it by software if not ECC, but only by some extent.

Probably upload a full journal when it happend. Probably there is a hint of this misbehavior. Share the link here.

journalctl --boot=-1 --no-hostname | curl -F'file=@-' https://0x0.st

ling · 28 September 2023 07:13

It’s when I’m using the computer normally, and it suddenly restarts without any warning or feedback. When I check the logs after the restart, there’s only this one issue around that time. Sometimes it just freezes completely, with no response to pressing keys like Caps Lock or even switching to a TTY. The computer screen remains on but unresponsive, with no activity. Only the hardware seems to be working. I have to force a reboot by holding down the power button, and when I check the last boot logs, I don’t find any errors. This is really puzzling to me.

ling · 28 September 2023 07:16

I’m really sorry I can’t provide the logs from that particular restart because they’ve already been overwritten. However, I’ve posted relevant screenshots in the v2ray GitHub issue, so maybe those can shed some light on the issue.
v2ray-core/issues/3217

megavolt · 28 September 2023 07:26

That could be a sign of faulty hardware. RAM or CPU are most likely the root cause.

That happens on an Out-Of-Memory problem. It takes a while until the oom-killer takes action and it is response again. If you have swap and the drive is slow, it can take longer. Sometimes in bad situations it is needed to restart the whole session.

Anyway… I would conclude from such behavior that it is a RAM issue. In very rare cases it could be the CPU. I would check the RAM with Memtest. Test each RAM module separately.

That supports the conclusion. Reasons could be in my view:

Memory leak
Buffer overflow
No memory left
Memory corruption

ling · 28 September 2023 07:51

Thank you very much for your response. I searched the internet again for issues related to v2ray memory leaks, and I finally found that this may be due to a DNS configuration problem in v2raya causing a memory leak in v2ray-core. I will try the suggested solution for a while to see if the problem improves. Because on my other computer, which is still running Manjaro 23, and also using v2raya as the GUI interface for configuring v2ray, I always see both memory and CPU being fully utilized by v2ray, which is a significant problem. These issues often lead to sudden freezes, leaving me helpless, and I cannot find the problem through the boot logs (because it is not recorded in boot.log). Thanks again for your help!
This is the link of v2ray-core memory leak

soundofthunder · 28 September 2023 12:00

…or: a rogue application attempting to access an illegal memory area, which also produces a generic (wonderfully descriptive) ‘Out of memory error’. Even without following the OP’s supplied link, this begins to seem more likely. Cheers.

Naturally, because your freezes don’t occur during boot.

My opinion is that the v2ray-core memory leak you describe is likely the culprit; unless someone has deeper insight they care to share.

Good luck with your endeavours.

ling · 28 September 2023 14:47

Based on my attempts, it turns out that the DoH (DNS over HTTPS) feature in v2rayA is the main culprit. When the network disconnects and DoH is enabled, it quickly consumes a large amount of memory until it’s exhausted, and CPU usage also spikes. I noticed this happening when using my network. So, indeed, the memory leak issue is caused by v2ray-core.

I’ve been using earlyoom to prevent OOM (out of memory) situations, and it’s been very effective. It monitors memory usage and promptly cleans up such processes. Linux’s built-in OOM killer is not as reliable as earlyoom in performing this function. With this workaround in place, my system is currently running smoothly. Thanks to everyone for their help, and I hope this post can provide some insights for those facing similar issues!

ling · 28 September 2023 14:51

And it’s advisable to use this method to completely disable the DoH feature.

This information is from the following link: the solution of v2ray-core memory leak

system · 1 October 2023 04:52

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