NetworkManager and Suspend/poweroff issues

unubar · 2024-06-08 05:56:21

After doing a pacman -Syuu, my notebook (ThinkPad P50) is having issues with suspend and poweroff. On either, the screen blanks and a cursor blinks at the top left indefinitely (at least for the 45+ minutes that I waited for something to happen). This happens regardless if I do a poweroff from the Gnome menu or via terminal.

I am also losing NetworkManager after some period of use. This period is just a few minutes sometimes and a few hours at other times.

Below is the output from journalctl for a few recent boots:

https://0x0.st/Xbe4.txt

https://0x0.st/Xbex.txt (this one resulted in a hang)

Appreciate pointing me in the right direction to solve this.

Thanks.

seth · 2024-06-08 07:52:23

Jun 08 07:31:42 Windows10 kernel: wlan0: disconnect from AP d4:6e:0e:3a:2b:5c for new auth to d4:6e:0e:3a:37:f8
Jun 08 07:36:43 Windows10 kernel: wlan0: disconnect from AP d4:6e:0e:3a:37:f8 for new auth to d4:6e:0e:3a:2b:5c
Jun 08 07:56:10 Windows10 kernel: wlan0: disconnect from AP d4:6e:0e:3a:2b:5c for new auth to d4:6e:0e:3a:37:f8
Jun 08 08:01:58 Windows10 kernel: wlan0: disconnect from AP d4:6e:0e:3a:37:f8 for new auth to d4:6e:0e:3a:2b:5c
Jun 08 08:13:22 Windows10 kernel: wlan0: disconnect from AP d4:6e:0e:3a:2b:5c for new auth to d4:6e:0e:3a:37:f8
Jun 08 08:13:53 Windows10 kernel: wlan0: disconnect from AP d4:6e:0e:3a:37:f8 for new auth to d4:6e:0e:3a:2b:5c

There're apparently two APs SSID='Dyafa-3' on 2412 and 2422 MHz and NM can't really decide where to go.
https://wiki.archlinux.org/title/Networ … ets_(WiFi)
See whether selecting a BSSID helps (neither seems to have any signal advantage)

After doing a pacman -Syuu

Why did you issue the second "u"?

Jun 08 00:26:19 Windows10 systemd[1]: Received SIGINT.
Jun 08 00:26:19 Windows10 systemd[1]: Activating special unit System Reboot...
Jun 08 00:26:19 Windows10 systemd[1]: Received SIGINT.
Jun 08 00:26:19 Windows10 systemd[1]: Activating special unit System Reboot...
Jun 08 00:26:19 Windows10 systemd[1]: Received SIGINT.
Jun 08 00:26:19 Windows10 systemd[1]: Activating special unit System Reboot...
Jun 08 00:26:19 Windows10 systemd[1]: Received SIGINT.
Jun 08 00:26:19 Windows10 systemd[1]: Activating special unit System Reboot...
Jun 08 00:26:20 Windows10 systemd[1]: Received SIGINT.
Jun 08 00:26:20 Windows10 systemd[1]: Activating special unit System Reboot...
Jun 08 00:26:20 Windows10 systemd[1]: Received SIGINT.
Jun 08 00:26:20 Windows10 systemd[1]: Activating special unit System Reboot...
Jun 08 00:26:20 Windows10 systemd[1]: Received SIGINT.
Jun 08 00:26:20 Windows10 systemd[1]: Activating special unit System Reboot...
Jun 08 00:26:20 Windows10 systemd[1]: Received SIGINT.
Jun 08 00:26:20 Windows10 systemd[1]: Forcibly rebooting: Ctrl-Alt-Del was pressed more than 7 times within 2s
Jun 08 00:26:20 Windows10 systemd[1]: Shutting down.

The second journal shows you rebooting w/ ctrl+alt+del after ~1 minute.
Don't do that - systemd's default timeout is 90s, it's clearly still responding so it's just waiting for something to die.
Let it wait because it'll then record the offender.

Random things:

Jun 07 14:51:13 Windows10 ntfs-3g[494]: Version 2022.10.3 external FUSE 29
Jun 07 14:51:13 Windows10 ntfs-3g[494]: Mounted /dev/sdb1 (Read-Write, label "", NTFS 3.1)
Jun 07 14:51:13 Windows10 ntfs-3g[494]: Cmdline options: rw
Jun 07 14:51:13 Windows10 ntfs-3g[494]: Mount options: allow_other,nonempty,relatime,rw,fsname=/dev/sdb1,blkdev,blksize=4096
Jun 07 14:51:13 Windows10 ntfs-3g[494]: Ownership and permissions disabled, configuration type 7

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Jun 08 00:25:28 Windows10 wireplumber[1789]: wireplumber: disconnected from pipewire
Jun 08 00:25:28 Windows10 wireplumber[1789]: pw.core: 0x613ce513a090: leaked proxy 0x613ce51912b0 id:6
Jun 08 00:25:28 Windows10 systemd[1152]: Stopping PipeWire Multimedia Service...
Jun 08 00:25:28 Windows10 systemd[1152]: Stopped PipeWire Multimedia Service.
Jun 08 00:25:53 Windows10 pulseaudio[1558]: org.bluez.BatteryProviderManager1.UnregisterBatteryProvider() 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.
Jun 08 00:25:53 Windows10 pulseaudio[1558]: Lost I/O connection in module "module-gsettings"

https://archlinux.org/packages/extra/x8 … ire-pulse/ - running PA and PW at the same time isn't a good idea/option

Jun 07 17:06:27 Windows10 kernel: RIP: 0010:rcu_sched_clock_irq+0xb3c/0x10f0
Jun 07 17:06:27 Windows10 kernel: RIP: 0010:syscall_enter_from_user_mode+0x16/0x70
Jun 07 17:06:27 Windows10 kernel: RIP: 0033:0x71d39f7259ed
Jun 07 17:06:36 Windows10 kernel: RIP: 0010:rcu_exp_handler+0x35/0xe0
Jun 07 17:06:36 Windows10 kernel: RIP: 0010:__fget_light+0x42/0x100
Jun 07 17:06:36 Windows10 kernel: RIP: 0033:0x70b39700fe9d
Jun 07 17:10:23 Windows10 kernel: RIP: 0033:0x70b396f8ed26
Jun 07 17:12:26 Windows10 kernel: RIP: 0033:0x70b396f8ed26
Jun 07 17:13:48 Windows10 kernel: RIP: 0010:__schedule+0x5e/0x1410
Jun 07 17:13:48 Windows10 kernel: RIP: 0033:0x7468e82aa5ab
Jun 07 17:14:29 Windows10 kernel: RIP: 0033:0x70b396f8ed26
Jun 07 17:16:32 Windows10 kernel: RIP: 0033:0x70b396f8ed26
Jun 07 17:16:59 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 17:16:59 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 17:18:35 Windows10 kernel: RIP: 0033:0x70b396f8ed26
Jun 07 17:20:10 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 17:20:10 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 17:20:38 Windows10 kernel: RIP: 0033:0x70b396f8ed26
Jun 07 17:22:41 Windows10 kernel: RIP: 0033:0x70b396f8ed26
Jun 07 17:32:55 Windows10 kernel: RIP: 0010:__update_load_avg_blocked_se+0xce/0x230
Jun 07 17:32:55 Windows10 kernel: RIP: 0033:0x76feb691d53d
Jun 07 17:36:06 Windows10 kernel: RIP: 0010:Task_Switch+0xd98/0x1c20 [vmmon]
Jun 07 17:36:06 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 17:36:06 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 17:36:06 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 17:39:17 Windows10 kernel: RIP: 0010:native_sched_clock+0x48/0x80
Jun 07 17:45:40 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 17:45:40 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 17:48:51 Windows10 kernel: RIP: 0010:__orc_find+0x61/0x80
Jun 07 17:48:51 Windows10 kernel: RIP: 0010:cpuidle_enter_state+0xc6/0x430
Jun 07 17:48:51 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 17:48:51 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 17:55:13 Windows10 kernel: RIP: 0010:update_load_avg+0x85/0x760
Jun 07 18:01:35 Windows10 kernel: RIP: 0010:mem_cgroup_css_rstat_flush+0x27/0x320
Jun 07 18:04:47 Windows10 kernel: RIP: 0010:check_cfs_rq_runtime+0x0/0x50
Jun 07 18:04:47 Windows10 kernel: RIP: 0033:0x70b397004910
Jun 07 18:04:47 Windows10 kernel: RIP: 0033:0x7468e82ba5d9
Jun 07 18:23:53 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 18:23:53 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 18:23:53 Windows10 kernel: RIP: 0010:update_irq_load_avg+0x4a/0x4c0
Jun 07 18:23:53 Windows10 kernel: RIP: 0033:0x70b397004910
Jun 07 18:30:16 Windows10 kernel: RIP: 0010:entry_SYSCALL_64_after_hwframe+0x59/0xe2
Jun 07 18:39:49 Windows10 kernel: RIP: 0010:Task_Switch+0xd98/0x1c20 [vmmon]
Jun 07 18:39:49 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 18:46:11 Windows10 kernel: RIP: 0010:down_read+0x23/0xa0
Jun 07 18:46:11 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 18:49:23 Windows10 kernel: RIP: 0010:cgroup_rstat_flush_locked+0xda/0x390
Jun 07 18:52:34 Windows10 kernel: RIP: 0010:elv_merge+0x29/0x100
Jun 07 18:55:45 Windows10 kernel: RIP: 0033:0x7c7b17473ba0
Jun 07 18:55:45 Windows10 kernel: RIP: 0010:Task_Switch+0xd98/0x1c20 [vmmon]
Jun 07 18:55:45 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 19:05:18 Windows10 kernel: RIP: 0010:rcu_sched_clock_irq+0x11c/0x10f0
Jun 07 19:05:18 Windows10 kernel: RIP: 0010:cpuidle_enter_state+0xc6/0x430
Jun 07 19:14:52 Windows10 kernel: RIP: 0010:syscall_return_via_sysret+0x1b/0x8b
Jun 07 19:18:03 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 19:18:03 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 19:24:25 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 19:24:25 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 19:30:47 Windows10 kernel: RIP: 0010:orc_find.part.0+0x52/0x1d0
Jun 07 19:30:47 Windows10 kernel: RIP: 0033:0x7271b1605737
Jun 07 19:30:47 Windows10 kernel: RIP: 0033:0x7271b1590a30
Jun 07 19:33:59 Windows10 kernel: RIP: 0010:leave_mm+0x0/0x40
Jun 07 19:33:59 Windows10 kernel: RIP: 0010:entry_SYSRETQ_unsafe_stack+0xa/0xd
Jun 07 19:46:43 Windows10 kernel: RIP: 0010:mem_cgroup_css_rstat_flush+0x297/0x320
Jun 07 19:46:43 Windows10 kernel: RIP: 0010:Task_Switch+0xd98/0x1c20 [vmmon]
Jun 07 19:46:43 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 19:49:54 Windows10 kernel: RIP: 0010:xas_find_marked+0x9c/0x320
Jun 07 19:56:17 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 19:56:17 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 19:56:17 Windows10 kernel: RIP: 0010:__hrtimer_run_queues+0xc8/0x2a0
Jun 07 19:56:17 Windows10 kernel: RIP: 0010:Task_Switch+0x12c0/0x1c20 [vmmon]
Jun 07 19:56:17 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 19:56:17 Windows10 kernel: RIP: 0010:mem_cgroup_handle_over_high+0x0/0x2a0
Jun 07 19:56:17 Windows10 kernel: RIP: 0033:0x70b397004910
Jun 07 20:02:39 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 20:02:39 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 20:12:12 Windows10 kernel: RIP: 0010:asm_sysvec_apic_timer_interrupt+0x0/0x20
Jun 07 20:12:12 Windows10 kernel: RIP: 0010:syscall_enter_from_user_mode+0x16/0x70
Jun 07 20:12:12 Windows10 kernel: RIP: 0033:0x7b519d9f7a44
Jun 07 20:18:35 Windows10 kernel: RIP: 0010:__calc_delta.constprop.0+0x9e/0xc0
Jun 07 20:31:19 Windows10 kernel: RIP: 0010:queue_delayed_work_on+0x0/0x50
Jun 07 20:37:42 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 20:37:42 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 20:44:04 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 20:44:04 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 20:50:26 Windows10 kernel: RIP: 0033:0x7095f1603f42
Jun 07 20:53:37 Windows10 kernel: RIP: 0010:__find_get_block+0x1d1/0x340
Jun 07 20:56:48 Windows10 kernel: RIP: 0010:__schedule+0x16d/0x1410
Jun 07 21:00:00 Windows10 kernel: RIP: 0010:Task_Switch+0xd98/0x1c20 [vmmon]
Jun 07 21:00:00 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 21:03:11 Windows10 kernel: RIP: 0010:can_migrate_task+0x20/0x500
Jun 07 21:09:33 Windows10 kernel: RIP: 0010:do_sys_poll+0x50e/0x5e0
Jun 07 21:09:33 Windows10 kernel: RIP: 0033:0x70b397004910
Jun 07 21:09:33 Windows10 kernel: RIP: 0010:__enqueue_entity+0x30/0x130
Jun 07 21:25:29 Windows10 kernel: RIP: 0010:need_update+0x45/0xa0
Jun 07 21:25:29 Windows10 kernel: RIP: 0010:psi_group_change+0x23/0x3d0
Jun 07 21:25:29 Windows10 kernel: RIP: 0010:cpuidle_enter_state+0xc6/0x430
Jun 07 21:25:29 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 21:25:29 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 21:25:29 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 21:25:29 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 21:35:02 Windows10 kernel: RIP: 0010:mem_cgroup_css_rstat_flush+0x3c/0x320
Jun 07 21:35:02 Windows10 kernel: RIP: 0033:0x7aea51ebff69
Jun 07 21:38:13 Windows10 kernel: RIP: 0010:syscall_return_via_sysret+0x1b/0x8b
Jun 07 21:57:20 Windows10 kernel: RIP: 0010:avg_vruntime+0x0/0x80
Jun 07 22:16:27 Windows10 kernel: RIP: 0033:0x7aea53f8e7a3
Jun 07 22:29:12 Windows10 kernel: RIP: 0010:mem_cgroup_css_rstat_flush+0x9f/0x320
Jun 07 22:35:34 Windows10 kernel: RIP: 0010:update_load_avg+0x3ad/0x760
Jun 07 22:35:34 Windows10 kernel: RIP: 0033:0x7aea5401c818
Jun 07 22:41:56 Windows10 kernel: RIP: 0010:memchr_inv+0xa2/0xf0
Jun 07 22:41:56 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 22:41:56 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 22:41:56 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 22:41:56 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 22:48:19 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 22:48:19 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 22:51:30 Windows10 kernel: RIP: 0010:cpuacct_charge+0x17/0x40
Jun 07 22:51:30 Windows10 kernel: RIP: 0033:0x70b397004910
Jun 07 22:51:30 Windows10 kernel: RIP: 0010:rcu_preempt_deferred_qs+0x0/0x40
Jun 07 22:54:41 Windows10 kernel: RIP: 0010:schedule+0x0/0xd0
Jun 07 22:54:41 Windows10 kernel: RIP: 0010:psi_task_switch+0x3b/0x230
Jun 07 22:54:41 Windows10 kernel: RIP: 0033:0x70b397004910
Jun 07 23:01:03 Windows10 kernel: RIP: 0010:Task_Switch+0xd98/0x1c20 [vmmon]
Jun 07 23:01:03 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 23:07:25 Windows10 kernel: RIP: 0010:_raw_spin_lock+0x1b/0x30
Jun 07 23:16:59 Windows10 kernel: RIP: 0010:watchdog+0x11c/0x500
Jun 07 23:20:10 Windows10 kernel: RIP: 0010:Task_Switch+0xd98/0x1c20 [vmmon]
Jun 07 23:20:10 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 23:20:10 Windows10 kernel: RIP: 0010:pipe_write+0x41b/0x730
Jun 07 23:20:10 Windows10 kernel: RIP: 0033:0x76feb691d53d
Jun 07 23:23:21 Windows10 kernel: RIP: 0010:cpuidle_governor_latency_req+0x16/0x50
Jun 07 23:23:21 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 23:23:21 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 23:23:21 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 23:23:21 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 23:29:43 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 23:29:43 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 23:29:43 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 23:29:43 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 23:32:55 Windows10 kernel: RIP: 0033:0x70658592df50
Jun 07 23:32:55 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 23:32:55 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 23:45:39 Windows10 kernel: RIP: 0010:watchdog+0x11c/0x500
Jun 07 23:52:01 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 23:52:01 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 23:52:01 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 23:52:01 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 23:55:13 Windows10 kernel: RIP: 0010:mem_cgroup_css_rstat_flush+0x253/0x320
Jun 07 23:55:13 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 23:55:13 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 08 00:07:57 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 08 00:07:57 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 08 00:11:08 Windows10 kernel: RIP: 0010:psi_group_change+0x5/0x3d0
Jun 08 00:20:42 Windows10 kernel: RIP: 0010:__rcu_read_lock+0x18/0x30
Jun 08 00:20:42 Windows10 kernel: RIP: 0010:memcg_slab_post_alloc_hook+0x78/0x240
Jun 08 00:20:42 Windows10 kernel: RIP: 0033:0x7271b161447b
Jun 08 00:23:53 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 08 00:23:53 Windows10 kernel: RIP: 0033:0x70b39700d9ed

There's a shit-ton of kernel oopsies - you may want to figure how many of them are not to be blamed on vmmon (vmware) to be able to adress the remainders.
Obviously this (and thereore likely vmware) doesn't exactly contribute to the reliability of the system, so make sure it's not a or the defining factor of your condition.

unubar · 2024-06-08 08:37:53

seth wrote:

There're apparently two APs SSID='Dyafa-3' on 2412 and 2422 MHz and NM can't really decide where to go.
https://wiki.archlinux.org/title/Networ … ets_(WiFi)
See whether selecting a BSSID helps (neither seems to have any signal advantage)

I am in a place where there are multiple access points with the same SSID.

seth wrote:

After doing a pacman -Syuu
Why did you issue the second "u"?

That's what my Linux friend who encouraged me to install Arch uses when he updates my system. (btw, this has been running well for the last 4 years on this notebook).
I read now about it and I should probably be using just -Syu

seth wrote:

Jun 08 00:26:20 Windows10 systemd[1]: Activating special unit System Reboot...
Jun 08 00:26:20 Windows10 systemd[1]: Received SIGINT.
Jun 08 00:26:20 Windows10 systemd[1]: Forcibly rebooting: Ctrl-Alt-Del was pressed more than 7 times within 2s
Jun 08 00:26:20 Windows10 systemd[1]: Shutting down.
The second journal shows you rebooting w/ ctrl+alt+del after ~1 minute.
Don't do that - systemd's default timeout is 90s, it's clearly still responding so it's just waiting for something to die.
Let it wait because it'll then record the offender.

Ok. Previously I was waiting for a lot longer but I will note to wait at least 90s.

seth wrote:

Random things:

Jun 07 14:51:13 Windows10 ntfs-3g[494]: Version 2022.10.3 external FUSE 29
Jun 07 14:51:13 Windows10 ntfs-3g[494]: Mounted /dev/sdb1 (Read-Write, label "", NTFS 3.1)
Jun 07 14:51:13 Windows10 ntfs-3g[494]: Cmdline options: rw
Jun 07 14:51:13 Windows10 ntfs-3g[494]: Mount options: allow_other,nonempty,relatime,rw,fsname=/dev/sdb1,blkdev,blksize=4096
Jun 07 14:51:13 Windows10 ntfs-3g[494]: Ownership and permissions disabled, configuration type 7

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

I don't have windows installed. I am using windows inside VMWare only. Do I still need to disable fast start?

seth wrote:

https://archlinux.org/packages/extra/x8 … ire-pulse/ - running PA and PW at the same time isn't a good idea/option

ok.

seth wrote:

Jun 07 17:06:27 Windows10 kernel: RIP: 0010:rcu_sched_clock_irq+0xb3c/0x10f0
Jun 07 17:06:27 Windows10 kernel: RIP: 0010:syscall_enter_from_user_mode+0x16/0x70
Jun 07 17:06:27 Windows10 kernel: RIP: 0033:0x71d39f7259ed
Jun 07 17:06:36 Windows10 kernel: RIP: 0010:rcu_exp_handler+0x35/0xe0
Jun 07 17:06:36 Windows10 kernel: RIP: 0010:__fget_light+0x42/0x100
Jun 07 17:06:36 Windows10 kernel: RIP: 0033:0x70b39700fe9d
Jun 07 17:10:23 Windows10 kernel: RIP: 0033:0x70b396f8ed26
Jun 07 17:12:26 Windows10 kernel: RIP: 0033:0x70b396f8ed26
Jun 07 17:13:48 Windows10 kernel: RIP: 0010:__schedule+0x5e/0x1410
Jun 07 17:13:48 Windows10 kernel: RIP: 0033:0x7468e82aa5ab
Jun 07 17:14:29 Windows10 kernel: RIP: 0033:0x70b396f8ed26
Jun 07 17:16:32 Windows10 kernel: RIP: 0033:0x70b396f8ed26
Jun 07 17:16:59 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 17:16:59 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 17:18:35 Windows10 kernel: RIP: 0033:0x70b396f8ed26
Jun 07 17:20:10 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 17:20:10 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 17:20:38 Windows10 kernel: RIP: 0033:0x70b396f8ed26
Jun 07 17:22:41 Windows10 kernel: RIP: 0033:0x70b396f8ed26
Jun 07 17:32:55 Windows10 kernel: RIP: 0010:__update_load_avg_blocked_se+0xce/0x230
Jun 07 17:32:55 Windows10 kernel: RIP: 0033:0x76feb691d53d
Jun 07 17:36:06 Windows10 kernel: RIP: 0010:Task_Switch+0xd98/0x1c20 [vmmon]
Jun 07 17:36:06 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 17:36:06 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 17:36:06 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 17:39:17 Windows10 kernel: RIP: 0010:native_sched_clock+0x48/0x80
Jun 07 17:45:40 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 17:45:40 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 17:48:51 Windows10 kernel: RIP: 0010:__orc_find+0x61/0x80
Jun 07 17:48:51 Windows10 kernel: RIP: 0010:cpuidle_enter_state+0xc6/0x430
Jun 07 17:48:51 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 17:48:51 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 17:55:13 Windows10 kernel: RIP: 0010:update_load_avg+0x85/0x760
Jun 07 18:01:35 Windows10 kernel: RIP: 0010:mem_cgroup_css_rstat_flush+0x27/0x320
Jun 07 18:04:47 Windows10 kernel: RIP: 0010:check_cfs_rq_runtime+0x0/0x50
Jun 07 18:04:47 Windows10 kernel: RIP: 0033:0x70b397004910
Jun 07 18:04:47 Windows10 kernel: RIP: 0033:0x7468e82ba5d9
Jun 07 18:23:53 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 18:23:53 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 18:23:53 Windows10 kernel: RIP: 0010:update_irq_load_avg+0x4a/0x4c0
Jun 07 18:23:53 Windows10 kernel: RIP: 0033:0x70b397004910
Jun 07 18:30:16 Windows10 kernel: RIP: 0010:entry_SYSCALL_64_after_hwframe+0x59/0xe2
Jun 07 18:39:49 Windows10 kernel: RIP: 0010:Task_Switch+0xd98/0x1c20 [vmmon]
Jun 07 18:39:49 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 18:46:11 Windows10 kernel: RIP: 0010:down_read+0x23/0xa0
Jun 07 18:46:11 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 18:49:23 Windows10 kernel: RIP: 0010:cgroup_rstat_flush_locked+0xda/0x390
Jun 07 18:52:34 Windows10 kernel: RIP: 0010:elv_merge+0x29/0x100
Jun 07 18:55:45 Windows10 kernel: RIP: 0033:0x7c7b17473ba0
Jun 07 18:55:45 Windows10 kernel: RIP: 0010:Task_Switch+0xd98/0x1c20 [vmmon]
Jun 07 18:55:45 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 19:05:18 Windows10 kernel: RIP: 0010:rcu_sched_clock_irq+0x11c/0x10f0
Jun 07 19:05:18 Windows10 kernel: RIP: 0010:cpuidle_enter_state+0xc6/0x430
Jun 07 19:14:52 Windows10 kernel: RIP: 0010:syscall_return_via_sysret+0x1b/0x8b
Jun 07 19:18:03 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 19:18:03 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 19:24:25 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 19:24:25 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 19:30:47 Windows10 kernel: RIP: 0010:orc_find.part.0+0x52/0x1d0
Jun 07 19:30:47 Windows10 kernel: RIP: 0033:0x7271b1605737
Jun 07 19:30:47 Windows10 kernel: RIP: 0033:0x7271b1590a30
Jun 07 19:33:59 Windows10 kernel: RIP: 0010:leave_mm+0x0/0x40
Jun 07 19:33:59 Windows10 kernel: RIP: 0010:entry_SYSRETQ_unsafe_stack+0xa/0xd
Jun 07 19:46:43 Windows10 kernel: RIP: 0010:mem_cgroup_css_rstat_flush+0x297/0x320
Jun 07 19:46:43 Windows10 kernel: RIP: 0010:Task_Switch+0xd98/0x1c20 [vmmon]
Jun 07 19:46:43 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 19:49:54 Windows10 kernel: RIP: 0010:xas_find_marked+0x9c/0x320
Jun 07 19:56:17 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 19:56:17 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 19:56:17 Windows10 kernel: RIP: 0010:__hrtimer_run_queues+0xc8/0x2a0
Jun 07 19:56:17 Windows10 kernel: RIP: 0010:Task_Switch+0x12c0/0x1c20 [vmmon]
Jun 07 19:56:17 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 19:56:17 Windows10 kernel: RIP: 0010:mem_cgroup_handle_over_high+0x0/0x2a0
Jun 07 19:56:17 Windows10 kernel: RIP: 0033:0x70b397004910
Jun 07 20:02:39 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 20:02:39 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 20:12:12 Windows10 kernel: RIP: 0010:asm_sysvec_apic_timer_interrupt+0x0/0x20
Jun 07 20:12:12 Windows10 kernel: RIP: 0010:syscall_enter_from_user_mode+0x16/0x70
Jun 07 20:12:12 Windows10 kernel: RIP: 0033:0x7b519d9f7a44
Jun 07 20:18:35 Windows10 kernel: RIP: 0010:__calc_delta.constprop.0+0x9e/0xc0
Jun 07 20:31:19 Windows10 kernel: RIP: 0010:queue_delayed_work_on+0x0/0x50
Jun 07 20:37:42 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 20:37:42 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 20:44:04 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 20:44:04 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 20:50:26 Windows10 kernel: RIP: 0033:0x7095f1603f42
Jun 07 20:53:37 Windows10 kernel: RIP: 0010:__find_get_block+0x1d1/0x340
Jun 07 20:56:48 Windows10 kernel: RIP: 0010:__schedule+0x16d/0x1410
Jun 07 21:00:00 Windows10 kernel: RIP: 0010:Task_Switch+0xd98/0x1c20 [vmmon]
Jun 07 21:00:00 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 21:03:11 Windows10 kernel: RIP: 0010:can_migrate_task+0x20/0x500
Jun 07 21:09:33 Windows10 kernel: RIP: 0010:do_sys_poll+0x50e/0x5e0
Jun 07 21:09:33 Windows10 kernel: RIP: 0033:0x70b397004910
Jun 07 21:09:33 Windows10 kernel: RIP: 0010:__enqueue_entity+0x30/0x130
Jun 07 21:25:29 Windows10 kernel: RIP: 0010:need_update+0x45/0xa0
Jun 07 21:25:29 Windows10 kernel: RIP: 0010:psi_group_change+0x23/0x3d0
Jun 07 21:25:29 Windows10 kernel: RIP: 0010:cpuidle_enter_state+0xc6/0x430
Jun 07 21:25:29 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 21:25:29 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 21:25:29 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 21:25:29 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 21:35:02 Windows10 kernel: RIP: 0010:mem_cgroup_css_rstat_flush+0x3c/0x320
Jun 07 21:35:02 Windows10 kernel: RIP: 0033:0x7aea51ebff69
Jun 07 21:38:13 Windows10 kernel: RIP: 0010:syscall_return_via_sysret+0x1b/0x8b
Jun 07 21:57:20 Windows10 kernel: RIP: 0010:avg_vruntime+0x0/0x80
Jun 07 22:16:27 Windows10 kernel: RIP: 0033:0x7aea53f8e7a3
Jun 07 22:29:12 Windows10 kernel: RIP: 0010:mem_cgroup_css_rstat_flush+0x9f/0x320
Jun 07 22:35:34 Windows10 kernel: RIP: 0010:update_load_avg+0x3ad/0x760
Jun 07 22:35:34 Windows10 kernel: RIP: 0033:0x7aea5401c818
Jun 07 22:41:56 Windows10 kernel: RIP: 0010:memchr_inv+0xa2/0xf0
Jun 07 22:41:56 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 22:41:56 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 22:41:56 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 22:41:56 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 22:48:19 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 22:48:19 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 22:51:30 Windows10 kernel: RIP: 0010:cpuacct_charge+0x17/0x40
Jun 07 22:51:30 Windows10 kernel: RIP: 0033:0x70b397004910
Jun 07 22:51:30 Windows10 kernel: RIP: 0010:rcu_preempt_deferred_qs+0x0/0x40
Jun 07 22:54:41 Windows10 kernel: RIP: 0010:schedule+0x0/0xd0
Jun 07 22:54:41 Windows10 kernel: RIP: 0010:psi_task_switch+0x3b/0x230
Jun 07 22:54:41 Windows10 kernel: RIP: 0033:0x70b397004910
Jun 07 23:01:03 Windows10 kernel: RIP: 0010:Task_Switch+0xd98/0x1c20 [vmmon]
Jun 07 23:01:03 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 23:07:25 Windows10 kernel: RIP: 0010:_raw_spin_lock+0x1b/0x30
Jun 07 23:16:59 Windows10 kernel: RIP: 0010:watchdog+0x11c/0x500
Jun 07 23:20:10 Windows10 kernel: RIP: 0010:Task_Switch+0xd98/0x1c20 [vmmon]
Jun 07 23:20:10 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 23:20:10 Windows10 kernel: RIP: 0010:pipe_write+0x41b/0x730
Jun 07 23:20:10 Windows10 kernel: RIP: 0033:0x76feb691d53d
Jun 07 23:23:21 Windows10 kernel: RIP: 0010:cpuidle_governor_latency_req+0x16/0x50
Jun 07 23:23:21 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 23:23:21 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 23:23:21 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 23:23:21 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 23:29:43 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 23:29:43 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 23:29:43 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 23:29:43 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 23:32:55 Windows10 kernel: RIP: 0033:0x70658592df50
Jun 07 23:32:55 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 23:32:55 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 23:45:39 Windows10 kernel: RIP: 0010:watchdog+0x11c/0x500
Jun 07 23:52:01 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 23:52:01 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 23:52:01 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 23:52:01 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 07 23:55:13 Windows10 kernel: RIP: 0010:mem_cgroup_css_rstat_flush+0x253/0x320
Jun 07 23:55:13 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 07 23:55:13 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 08 00:07:57 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 08 00:07:57 Windows10 kernel: RIP: 0033:0x70b39700d9ed
Jun 08 00:11:08 Windows10 kernel: RIP: 0010:psi_group_change+0x5/0x3d0
Jun 08 00:20:42 Windows10 kernel: RIP: 0010:__rcu_read_lock+0x18/0x30
Jun 08 00:20:42 Windows10 kernel: RIP: 0010:memcg_slab_post_alloc_hook+0x78/0x240
Jun 08 00:20:42 Windows10 kernel: RIP: 0033:0x7271b161447b
Jun 08 00:23:53 Windows10 kernel: RIP: 0010:Task_Switch+0xaf6/0x1c20 [vmmon]
Jun 08 00:23:53 Windows10 kernel: RIP: 0033:0x70b39700d9ed

There's a shit-ton of kernel oopsies - you may want to figure how many of them are not to be blamed on vmmon (vmware) to be able to adress the remainders.
Obviously this (and thereore likely vmware) doesn't exactly contribute to the reliability of the system, so make sure it's not a or the defining factor of your condition.

How do I address these issues? Where do I start? This might be the defining factor as you said.

My Linux guy has recommended me to re-install Arch from scratch as this installation is 4+ years old. I am trying to see if I can salvage the situation without having to do that now.

seth · 2024-06-08 12:10:28

I am in a place where there are multiple access points with the same SSID.

Yes, I can see that and the suggestion was to avoid AP hopping by locking into a single BSSID

I don't have windows installed. … Do I still need to disable fast start?

No, of couse not. The fast-start condition would cause to parallel OS on the HW and undefined states of the latter, but that's not a concern w/ virtual HW.

How do I address these issues? Where do I start? This might be the defining factor as you said.

Avoid running vmware/loading the vmmon module for a while, see whether there're reamining kernel oopses.
They're however no necessarily (actually not very likely) the cause for poweroff stalls - well see what processes refuse to die.

My Linux guy has recommended me to re-install Arch from scratch as this installation is 4+ years old.

The one who told you to run "-Syuu" ? … There you go.
Re-installing the same system will most likely result in the same condition, it's better to understand the problem and then fix it.
Re-installation is a windows tradition because up-until XP you'd run that as administrator (there was not even a sane user system before NT/2000/XP) and screwing up your local config implied to screw up the system at large.

unubar · 2024-06-08 15:07:15

seth wrote:

How do I address these issues? Where do I start? This might be the defining factor as you said.
Avoid running vmware/loading the vmmon module for a while, see whether there're reamining kernel oopses.
They're however no necessarily (actually not very likely) the cause for poweroff stalls - well see what processes refuse to die.

It seems the issues exacerbate when I run vmware. Here is a log of the previous boot where poweroff wouldn't complete after running and exiting vmware.
https://0x0.st/XbLy.txt

The system started powering down at Jun 08 15:49:51
I left it for more than an hour before force shutting down the system.

This is a log of the current boot after that:
https://0x0.st/XbL4.txt

seth wrote:

My Linux guy has recommended me to re-install Arch from scratch as this installation is 4+ years old.
The one who told you to run "-Syuu" ? … There you go.
Re-installing the same system will most likely result in the same condition, it's better to understand the problem and then fix it.
Re-installation is a windows tradition because up-until XP you'd run that as administrator (there was not even a sane user system before NT/2000/XP) and screwing up your local config implied to screw up the system at large.

To be fair, he has never had me do a re-install for the last 4 years.
His rationale for the re-install is that Gnome had common dependencies on KDE libs and now it does not so there are probably some KDE dependencies that are broken and messing with Gnome (e.g. mysql db errors in the log).
So, it would be faster to format the drive and re-install to get rid of all the unnecessary dependencies.

If there is a way to get this as good as a new install, I would like to take that route. That way I get to understand the system better too.

seth · 2024-06-08 15:29:39

Jun 08 15:50:18 Windows10 systemd[1155]: Stopped Sound Service.
Jun 08 15:51:21 Windows10 systemd[1]: vmware-USBArbitrator.service: Stopping timed out. Terminating.
Jun 08 15:51:21 Windows10 systemd[1]: vmware-USBArbitrator.service: Control process exited, code=killed, status=15/TERM
Jun 08 15:51:21 Windows10 systemd[1]: ntpd.service: State 'stop-sigterm' timed out. Killing.
Jun 08 15:51:21 Windows10 systemd[1]: ntpd.service: Killing process 579 (ntpd) with signal SIGKILL.
Jun 08 15:51:21 Windows10 systemd[1]: ntpd.service: Failed to kill control group /system.slice/ntpd.service, ignoring: Invalid argument
Jun 08 15:51:21 Windows10 systemd[1]: polkit.service: State 'stop-sigterm' timed out. Killing.
Jun 08 15:51:21 Windows10 systemd[1]: polkit.service: Killing process 644 (polkitd) with signal SIGKILL.
Jun 08 15:51:21 Windows10 systemd[1]: polkit.service: Failed to kill control group /system.slice/polkit.service, ignoring: Invalid argument
Jun 08 15:51:21 Windows10 systemd[1]: power-profiles-daemon.service: State 'stop-sigterm' timed out. Killing.
Jun 08 15:51:21 Windows10 systemd[1]: power-profiles-daemon.service: Killing process 1089 (power-profiles-) with signal SIGKILL.
Jun 08 15:51:21 Windows10 systemd[1]: power-profiles-daemon.service: Failed to kill control group /system.slice/power-profiles-daemon.service, ignoring: Invalid argument
Jun 08 15:51:21 Windows10 systemd[1]: bluetooth.service: State 'stop-sigterm' timed out. Killing.
Jun 08 15:51:21 Windows10 systemd[1]: bluetooth.service: Killing process 520 (bluetoothd) with signal SIGKILL.
Jun 08 15:51:21 Windows10 systemd[1]: colord.service: State 'stop-sigterm' timed out. Killing.
Jun 08 15:51:21 Windows10 systemd[1]: colord.service: Killing process 823 (colord) with signal SIGKILL.
Jun 08 15:51:21 Windows10 systemd[1]: colord.service: Failed to kill control group /system.slice/colord.service, ignoring: Invalid argument
Jun 08 15:51:21 Windows10 systemd[1]: accounts-daemon.service: State 'stop-sigterm' timed out. Killing.
Jun 08 15:51:21 Windows10 systemd[1]: accounts-daemon.service: Killing process 615 (accounts-daemon) with signal SIGKILL.
Jun 08 15:51:21 Windows10 systemd[1]: upower.service: State 'stop-sigterm' timed out. Killing.
Jun 08 15:51:21 Windows10 systemd[1]: upower.service: Killing process 866 (upowerd) with signal SIGKILL.
Jun 08 15:51:21 Windows10 systemd[1]: upower.service: Failed to kill control group /system.slice/upower.service, ignoring: Invalid argument
Jun 08 15:51:21 Windows10 systemd[1]: rtkit-daemon.service: State 'stop-sigterm' timed out. Killing.
Jun 08 15:51:21 Windows10 systemd[1]: rtkit-daemon.service: Killing process 1070 (rtkit-daemon) with signal SIGKILL.
Jun 08 15:51:21 Windows10 systemd[1]: rtkit-daemon.service: Failed to kill control group /system.slice/rtkit-daemon.service, ignoring: Invalid argument
Jun 08 15:51:21 Windows10 systemd[1155]: xdg-document-portal.service: State 'stop-sigterm' timed out. Killing.
Jun 08 15:51:21 Windows10 systemd[1155]: xdg-document-portal.service: Killing process 1628 (xdg-document-po) with signal SIGKILL.
Jun 08 15:51:21 Windows10 systemd[1155]: xdg-document-portal.service: Killing process 1644 (fusermount3) with signal SIGKILL.
Jun 08 15:51:21 Windows10 systemd[1155]: xdg-document-portal.service: Killing process 4415 (fusermount3) with signal SIGKILL.
Jun 08 15:51:21 Windows10 systemd[1155]: gvfs-daemon.service: State 'final-sigterm' timed out. Killing.
Jun 08 15:51:21 Windows10 systemd[1155]: gvfs-daemon.service: Killing process 1303 (gvfsd-fuse) with signal SIGKILL.
Jun 08 15:51:21 Windows10 systemd[1155]: gvfs-daemon.service: Killing process 4414 (fusermount3) with signal SIGKILL.
Jun 08 15:51:21 Windows10 systemd[1155]: gvfs-daemon.service: Failed to kill control group /user.slice/user-1000.slice/user@1000.service/session.slice/gvfs-daemon.service, ignoring: Invalid argument
Jun 08 15:51:21 Windows10 systemd[1155]: gvfs-daemon.service: Failed with result 'timeout'.
Jun 08 15:51:21 Windows10 systemd[1155]: gvfs-daemon.service: Unit process 4414 (fusermount3) remains running after unit stopped.
Jun 08 15:51:21 Windows10 systemd[1155]: Stopped Virtual filesystem service.
Jun 08 15:51:21 Windows10 systemd[1155]: xdg-document-portal.service: Main process exited, code=killed, status=9/KILL
Jun 08 15:51:23 Windows10 systemd[1]: vmware.service: State 'stop-sigterm' timed out. Killing.
Jun 08 15:51:23 Windows10 systemd[1]: vmware.service: Killing process 646 (vmnet-bridge) with signal SIGKILL.
Jun 08 15:51:23 Windows10 systemd[1]: vmware.service: Killing process 692 (vmnet-netifup) with signal SIGKILL.
Jun 08 15:51:23 Windows10 systemd[1]: vmware.service: Killing process 706 (vmnet-netifup) with signal SIGKILL.
Jun 08 15:51:23 Windows10 systemd[1]: vmware.service: Killing process 721 (vmnet-netifup) with signal SIGKILL.
Jun 08 15:51:23 Windows10 systemd[1155]: app-gnome-vmware\x2dworkstation-2546.scope: Stopping timed out. Killing.
Jun 08 15:51:23 Windows10 systemd[1155]: app-gnome-vmware\x2dworkstation-2546.scope: Killing process 2712 (vmware-vmx) with signal SIGKILL.
Jun 08 15:51:23 Windows10 systemd[1155]: app-gnome-vmware\x2dworkstation-2546.scope: Failed to kill control group /user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-vmware\x2dworkstation-2546.scope, ignoring: Invalid argument
Jun 08 15:51:23 Windows10 systemd[1155]: app-gnome-vmware\x2dworkstation-2546.scope: Failed with result 'timeout'.
Jun 08 15:51:23 Windows10 systemd[1155]: Stopped Application launched by gnome-shell.
Jun 08 15:51:23 Windows10 systemd[1155]: app-gnome-vmware\x2dworkstation-2546.scope: Consumed 1h 6min 4.844s CPU time, 15.6G memory peak, 0B memory swap peak.

Jun 08 15:51:23 Windows10 systemd[1]: systemd-logind.service: State 'final-sigterm' timed out. Killing.
Jun 08 15:51:34 Windows10 kernel: wlan0: deauthenticated from 42:86:83:77:3a:f7 (Reason: 3=DEAUTH_LEAVING)
Jun 08 15:51:53 Windows10 systemd[1]: user@1000.service: State 'stop-sigterm' timed out. Killing.
Jun 08 15:51:53 Windows10 systemd[1]: user@1000.service: Killing process 1155 (systemd) with signal SIGKILL.
Jun 08 15:51:53 Windows10 systemd[1]: user@1000.service: Killing process 4564 (dbus-broker-lau) with signal SIGKILL.
Jun 08 15:51:53 Windows10 systemd[1]: user@1000.service: Killing process 4565 (dbus-broker) with signal SIGKILL.
Jun 08 15:51:53 Windows10 systemd[1]: user@1000.service: Killing process 4415 (fusermount3) with signal SIGKILL.
Jun 08 15:51:53 Windows10 systemd[1]: user@1000.service: Killing process 4414 (fusermount3) with signal SIGKILL.
Jun 08 15:51:53 Windows10 systemd[1]: user@1000.service: Killing process 2712 (vmware-vmx) with signal SIGKILL.
Jun 08 15:51:53 Windows10 systemd[1]: user@1000.service: Main process exited, code=killed, status=9/KILL
Jun 08 15:51:53 Windows10 systemd[1]: user@1000.service: Killing process 4415 (fusermount3) with signal SIGKILL.
Jun 08 15:51:53 Windows10 systemd[1]: user@1000.service: Killing process 4414 (fusermount3) with signal SIGKILL.
Jun 08 15:51:53 Windows10 systemd[1]: user@1000.service: Killing process 2712 (vmware-vmx) with signal SIGKILL.

There's a whole host of services not going down

systemctl --user mask xdg-document-portal.service

https://bbs.archlinux.org/viewtopic.php?id=296469
But there're obviously also (stale?) vmware related services - can you just log out (without even trying to shutdown)?
Can you shutdown/logout after first explicitly stopping vmware-vmx ?

Jun 08 14:49:55 Windows10 kernel: CPU: 3 PID: 2652 Comm: vmware-vmx Tainted: P           OE      6.6.32-1-lts #1 ee405f31cc2370c66e95bb51982e71a894d4c0fd
Jun 08 15:14:17 Windows10 kernel: INFO: task vmware-vmx:2712 blocked for more than 122 seconds.
Jun 08 15:14:17 Windows10 kernel: task:vmware-vmx      state:D stack:0     pid:2712  ppid:1155   flags:0x00004002
Jun 08 15:16:20 Windows10 kernel: INFO: task vmware-vmx:2712 blocked for more than 245 seconds.
Jun 08 15:16:20 Windows10 kernel: task:vmware-vmx      state:D stack:0     pid:2712  ppid:1155   flags:0x00004002
Jun 08 15:18:23 Windows10 kernel: INFO: task vmware-vmx:2712 blocked for more than 368 seconds.
Jun 08 15:18:23 Windows10 kernel: task:vmware-vmx      state:D stack:0     pid:2712  ppid:1155   flags:0x00004002
Jun 08 15:49:53 Windows10 vmware[4440]: At least one instance of vmware-vmx is still running.
Jun 08 15:49:53 Windows10 vmware[4440]: Please stop all running instances of vmware-vmx first.
Jun 08 15:51:23 Windows10 systemd[1155]: app-gnome-vmware\x2dworkstation-2546.scope: Killing process 2712 (vmware-vmx) with signal SIGKILL.
Jun 08 15:51:53 Windows10 systemd[1]: user@1000.service: Killing process 2712 (vmware-vmx) with signal SIGKILL.
Jun 08 15:51:53 Windows10 systemd[1]: user@1000.service: Killing process 2712 (vmware-vmx) with signal SIGKILL.
Jun 08 15:53:53 Windows10 systemd[1]: user@1000.service: Unit process 2712 (vmware-vmx) remains running after unit stopped.

unubar · 2024-06-08 17:05:06

seth wrote:

There's a whole host of services not going down
systemctl --user mask xdg-document-portal.service

I get this message when I do that:
Failed to connect to bus: No medium found

seth wrote:

https://bbs.archlinux.org/viewtopic.php?id=296469

I tried to follow this thread but the issue on my machine is probably not the same as don't have tmux. Also, I have the NetworkManager issue that occurs when vmware is running (not immediately though).

seth wrote:

But there're obviously also (stale?) vmware related services - can you just log out (without even trying to shutdown)?
Can you shutdown/logout after first explicitly stopping vmware-vmx ?

Sometimes it works, sometimes it doesn't. Sometimes suspend/poweroff also works. A bit hard to know if the explicit stop helped because it might have shutdown successfully anyway.

seth · 2024-06-08 19:10:07

Failed to connect to bus: No medium found

Did you try to sudo the command??

systemctl --user status

The issue on my machine is probably not the same as don't have tmux

xdg-document-portal.service showed up there as well and was reported to lower the frequency of the problem, I just wanted to reference the pattern.

I have the NetworkManager issue that occurs when vmware is running (not immediately though).

NM not being able to decide on an AP is completely unrelated - did you try to lock in a BSSID?

A bit hard to know if the explicit stop helped because it might have shutdown successfully anyway.

You can only reject the theory, ie. iff the shutdown locks *despite* terminating the service ahead that would suggest that it is not the (only) culprit.

unubar · 2024-06-08 19:42:46

seth wrote:

Failed to connect to bus: No medium found
Did you try to sudo the command??
systemctl --user status

My bad. I was in sudo -i mode already. Ran it without sudo and got the following:

Created symlink /home/myuser/.config/systemd/user/xdg-document-portal.service → /dev/null.

seth wrote:

I have the NetworkManager issue that occurs when vmware is running (not immediately though).
NM not being able to decide on an AP is completely unrelated - did you try to lock in a BSSID?

The NM issue I am referencing is when NM was getting disabled, not the one switching between APs. Anyway, I have now connected to a different AP to see how that goes.

seth wrote:

A bit hard to know if the explicit stop helped because it might have shutdown successfully anyway.
You can only reject the theory, ie. iff the shutdown locks *despite* terminating the service ahead that would suggest that it is not the (only) culprit.

I will test a few more iterations and get back here.

unubar · 2024-06-08 22:30:41

So I started vmware, ran a windows vm for a little while and then closed the vm and exited vmware.

Tried to kill vmware-vmx but the terminal would hang when I tried to sudo. Closed terminal and tried again. Same.
At that point NM was also stalled.

As expected, poweroff did not complete.

Here is the log from journalctl -b -1:
http://0x0.st/XbO7.txt

Also, after bootup, systemctl status shows status as degraded. So I did a systemctl --failed and it shows that vmware-usbarbitrator.service failed.

unubar · 2024-06-09 04:10:53

Tried again and exited vmware after running a windows vm for a while.

This time sudo worked but kill did not work for vmware-vmx. Issued a normal kill and also kill -9 but vmware-vmx persists. poweroff hanged as expected.

Log from journalctl -b -1:
http://0x0.st/Xb41.txt

poweroff was issued at Jun 09 06:51:01

Here is the output of ps aux | grep vm:
http://0x0.st/Xb4N.txt

seth · 2024-06-09 15:50:47

Well, I guess we've our culprit, just not what gets vmware into an IO lock.
Things start here

Jun 09 05:49:17 Windows10 vmware-workstation.desktop[3626]: I/O warning : failed to load external entity "/etc/vmware/hostd/proxy.xml"
Jun 09 05:49:18 Windows10 gnome-shell[1321]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
Jun 09 05:49:18 Windows10 gnome-shell[1321]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
Jun 09 05:49:25 Windows10 gnome-character[3492]: JS LOG: Characters Application exiting
Jun 09 05:49:29 Windows10 kernel: /dev/vmmon[3725]: PTSC: initialized at 2712000000 Hz using TSC, TSCs are synchronized.
Jun 09 05:49:29 Windows10 kernel: /dev/vmmon[3725]: Monitor IPI vector: 0
Jun 09 05:49:29 Windows10 kernel: /dev/vmmon[3725]: HV      IPI vector: 0
Jun 09 05:49:29 Windows10 kernel: ------------[ cut here ]------------
Jun 09 05:49:29 Windows10 kernel: WARNING: CPU: 5 PID: 3725 at kernel/rcu/tree_plugin.h:734 rcu_sched_clock_irq+0xb3c/0x10f0
Jun 09 05:49:29 Windows10 kernel: Modules linked in: isofs cdrom rfcomm ccm vmnet(OE) ppdev parport_pc parport vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) cmac algif_hash algif_skcipher af_alg bnep joydev mousedev rmi_smbus rmi_core intel_rapl_msr intel_rapl_common intel_tcc_cooling x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass snd_soc_avs crct10dif_pclmul snd_soc_hda_codec snd_ctl_led crc32_pclmul snd_hda_ext_core polyval_clmulni snd_hda_codec_realtek polyval_generic gf128mul snd_soc_core snd_hda_codec_generic ghash_clmulni_intel iwlmvm snd_compress sha512_ssse3 snd_hda_codec_hdmi sha256_ssse3 ac97_bus snd_pcm_dmaengine sha1_ssse3 aesni_intel snd_hda_intel crypto_simd snd_intel_dspcfg pkcs8_key_parser cryptd snd_intel_sdw_acpi mac80211 snd_hda_codec uvcvideo btusb snd_hda_core rapl btrtl videobuf2_vmalloc mei_hdcp libarc4 uvc iTCO_wdt mei_pxp nvidia_drm(POE) vfat snd_hwdep btintel videobuf2_memops mei_wdt nvidia_uvm(POE) snd_pcm thinkpad_acpi intel_pmc_bxt btbcm think_lmi intel_cstate ledtrig_audio btmtk
Jun 09 05:49:29 Windows10 kernel:  nvidia_modeset(POE) ee1004 iwlwifi iTCO_vendor_support intel_wmi_thunderbolt fat wmi_bmof videobuf2_v4l2 firmware_attributes_class snd_timer platform_profile bluetooth videodev intel_uncore snd cfg80211 video pcspkr i2c_i801 videobuf2_common mei_me ecdh_generic e1000e psmouse i2c_smbus mc soundcore rfkill usbhid mei intel_pch_thermal wmi mac_hid nvidia(POE) sg crypto_user dm_mod loop fuse nfnetlink bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 uas usb_storage rtsx_pci_sdmmc serio_raw atkbd mmc_core libps2 vivaldi_fmap crc32c_intel rtsx_pci xhci_pci xhci_pci_renesas i8042 serio
Jun 09 05:49:29 Windows10 kernel: CPU: 5 PID: 3725 Comm: vmware-vmx Tainted: P           OE      6.6.32-1-lts #1 ee405f31cc2370c66e95bb51982e71a894d4c0fd
Jun 09 05:49:29 Windows10 kernel: Hardware name: LENOVO 20EN0036AD/20EN0036AD, BIOS N1EET91W (1.64 ) 05/12/2021
Jun 09 05:49:29 Windows10 kernel: RIP: 0010:rcu_sched_clock_irq+0xb3c/0x10f0
Jun 09 05:49:29 Windows10 kernel: Code: 60 04 00 00 85 c0 0f 84 e6 f5 ff ff e9 1b fd ff ff c6 87 61 04 00 00 01 e9 d5 f5 ff ff 4c 89 f7 e8 69 5d f3 ff e9 37 ff ff ff <0f> 0b e9 69 f5 ff ff be 03 00 00 00 4c 89 ef e8 40 1f 4d 00 e9 1e
Jun 09 05:49:29 Windows10 kernel: RSP: 0018:ffffae8440248de8 EFLAGS: 00010082
Jun 09 05:49:29 Windows10 kernel: RAX: ffff923eebb3da00 RBX: 0000000000000000 RCX: 000000001453733b
Jun 09 05:49:29 Windows10 kernel: RDX: 00000000ffffffa7 RSI: ffff923e86a7dd80 RDI: ffff923eebb3da00
Jun 09 05:49:29 Windows10 kernel: RBP: ffff924de3f62080 R08: 0000000000000000 R09: 0000000000000000
Jun 09 05:49:29 Windows10 kernel: R10: 0000000000000000 R11: ffffae8440248ff8 R12: ffff924de3f64b00
Jun 09 05:49:29 Windows10 kernel: R13: ffffae84444cb8c8 R14: ffff924de3f64b10 R15: ffff924de3f645c0
Jun 09 05:49:29 Windows10 kernel: FS:  000071e92e6c2c00(0000) GS:ffff924de3f40000(0000) knlGS:0000000000000000
Jun 09 05:49:29 Windows10 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 09 05:49:29 Windows10 kernel: CR2: 000071e92c049000 CR3: 00000001042be006 CR4: 00000000003706e0
Jun 09 05:49:29 Windows10 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jun 09 05:49:29 Windows10 kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Jun 09 05:49:29 Windows10 kernel: Call Trace:
Jun 09 05:49:29 Windows10 kernel:  <IRQ>
Jun 09 05:49:29 Windows10 kernel:  ? rcu_sched_clock_irq+0xb3c/0x10f0
Jun 09 05:49:29 Windows10 kernel:  ? __warn+0x81/0x130
Jun 09 05:49:29 Windows10 kernel:  ? rcu_sched_clock_irq+0xb3c/0x10f0
Jun 09 05:49:29 Windows10 kernel:  ? report_bug+0x16f/0x1a0
Jun 09 05:49:29 Windows10 kernel:  ? handle_bug+0x3c/0x80
Jun 09 05:49:29 Windows10 kernel:  ? exc_invalid_op+0x17/0x70
Jun 09 05:49:29 Windows10 kernel:  ? asm_exc_invalid_op+0x1a/0x20
Jun 09 05:49:29 Windows10 kernel:  ? rcu_sched_clock_irq+0xb3c/0x10f0
Jun 09 05:49:29 Windows10 kernel:  ? rcu_sched_clock_irq+0x4cb/0x10f0
Jun 09 05:49:29 Windows10 kernel:  ? timekeeping_update+0xe0/0x130
Jun 09 05:49:29 Windows10 kernel:  ? timekeeping_advance+0x378/0x5a0
Jun 09 05:49:29 Windows10 kernel:  update_process_times+0x74/0xb0
Jun 09 05:49:29 Windows10 kernel:  tick_sched_handle+0x21/0x60
Jun 09 05:49:29 Windows10 kernel:  tick_sched_timer+0x6f/0x90
Jun 09 05:49:29 Windows10 kernel:  ? __pfx_tick_sched_timer+0x10/0x10
Jun 09 05:49:29 Windows10 kernel:  __hrtimer_run_queues+0x12f/0x2a0
Jun 09 05:49:29 Windows10 kernel:  hrtimer_interrupt+0xf8/0x230
Jun 09 05:49:29 Windows10 kernel:  __sysvec_apic_timer_interrupt+0x4a/0x140
Jun 09 05:49:29 Windows10 kernel:  sysvec_apic_timer_interrupt+0x6d/0x90
Jun 09 05:49:29 Windows10 kernel:  </IRQ>
Jun 09 05:49:29 Windows10 kernel:  <TASK>
Jun 09 05:49:29 Windows10 kernel:  asm_sysvec_apic_timer_interrupt+0x1a/0x20
Jun 09 05:49:29 Windows10 kernel: RIP: 0010:xas_descend+0xd/0xa0
Jun 09 05:49:29 Windows10 kernel: Code: e8 20 48 89 57 08 c3 cc cc cc cc 66 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f b6 0e 48 8b 47 08 48 89 f2 48 d3 e8 <83> e0 3f 89 c1 48 83 c1 04 48 8b 74 ce 08 48 89 57 18 49 89 f0 48
Jun 09 05:49:29 Windows10 kernel: RSP: 0018:ffffae84444cb970 EFLAGS: 00000202
Jun 09 05:49:29 Windows10 kernel: RAX: 0000000000000001 RBX: ffff923ea3b03d9a RCX: 000000000000000c
Jun 09 05:49:29 Windows10 kernel: RDX: ffff923ea3b03d98 RSI: ffff923ea3b03d98 RDI: ffffae84444cb978
Jun 09 05:49:29 Windows10 kernel: RBP: ffffae84444cb978 R08: 000000000003a5c0 R09: 0000000000000013
Jun 09 05:49:29 Windows10 kernel: R10: 0000000000000001 R11: 0000000000000010 R12: 000000000000000c
Jun 09 05:49:29 Windows10 kernel: R13: ffffefdb8725db40 R14: 0000000000000140 R15: 000000000000146e
Jun 09 05:49:29 Windows10 kernel:  xa_load+0xc2/0xe0
Jun 09 05:49:29 Windows10 kernel:  page_cache_ra_unbounded+0xf5/0x180
Jun 09 05:49:29 Windows10 kernel:  filemap_get_pages+0x4ec/0x650
Jun 09 05:49:29 Windows10 kernel:  filemap_read+0xe3/0x350
Jun 09 05:49:29 Windows10 kernel:  vfs_read+0x1fe/0x340
Jun 09 05:49:29 Windows10 kernel:  ksys_read+0x6d/0xf0
Jun 09 05:49:29 Windows10 kernel:  do_syscall_64+0x5a/0x80
Jun 09 05:49:29 Windows10 kernel:  ? __mod_memcg_lruvec_state+0x4e/0xa0
Jun 09 05:49:29 Windows10 kernel:  ? __mod_lruvec_page_state+0x99/0x130
Jun 09 05:49:29 Windows10 kernel:  ? folio_add_new_anon_rmap+0x45/0xe0
Jun 09 05:49:29 Windows10 kernel:  ? set_ptes.isra.0+0x1e/0xa0
Jun 09 05:49:29 Windows10 kernel:  ? do_anonymous_page+0x2f2/0x3b0
Jun 09 05:49:29 Windows10 kernel:  ? __handle_mm_fault+0xb99/0xdd0
Jun 09 05:49:29 Windows10 kernel:  ? __count_memcg_events+0x42/0x90
Jun 09 05:49:29 Windows10 kernel:  ? count_memcg_events.constprop.0+0x1a/0x30
Jun 09 05:49:29 Windows10 kernel:  ? handle_mm_fault+0x1f2/0x350
Jun 09 05:49:29 Windows10 kernel:  ? do_user_addr_fault+0x20f/0x650
Jun 09 05:49:29 Windows10 kernel:  ? exc_page_fault+0x7f/0x180
Jun 09 05:49:29 Windows10 kernel:  entry_SYSCALL_64_after_hwframe+0x78/0xe2
Jun 09 05:49:29 Windows10 kernel: RIP: 0033:0x71e92e8049ba
Jun 09 05:49:29 Windows10 kernel: Code: 55 48 89 e5 48 83 ec 20 48 89 55 e8 48 89 75 f0 89 7d f8 e8 e8 63 f8 ff 48 8b 55 e8 48 8b 75 f0 41 89 c0 8b 7d f8 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 2e 44 89 c7 48 89 45 f8 e8 42 64 f8 ff 48 8b
Jun 09 05:49:29 Windows10 kernel: RSP: 002b:00007fff91f65770 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
Jun 09 05:49:29 Windows10 kernel: RAX: ffffffffffffffda RBX: 0000000000553f88 RCX: 000071e92e8049ba
Jun 09 05:49:29 Windows10 kernel: RDX: 0000000000553f88 RSI: 000071e92c042010 RDI: 0000000000000056
Jun 09 05:49:29 Windows10 kernel: RBP: 00007fff91f65790 R08: 0000000000000000 R09: 0000000000000000
Jun 09 05:49:29 Windows10 kernel: R10: 0000000000000022 R11: 0000000000000246 R12: 0000000000553f88
Jun 09 05:49:29 Windows10 kernel: R13: 0000000000000027 R14: 000071e92c042010 R15: 0000000000000001
Jun 09 05:49:29 Windows10 kernel:  </TASK>
Jun 09 05:49:29 Windows10 kernel: ---[ end trace 0000000000000000 ]---

Wild guess: you've zswap but no swap partition or file to back it - add a swap file and see whether vmware still loses it.

Edit: also the 550xx nvidia drivers are otr for corrupting the kernel memory, https://aur.archlinux.org/packages/nvidia-535xx-dkms and if you've not done that yet, https://wiki.archlinux.org/title/VMware … _hugepages

Last edited by seth (2024-06-09 15:55:09)

unubar · 2024-06-09 21:09:59

seth wrote:

Well, I guess we've our culprit, just not what gets vmware into an IO lock.
Things start here
Jun 09 05:49:17 Windows10 vmware-workstation.desktop[3626]: I/O warning : failed to load external entity "/etc/vmware/hostd/proxy.xml"

This doesn't even exist: "/etc/vmware/hostd/proxy.xml"

seth wrote:

Edit: also the 550xx nvidia drivers are otr for corrupting the kernel memory, https://aur.archlinux.org/packages/nvidia-535xx-dkms and if you've not done that yet, https://wiki.archlinux.org/title/VMware … _hugepages

This is for version 535. I have 550 installed so not sure what to do with this.

I uninstalled vmware completely, removed the vmware-usbarbitrator service and installed the latest 17.5.2 (I had 17.5.0). The vmware-usbarbitrator failed message is gone now. But starting vmware and then any vm still causes poweroff to hang.
This the last log:
https://0x0.st/Xb3X.txt

At this point, I am considering a fresh re-install of archlinux.

seth · 2024-06-09 21:15:23

The plan is to replace 550xx with 535xx to avoid the 550xx issues, https://bbs.archlinux.org/viewtopic.php?id=293400

At this point, I am considering a fresh re-install of archlinux.

Without vmware?

The journal is mostly baloo-spam, but vmx-vmem is still IO blocked - have you ever encountered this (and a journal of that boot) when *not* running vmware at all?

Edit: there's no swap device and it doesn't look like you disable THP either?

Last edited by seth (2024-06-09 21:17:29)

unubar · 2024-06-10 05:39:30

seth wrote:

The plan is to replace 550xx with 535xx to avoid the 550xx issues, https://bbs.archlinux.org/viewtopic.php?id=293400
At this point, I am considering a fresh re-install of archlinux.
Without vmware?

I am going to install nvidia 535xx next.

seth wrote:

The journal is mostly baloo-spam, but vmx-vmem is still IO blocked - have you ever encountered this (and a journal of that boot) when *not* running vmware at all?

I don't think vmx-vmem appears if I don't start vmware. I will get a journal of that next.

seth wrote:

Edit: there's no swap device and it doesn't look like you disable THP either?

Regarding THP, adding transparent_hugepage=never to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub followed by grub-mkconfig resulted in a grub.cfg that was not bootable. Thankfully, I had saved the previous grub.cfg and was able to restore it.

Next, I did the following:
echo never > /sys/kernel/mm/transparent_hugepage/enabled
and started vmware and exited. Still vmware-vmx shows as defunct and cannot be killed.

I'm sure the poweroff is going to hang now.

Below is the log for the current boot:
http://0x0.st/Xb6P.txt

seth · 2024-06-10 06:40:58

Regarding THP, adding transparent_hugepage=never to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub followed by grub-mkconfig resulted in a grub.cfg that was not bootable.

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
What did the etc/default/grub and the grub.cfg actually look like and how specifically was that "not bootable"?

I don't think vmx-vmem appears if I don't start vmware. I will get a journal of that next.

That's expectable, but what about the shutdown hangs? Gone w/o vmware, too?

unubar · 2024-06-10 09:17:50

seth wrote:

Regarding THP, adding transparent_hugepage=never to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub followed by grub-mkconfig resulted in a grub.cfg that was not bootable.
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
What did the etc/default/grub and the grub.cfg actually look like and how specifically was that "not bootable"?

I added transparent_hugepage=never to /etc/default/grub by updating this line:

GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet transparent_hugepage=never"

Then I ran:

grub-mkconfig -o /boot/grub/grub.cfg

The whole grub:

# GRUB boot loader configuration

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet transparent_hugepage=never"
GRUB_CMDLINE_LINUX=""

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y

# Set to 'countdown' or 'hidden' to change timeout behavior,
# press ESC key to display menu.
GRUB_TIMEOUT_STYLE=menu

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `videoinfo'
GRUB_GFXMODE=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper
# modes only.  Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
#GRUB_THEME="/path/to/gfxtheme"

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

# Uncomment to make GRUB remember the last selection. This requires
# setting 'GRUB_DEFAULT=saved' above.
#GRUB_SAVEDEFAULT=true

# Uncomment to disable submenus in boot menu
#GRUB_DISABLE_SUBMENU=y

# Probing for other operating systems is disabled for security reasons. Read
# documentation on GRUB_DISABLE_OS_PROBER, if still want to enable this
# functionality install os-prober and uncomment to detect and include other
# operating systems.
#GRUB_DISABLE_OS_PROBER=false

The resulting grub.cfg:

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  14b87552-dfe3-4b02-92cf-7f5208f05197
else
  search --no-floppy --fs-uuid --set=root 14b87552-dfe3-4b02-92cf-7f5208f05197
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_input console
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
  set timeout_style=menu
  set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
  set timeout=5
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-14b87552-dfe3-4b02-92cf-7f5208f05197' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_gpt
	insmod fat
	set root='hd0,gpt1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1  AB8C-B6B0
	else
	  search --no-floppy --fs-uuid --set=root AB8C-B6B0
	fi
	echo	'Loading Linux linux-lts ...'
	linux	/vmlinuz-linux-lts root=UUID=14b87552-dfe3-4b02-92cf-7f5208f05197 rw  loglevel=3 quiet transparent_hugepage=never
	echo	'Loading initial ramdisk ...'
	initrd	/intel-ucode.img /initramfs-linux-lts.img
}
submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-14b87552-dfe3-4b02-92cf-7f5208f05197' {
	menuentry 'Arch Linux, with Linux linux-lts' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-lts-advanced-14b87552-dfe3-4b02-92cf-7f5208f05197' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod fat
		set root='hd0,gpt1'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1  AB8C-B6B0
		else
		  search --no-floppy --fs-uuid --set=root AB8C-B6B0
		fi
		echo	'Loading Linux linux-lts ...'
		linux	/vmlinuz-linux-lts root=UUID=14b87552-dfe3-4b02-92cf-7f5208f05197 rw  loglevel=3 quiet transparent_hugepage=never
		echo	'Loading initial ramdisk ...'
		initrd	/intel-ucode.img /initramfs-linux-lts.img
	}
	menuentry 'Arch Linux, with Linux linux-lts (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-lts-fallback-14b87552-dfe3-4b02-92cf-7f5208f05197' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod fat
		set root='hd0,gpt1'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1  AB8C-B6B0
		else
		  search --no-floppy --fs-uuid --set=root AB8C-B6B0
		fi
		echo	'Loading Linux linux-lts ...'
		linux	/vmlinuz-linux-lts root=UUID=14b87552-dfe3-4b02-92cf-7f5208f05197 rw  loglevel=3 quiet transparent_hugepage=never
		echo	'Loading initial ramdisk ...'
		initrd	/intel-ucode.img /initramfs-linux-lts-fallback.img
	}
	menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-14b87552-dfe3-4b02-92cf-7f5208f05197' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod fat
		set root='hd0,gpt1'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1  AB8C-B6B0
		else
		  search --no-floppy --fs-uuid --set=root AB8C-B6B0
		fi
		echo	'Loading Linux linux ...'
		linux	/vmlinuz-linux root=UUID=14b87552-dfe3-4b02-92cf-7f5208f05197 rw  loglevel=3 quiet transparent_hugepage=never
		echo	'Loading initial ramdisk ...'
		initrd	/intel-ucode.img /initramfs-linux.img
	}
	menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-14b87552-dfe3-4b02-92cf-7f5208f05197' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod fat
		set root='hd0,gpt1'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1  AB8C-B6B0
		else
		  search --no-floppy --fs-uuid --set=root AB8C-B6B0
		fi
		echo	'Loading Linux linux ...'
		linux	/vmlinuz-linux root=UUID=14b87552-dfe3-4b02-92cf-7f5208f05197 rw  loglevel=3 quiet transparent_hugepage=never
		echo	'Loading initial ramdisk ...'
		initrd	/intel-ucode.img /initramfs-linux-fallback.img
	}
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/15_ostree ###
### END /etc/grub.d/15_ostree ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/25_bli ###
if [ "$grub_platform" = "efi" ]; then
  insmod bli
fi
### END /etc/grub.d/25_bli ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
if [ "$grub_platform" = "efi" ]; then
	fwsetup --is-supported
	if [ "$?" = 0 ]; then
		menuentry 'UEFI Firmware Settings' $menuentry_id_option 'uefi-firmware' {
			fwsetup
		}
	fi
fi
### END /etc/grub.d/30_uefi-firmware ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg
fi
### END /etc/grub.d/41_custom ###

The previous grub.cfg that I reverted back to:

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  14b87552-dfe3-4b02-92cf-7f5208f05197
else
  search --no-floppy --fs-uuid --set=root 14b87552-dfe3-4b02-92cf-7f5208f05197
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_input console
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
  set timeout_style=menu
  set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
  set timeout=5
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-14b87552-dfe3-4b02-92cf-7f5208f05197' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_gpt
	insmod fat
	set root='hd0,gpt1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1  AB8C-B6B0
	else
	  search --no-floppy --fs-uuid --set=root AB8C-B6B0
	fi
	echo	'Loading Linux linux-lts ...'
	linux	/vmlinuz-linux-lts root=UUID=14b87552-dfe3-4b02-92cf-7f5208f05197 rw  loglevel=3 quiet
	echo	'Loading initial ramdisk ...'
	initrd	/intel-ucode.img /initramfs-linux-lts.img
}
submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-14b87552-dfe3-4b02-92cf-7f5208f05197' {
	menuentry 'Arch Linux, with Linux linux-lts' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-lts-advanced-14b87552-dfe3-4b02-92cf-7f5208f05197' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod fat
		set root='hd0,gpt1'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1  AB8C-B6B0
		else
		  search --no-floppy --fs-uuid --set=root AB8C-B6B0
		fi
		echo	'Loading Linux linux-lts ...'
		linux	/vmlinuz-linux-lts root=UUID=14b87552-dfe3-4b02-92cf-7f5208f05197 rw  loglevel=3 quiet
		echo	'Loading initial ramdisk ...'
		initrd	/intel-ucode.img /initramfs-linux-lts.img
	}
	menuentry 'Arch Linux, with Linux linux-lts (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-lts-fallback-14b87552-dfe3-4b02-92cf-7f5208f05197' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod fat
		set root='hd0,gpt1'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1  AB8C-B6B0
		else
		  search --no-floppy --fs-uuid --set=root AB8C-B6B0
		fi
		echo	'Loading Linux linux-lts ...'
		linux	/vmlinuz-linux-lts root=UUID=14b87552-dfe3-4b02-92cf-7f5208f05197 rw  loglevel=3 quiet
		echo	'Loading initial ramdisk ...'
		initrd	/intel-ucode.img /initramfs-linux-lts-fallback.img
	}
	menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-14b87552-dfe3-4b02-92cf-7f5208f05197' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod fat
		set root='hd0,gpt1'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1  AB8C-B6B0
		else
		  search --no-floppy --fs-uuid --set=root AB8C-B6B0
		fi
		echo	'Loading Linux linux ...'
		linux	/vmlinuz-linux root=UUID=14b87552-dfe3-4b02-92cf-7f5208f05197 rw  loglevel=3 quiet
		echo	'Loading initial ramdisk ...'
		initrd	/intel-ucode.img /initramfs-linux.img
	}
	menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-14b87552-dfe3-4b02-92cf-7f5208f05197' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod fat
		set root='hd0,gpt1'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1  AB8C-B6B0
		else
		  search --no-floppy --fs-uuid --set=root AB8C-B6B0
		fi
		echo	'Loading Linux linux ...'
		linux	/vmlinuz-linux root=UUID=14b87552-dfe3-4b02-92cf-7f5208f05197 rw  loglevel=3 quiet
		echo	'Loading initial ramdisk ...'
		initrd	/intel-ucode.img /initramfs-linux-fallback.img
	}
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
menuentry 'UEFI Firmware Settings' $menuentry_id_option 'uefi-firmware' {
	fwsetup
}
### END /etc/grub.d/30_uefi-firmware ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg
fi
### END /etc/grub.d/41_custom ###

seth wrote:

I don't think vmx-vmem appears if I don't start vmware. I will get a journal of that next.
That's expectable, but what about the shutdown hangs? Gone w/o vmware, too?

The shutdown hangs don't happen if I don't start vmware. I can safely say at this point that poweroff hangs only when vmware-vmx is in a defunct state.
Once I run vmware and start a vm, then after exiting vmware, poweroff doesn't complete.

Log from last boot where I did not run vmware:
http://0x0.st/XbUF.txt

unubar · 2024-06-10 09:36:49

seth wrote:

Edit: also the 550xx nvidia drivers are otr for corrupting the kernel memory, https://aur.archlinux.org/packages/nvidia-535xx-dkms and if you've not done that yet, https://wiki.archlinux.org/title/VMware … _hugepages

I have not installed aur packages before. Should I follow the steps in the following page to install nvidia-535xx?
https://gewhere.github.io/install-aur-with-pacman

unubar · 2024-06-10 10:22:53

unubar wrote:

seth wrote:
Edit: also the 550xx nvidia drivers are otr for corrupting the kernel memory, https://aur.archlinux.org/packages/nvidia-535xx-dkms and if you've not done that yet, https://wiki.archlinux.org/title/VMware … _hugepages
I have not installed aur packages before. Should I follow the steps in the following page to install nvidia-535xx?
https://gewhere.github.io/install-aur-with-pacman

I guess I should just download 535.183.01 from nvidia.com

unubar · 2024-06-10 11:09:17

unubar wrote:

unubar wrote:
seth wrote:
Edit: also the 550xx nvidia drivers are otr for corrupting the kernel memory, https://aur.archlinux.org/packages/nvidia-535xx-dkms and if you've not done that yet, https://wiki.archlinux.org/title/VMware … _hugepages
I have not installed aur packages before. Should I follow the steps in the following page to install nvidia-535xx?
https://gewhere.github.io/install-aur-with-pacman
I guess I should just download 535.183.01 from nvidia.com

That didn't go too well. Contents of '/var/log/nvidia-installer.log' :
https://0x0.st/Xb00.txt

How do I unload 'nvidia-drm' now?
This seems related: https://bbs.archlinux.org/viewtopic.php?id=290961
But I am not clear how to proceed now.

seth · 2024-06-10 13:46:17

Please don't bump - edit your previous post if nobody has responded yet.
We'll come back to how that "did not boot" later.

https://gewhere.github.io/install-aur-with-pacman … That didn't go too well.

PSA: Don't follow random tutorials, https://wiki.archlinux.org/title/Arch_User_Repository & https://wiki.archlinux.org/title/Dynami … le_Support

I guess I should just download 535.183.01 from nvidia.com

Very bad idea, stop that.

pacman -Q linux-lts-headers # you need the header packages for all kernels you inted to use,
# they have to match the booting kernel, ie. eg. linux-lts-headers 6.6.32 with linux-lts 6.6.31 will not work
git clone https://aur.archlinux.org/nvidia-535xx-utils.git
cd nvidia-535xx-utils
makepkg -i

unubar · 2024-06-11 07:49:40

seth wrote:

pacman -Q linux-lts-headers # you need the header packages for all kernels you inted to use,
# they have to match the booting kernel, ie. eg. linux-lts-headers 6.6.32 with linux-lts 6.6.31 will not work
git clone https://aur.archlinux.org/nvidia-535xx-utils.git
cd nvidia-535xx-utils
makepkg -i

Followed above steps. Still same issue. Starting vmware and a vm causes poweroff hang.

Log from last boot:
http://0x0.st/Xcsl.txt

# pacman -Q | grep nvid
nvidia-535xx-dkms 535.183.01-1
nvidia-535xx-utils 535.183.01-1
nvidia-settings 550.78-1
opencl-nvidia-535xx 535.183.01-1

seth · 2024-06-11 16:55:24

You could attach strace to vmware-vmx (before it goess dormant! in doubt change the service to strace the process) so we can maybe see what device the process is waiting for: https://man.archlinux.org/man/extra/str … .en#attach
But I assume it's related to the resp. kernel module.

Same issue w/ onle of the older LTS kernels (5.15, 5.4 or 4.19)?
https://aur.archlinux.org/packages?O=0&K=linux-lts

Arch Linux

#1 2024-06-08 05:56:21

NetworkManager and Suspend/poweroff issues

#2 2024-06-08 07:52:23

Re: NetworkManager and Suspend/poweroff issues

#3 2024-06-08 08:37:53

Re: NetworkManager and Suspend/poweroff issues

#4 2024-06-08 12:10:28

Re: NetworkManager and Suspend/poweroff issues

#5 2024-06-08 15:07:15

Re: NetworkManager and Suspend/poweroff issues

#6 2024-06-08 15:29:39

Re: NetworkManager and Suspend/poweroff issues

#7 2024-06-08 17:05:06

Re: NetworkManager and Suspend/poweroff issues

#8 2024-06-08 19:10:07

Re: NetworkManager and Suspend/poweroff issues

#9 2024-06-08 19:42:46

Re: NetworkManager and Suspend/poweroff issues

#10 2024-06-08 22:30:41

Re: NetworkManager and Suspend/poweroff issues

#11 2024-06-09 04:10:53

Re: NetworkManager and Suspend/poweroff issues

#12 2024-06-09 15:50:47

Re: NetworkManager and Suspend/poweroff issues

#13 2024-06-09 21:09:59

Re: NetworkManager and Suspend/poweroff issues

#14 2024-06-09 21:15:23

Re: NetworkManager and Suspend/poweroff issues

#15 2024-06-10 05:39:30

Re: NetworkManager and Suspend/poweroff issues

#16 2024-06-10 06:40:58

Re: NetworkManager and Suspend/poweroff issues

#17 2024-06-10 09:17:50

Re: NetworkManager and Suspend/poweroff issues

#18 2024-06-10 09:36:49

Re: NetworkManager and Suspend/poweroff issues

#19 2024-06-10 10:22:53

Re: NetworkManager and Suspend/poweroff issues

#20 2024-06-10 11:09:17

Re: NetworkManager and Suspend/poweroff issues

#21 2024-06-10 13:46:17

Re: NetworkManager and Suspend/poweroff issues

#22 2024-06-11 07:49:40

Re: NetworkManager and Suspend/poweroff issues

#23 2024-06-11 16:55:24

Re: NetworkManager and Suspend/poweroff issues

Board footer