You are not logged in.

Pages: 1

#1 2023-12-07 03:39:30

rschristian
Member
Registered: 2021-03-11
Posts: 7

[SOLVED] How to debug input lock-out seeming caused by GPU use?

As of 2-3 months ago, I started to notice an occasional issue when moving floating windows in i3 -- essentially, my Arch guest (ran in vmware) would lock out input. The UI would still react, so if I was watching a video or running `top` I could still see updates just fine. This was a very occasional issue, so I didn't give it much thought. I'd shut down the guest, restart, and have no issues for a week.

As of last week, I started to notice extreme lag when creating new windows (say new terminal sessions or opening my browser), with this taking 3-4x longer than it had in the past, and guaranteed locking if I moved floating windows more than a little bit. These, combined with some CLI commands seeing increased runtime (`inxi -Gxx` takes 5-6 seconds) makes me (perhaps ignorantly) guess this is a GPU/driver-driven issue? I appreciate GPUs and virtualization are probably a bad surface area to try to deal with.

For the past 3-4 days I've been scrolling various logs but haven't seen anything stand out, but then again, I'm not 100% on what I'm looking for. I've played around with sysrq but even it isn't able to get through this lockout. Does anyone happen to have any pointers as to what I need to be looking through? Here is the results of `inxi -Gxx`, if it's useful:

Graphics:
  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.20.0.0 ports:
    active: Virtual-1 empty: Virtual-2, Virtual-3, Virtual-4, Virtual-5,
    Virtual-6, Virtual-7, Virtual-8 bus-ID: 00:0f.0 chip-ID: 15ad:0405
  Display: x11 server: X.Org v: 21.1.9 driver: X: loaded: vmware
    unloaded: modesetting alternate: fbdev,vesa dri: vmwgfx gpu: vmwgfx
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3440x1440 s-dpi: 96
  Monitor-1: Virtual-1 mapped: Virtual1 res: 3440x1440 size: N/A
  API: EGL v: 1.5 platforms: device: 0 egl: 1.4 drv: vmwgfx device: 1
    drv: swrast gbm: egl: 1.4 drv: vmwgfx surfaceless: egl: 1.4 drv: vmwgfx x11:
    egl: 1.4 drv: vmwgfx inactive: wayland
  API: OpenGL v: 4.5 compat-v: 4.1 vendor: vmware mesa v: 23.2.1-arch1.2
    glx-v: 1.4 direct-render: yes renderer: SVGA3D; build: RELEASE; LLVM;
    device-ID: 15ad:040

Per the forum rules, I am running the latest of all my packages and I've also tested downgrading to the oldest cached versions (including Linux kernel) to no avail (actually with some adverse affects, as there seem to have been some pesky vmware issues in recent-ish kernel versions).

Last edited by rschristian (2023-12-18 06:37:41)

Offline

#2 2023-12-07 08:51:22

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,334

Re: [SOLVED] How to debug input lock-out seeming caused by GPU use?

Please use [code][/code] tags. Edit your post in this regard.
The BBS predates markdown by decades.

"locked input" could either be a grab or, showed up in a recent thread, the i3 process being stopped.
When it locks, move to a different TTY

export DISPLAY=:0
ps aux | grep i3
xdotool key "XF86LogGrabInfo"

The latter will print all grabs into your xorg log, the interesting being the active one(s)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2023-12-08 19:27:52

rschristian
Member
Registered: 2021-03-11
Posts: 7

Re: [SOLVED] How to debug input lock-out seeming caused by GPU use?

seth wrote:

Please use  tags. Edit your post in this regard.

Sorry, blanked on this. Thanks for correcting me.

seth wrote:

When it locks, move to a different TTY

This was a bit fiddly, but got there in the end. Unfortunately I couldn't switch TTY after the lock-up occurred, and even setting up the switch programmatically with a `sleep` didn't work as input still wouldn't be accepted, so I ended up doing this:

(sleep 10; xdotool "XF86LogGrabInfo"; cp /var/log/Xorg.0.log ./) &

Had to reboot to gain access again, but once I did, I could get at the logs.

Here's the active grabs, indeed, looks like it might be i3?

[   279.322] (II) Printing all currently active device grabs:
[   279.322] Active grab 0x400000 (core) on device 'Virtual core pointer' (2):
[   279.322]       client pid 703 i3 
[   279.322]       at 272008 (from active grab) (device thawed, state 1)
[   279.322]         core event mask 0x48
[   279.322]       owner-events false, kb 1 ptr 1, confine 0, cursor 0x400023
[   279.323] Active grab 0x400000 (core) on device 'Virtual core keyboard' (3):
[   279.323]       client pid 703 i3 
[   279.323]       at 272008 (from active grab) (device thawed, state 1)
[   279.323]         core event mask 0x3
[   279.323]       owner-events false, kb 1 ptr 1, confine 0, cursor 0x0
[   279.323] (II) End list of active device grabs

Offline

#4 2023-12-08 20:19:57

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,334

Re: [SOLVED] How to debug input lock-out seeming caused by GPU use?

Looks like, you could confirm that by checking pid 703 in the process table.

However

Unfortunately I couldn't switch TTY after the lock-up occurred

i3 might be a victim here that gets trapped in the grab because wider input processing has stalled.

Are there any relevant errors in the xorg log leading up to the stale grab?
Can you ssh into the system?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2023-12-09 00:33:34

rschristian
Member
Registered: 2021-03-11
Posts: 7

Re: [SOLVED] How to debug input lock-out seeming caused by GPU use?

seth wrote:

Looks like, you could confirm that by checking pid 703 in the process table.

Sorry, what would I be looking for? Using `ps aux` shows no change after lock-up; i3 has same mem/cpu usage, same status. Am I looking in the wrong place, or does that indicate i3 isn't the problem here?

seth wrote:

Are there any relevant errors in the xorg log leading up to the stale grab?

Nothing, it's just startup stuff followed immediately by the active grabs (prompted by that command above).

As for ssh'ing, perhaps. Need to figure out how but seems possible

Offline

#6 2023-12-09 08:05:33

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,334

Re: [SOLVED] How to debug input lock-out seeming caused by GPU use?

Sorry, what would I be looking for?
pid and state of the i3 process

ps aux | grep i3

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General
https://wiki.archlinux.org/title/Openssh

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#7 2023-12-09 08:33:21

rschristian
Member
Registered: 2021-03-11
Posts: 7

Re: [SOLVED] How to debug input lock-out seeming caused by GPU use?

pid and state of the i3 process

Oh, well as I mentioned, there's 0 change in the before/after there, hence why I thought you might be referring to something else:

ryan         725  0.1  0.1 170904 14940 ?        Ss   02:06   0:00 i3

Please post your Xorg log

Sure thing:

[     6.016] 
X.Org X Server 1.21.1.9
X Protocol Version 11, Revision 0
[     6.016] Current Operating System: Linux ryan-vm 6.4.12-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 24 Aug 2023 00:38:14 +0000 x86_64
[     6.016] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=d74a4203-f029-45bf-9ebc-44e9b183dc4a rw nowatchdog nvme_load=YES loglevel=3
[     6.016]  
[     6.016] Current version of pixman: 0.42.2
[     6.016] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[     6.016] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[     6.016] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Dec  9 02:17:40 2023
[     6.018] (==) Using config directory: "/etc/X11/xorg.conf.d"
[     6.018] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[     6.019] (==) No Layout section.  Using the first Screen section.
[     6.019] (==) No screen section available. Using defaults.
[     6.019] (**) |-->Screen "Default Screen Section" (0)
[     6.019] (**) |   |-->Monitor "<default monitor>"
[     6.020] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[     6.020] (==) Automatically adding devices
[     6.020] (==) Automatically enabling devices
[     6.020] (==) Automatically adding GPU devices
[     6.020] (==) Automatically binding GPU devices
[     6.020] (==) Max clients allowed: 256, resource mask: 0x1fffff
[     6.020] (WW) The directory "/usr/share/fonts/misc" does not exist.
[     6.020] 	Entry deleted from font path.
[     6.020] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/TTF".
[     6.020] 	Entry deleted from font path.
[     6.020] 	(Run 'mkfontdir' on "/usr/share/fonts/TTF").
[     6.020] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[     6.020] 	Entry deleted from font path.
[     6.020] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[     6.020] 	Entry deleted from font path.
[     6.020] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[     6.020] 	Entry deleted from font path.
[     6.020] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[     6.020] 	Entry deleted from font path.
[     6.020] (==) FontPath set to:
	
[     6.020] (==) ModulePath set to "/usr/lib/xorg/modules"
[     6.020] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[     6.020] (II) Module ABI versions:
[     6.020] 	X.Org ANSI C Emulation: 0.4
[     6.020] 	X.Org Video Driver: 25.2
[     6.020] 	X.Org XInput driver : 24.4
[     6.020] 	X.Org Server Extension : 10.0
[     6.021] (++) using VT number 7

[     6.021] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[     6.022] (II) xfree86: Adding drm device (/dev/dri/card0)
[     6.022] (II) Platform probe for /sys/devices/pci0000:00/0000:00:0f.0/drm/card0
[     6.032] (--) PCI:*(0@0:15:0) 15ad:0405:15ad:0405 rev 0, Mem @ 0xe8000000/134217728, 0xfe000000/8388608, I/O @ 0x00001070/16, BIOS @ 0x????????/131072
[     6.032] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[     6.032] (II) LoadModule: "glx"
[     6.032] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[     6.042] (II) Module glx: vendor="X.Org Foundation"
[     6.042] 	compiled for 1.21.1.9, module version = 1.0.0
[     6.042] 	ABI class: X.Org Server Extension, version 10.0
[     6.042] (==) Matched vmware as autoconfigured driver 0
[     6.042] (==) Matched modesetting as autoconfigured driver 1
[     6.042] (==) Matched fbdev as autoconfigured driver 2
[     6.042] (==) Matched vesa as autoconfigured driver 3
[     6.042] (==) Assigned the driver to the xf86ConfigLayout
[     6.042] (II) LoadModule: "vmware"
[     6.042] (II) Loading /usr/lib/xorg/modules/drivers/vmware_drv.so
[     6.287] (II) Module vmware: vendor="X.Org Foundation"
[     6.287] 	compiled for 1.21.1.6, module version = 13.4.0
[     6.287] 	Module class: X.Org Video Driver
[     6.287] 	ABI class: X.Org Video Driver, version 25.2
[     6.287] (II) LoadModule: "modesetting"
[     6.287] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[     6.290] (II) Module modesetting: vendor="X.Org Foundation"
[     6.290] 	compiled for 1.21.1.9, module version = 1.21.1
[     6.290] 	Module class: X.Org Video Driver
[     6.290] 	ABI class: X.Org Video Driver, version 25.2
[     6.290] (II) LoadModule: "fbdev"
[     6.290] (WW) Warning, couldn't open module fbdev
[     6.290] (EE) Failed to load module "fbdev" (module does not exist, 0)
[     6.290] (II) LoadModule: "vesa"
[     6.290] (WW) Warning, couldn't open module vesa
[     6.290] (EE) Failed to load module "vesa" (module does not exist, 0)
[     6.290] (II) vmware: driver for VMware SVGA: vmware0405, vmware0710
[     6.290] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[     6.292] (WW) Falling back to old probe method for modesetting
[     6.292] (II) vmware(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[     6.292] (--) vmware(0): DRM driver version is 2.20.0
[     6.292] (==) vmware(0): Depth 24, (--) framebuffer bpp 32
[     6.292] (==) vmware(0): RGB weight 888
[     6.292] (==) vmware(0): Default visual is TrueColor
[     6.292] (--) vmware(0): Min width 1, Max Width 16384.
[     6.292] (--) vmware(0): Min height 1, Max Height 16384.
[     6.292] (II) vmware(0): Output Virtual1 using monitor section Virtual1
[     6.292] (**) vmware(0): Option "PreferredMode" "3440x1440_60.00"
[     6.292] (II) vmware(0): Output Virtual2 has no monitor section
[     6.292] (II) vmware(0): Output Virtual3 has no monitor section
[     6.292] (II) vmware(0): Output Virtual4 has no monitor section
[     6.292] (II) vmware(0): Output Virtual5 has no monitor section
[     6.292] (II) vmware(0): Output Virtual6 has no monitor section
[     6.292] (II) vmware(0): Output Virtual7 has no monitor section
[     6.292] (II) vmware(0): Output Virtual8 has no monitor section
[     6.292] (II) vmware(0): Printing probed modes for output Virtual1
[     6.292] (II) vmware(0): Modeline "3440x1440_60.00"x59.9  419.50  3440 3696 4064 4688  1440 1443 1453 1493 -hsync +vsync (89.5 kHz UP)
[     6.292] (II) vmware(0): Modeline "1280x800"x60.0   81.51  1280 1330 1380 1430  800 850 900 950 -hsync +vsync (57.0 kHz eP)
[     6.292] (II) vmware(0): Modeline "3840x2400"x60.0  592.25  3840 3888 3920 4000  2400 2403 2409 2469 +hsync -vsync (148.1 kHz e)
[     6.292] (II) vmware(0): Modeline "3840x2160"x60.0  533.00  3840 3888 3920 4000  2160 2163 2168 2222 +hsync -vsync (133.2 kHz e)
[     6.292] (II) vmware(0): Modeline "2880x1800"x59.9  337.50  2880 2928 2960 3040  1800 1803 1809 1852 +hsync -vsync (111.0 kHz e)
[     6.292] (II) vmware(0): Modeline "2560x1600"x60.0  348.50  2560 2752 3032 3504  1600 1603 1609 1658 -hsync +vsync (99.5 kHz e)
[     6.292] (II) vmware(0): Modeline "2560x1440"x60.0  241.50  2560 2608 2640 2720  1440 1443 1448 1481 +hsync -vsync (88.8 kHz e)
[     6.292] (II) vmware(0): Modeline "1920x1440"x60.0  234.00  1920 2048 2256 2600  1440 1441 1444 1500 -hsync +vsync (90.0 kHz e)
[     6.292] (II) vmware(0): Modeline "1856x1392"x60.0  218.25  1856 1952 2176 2528  1392 1393 1396 1439 -hsync +vsync (86.3 kHz e)
[     6.292] (II) vmware(0): Modeline "1792x1344"x60.0  204.75  1792 1920 2120 2448  1344 1345 1348 1394 -hsync +vsync (83.6 kHz e)
[     6.292] (II) vmware(0): Modeline "1920x1200"x59.9  193.25  1920 2056 2256 2592  1200 1203 1209 1245 -hsync +vsync (74.6 kHz e)
[     6.292] (II) vmware(0): Modeline "1920x1080"x60.0  173.00  1920 2048 2248 2576  1080 1083 1088 1120 -hsync +vsync (67.2 kHz e)
[     6.292] (II) vmware(0): Modeline "1600x1200"x60.0  162.00  1600 1664 1856 2160  1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[     6.292] (II) vmware(0): Modeline "1680x1050"x60.0  146.25  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
[     6.292] (II) vmware(0): Modeline "1400x1050"x60.0  121.75  1400 1488 1632 1864  1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
[     6.292] (II) vmware(0): Modeline "1280x1024"x60.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[     6.292] (II) vmware(0): Modeline "1440x900"x59.9  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz e)
[     6.292] (II) vmware(0): Modeline "1280x960"x60.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
[     6.292] (II) vmware(0): Modeline "1360x768"x60.0   85.50  1360 1424 1536 1792  768 771 777 795 +hsync +vsync (47.7 kHz e)
[     6.292] (II) vmware(0): Modeline "1280x800"x59.8   83.50  1280 1352 1480 1680  800 803 809 831 +hsync -vsync (49.7 kHz e)
[     6.292] (II) vmware(0): Modeline "1152x864"x75.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[     6.292] (II) vmware(0): Modeline "1280x768"x59.9   79.50  1280 1344 1472 1664  768 771 778 798 -hsync +vsync (47.8 kHz e)
[     6.292] (II) vmware(0): Modeline "1280x720"x59.9   74.50  1280 1344 1472 1664  720 723 728 748 -hsync +vsync (44.8 kHz e)
[     6.292] (II) vmware(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[     6.292] (II) vmware(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[     6.292] (II) vmware(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 489 492 525 -hsync -vsync (31.5 kHz e)
[     6.292] (II) vmware(0): EDID for output Virtual2
[     6.292] (II) vmware(0): EDID for output Virtual3
[     6.292] (II) vmware(0): EDID for output Virtual4
[     6.292] (II) vmware(0): EDID for output Virtual5
[     6.292] (II) vmware(0): EDID for output Virtual6
[     6.293] (II) vmware(0): EDID for output Virtual7
[     6.293] (II) vmware(0): EDID for output Virtual8
[     6.293] (II) vmware(0): Output Virtual1 connected
[     6.293] (II) vmware(0): Output Virtual2 disconnected
[     6.293] (II) vmware(0): Output Virtual3 disconnected
[     6.293] (II) vmware(0): Output Virtual4 disconnected
[     6.293] (II) vmware(0): Output Virtual5 disconnected
[     6.293] (II) vmware(0): Output Virtual6 disconnected
[     6.293] (II) vmware(0): Output Virtual7 disconnected
[     6.293] (II) vmware(0): Output Virtual8 disconnected
[     6.293] (II) vmware(0): Using user preference for initial modes
[     6.293] (II) vmware(0): Output Virtual1 using initial mode 3440x1440_60.00 +0+0
[     6.293] (==) vmware(0): DPI set to (96, 96)
[     6.293] (==) vmware(0): Using gamma correction (1.0, 1.0, 1.0)
[     6.293] (II) Loading sub module "fb"
[     6.293] (II) LoadModule: "fb"
[     6.293] (II) Module "fb" already built-in
[     6.293] (II) Loading sub module "dri2"
[     6.293] (II) LoadModule: "dri2"
[     6.293] (II) Module "dri2" already built-in
[     6.293] (II) Loading sub module "dri3"
[     6.293] (II) LoadModule: "dri3"
[     6.293] (II) Module "dri3" already built-in
[     6.293] (II) UnloadModule: "modesetting"
[     6.293] (II) Unloading modesetting
[     6.294] (II) vmware(0): Initialized VMWARE_CTRL extension version 0.2
[     6.326] (II) vmware(0): Gallium3D XA version: 2.5.0.
[     6.326] (II) vmware(0): Path of drm device is "/dev/dri/card0".
[     6.326] (II) vmware(0): [DRI2] Setup complete
[     6.326] (II) vmware(0): [DRI2]   DRI driver: vmwgfx
[     7.890] (--) vmware(0): Render acceleration is enabled.
[     7.890] (==) vmware(0): Rendercheck mode is disabled.
[     7.890] (--) vmware(0): Direct rendering (DRI2 3D) is enabled.
[     7.890] (--) vmware(0): Direct rendering (DRI3 3D) is enabled.
[     7.890] (==) vmware(0): Direct presents are disabled.
[     7.890] (==) vmware(0): Hardware only presents are automatic per scanout.
[     7.890] (==) vmware(0): Backing store enabled
[     7.890] (==) vmware(0): Silken mouse enabled
[     7.891] (==) vmware(0): DPMS enabled
[     7.891] (II) Initializing extension Generic Event Extension
[     7.891] (II) Initializing extension SHAPE
[     7.891] (II) Initializing extension MIT-SHM
[     7.891] (II) Initializing extension XInputExtension
[     7.891] (II) Initializing extension XTEST
[     7.891] (II) Initializing extension BIG-REQUESTS
[     7.891] (II) Initializing extension SYNC
[     7.891] (II) Initializing extension XKEYBOARD
[     7.891] (II) Initializing extension XC-MISC
[     7.891] (II) Initializing extension SECURITY
[     7.892] (II) Initializing extension XFIXES
[     7.892] (II) Initializing extension RENDER
[     7.892] (II) Initializing extension RANDR
[     7.892] (II) Initializing extension COMPOSITE
[     7.892] (II) Initializing extension DAMAGE
[     7.892] (II) Initializing extension MIT-SCREEN-SAVER
[     7.892] (II) Initializing extension DOUBLE-BUFFER
[     7.892] (II) Initializing extension RECORD
[     7.892] (II) Initializing extension DPMS
[     7.892] (II) Initializing extension Present
[     7.892] (II) Initializing extension DRI3
[     7.892] (II) Initializing extension X-Resource
[     7.892] (II) Initializing extension XVideo
[     7.892] (II) Initializing extension XVideo-MotionCompensation
[     7.892] (II) Initializing extension GLX
[     7.925] (II) AIGLX: Loaded and initialized vmwgfx
[     7.925] (II) GLX: Initialized DRI2 GL provider for screen 0
[     7.925] (II) Initializing extension XFree86-VidModeExtension
[     7.926] (II) Initializing extension XFree86-DGA
[     7.926] (II) Initializing extension XFree86-DRI
[     7.926] (II) Initializing extension DRI2
[     7.968] (II) vmware(0): Setting screen physical size to 910 x 381
[     8.069] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[     8.069] (**) Power Button: Applying InputClass "devname"
[     8.069] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[     8.069] (**) Power Button: Applying InputClass "system-keyboard"
[     8.069] (II) LoadModule: "libinput"
[     8.069] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[     8.073] (II) Module libinput: vendor="X.Org Foundation"
[     8.073] 	compiled for 1.21.1.8, module version = 1.4.0
[     8.073] 	Module class: X.Org XInput Driver
[     8.073] 	ABI class: X.Org XInput driver, version 24.4
[     8.073] (II) Using input driver 'libinput' for 'Power Button'
[     8.073] (**) Power Button: always reports core events
[     8.073] (**) Option "Device" "/dev/input/event0"
[     8.082] (II) event0  - Power Button: is tagged by udev as: Keyboard
[     8.082] (II) event0  - Power Button: device is a keyboard
[     8.082] (II) event0  - Power Button: device removed
[     8.113] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input0/event0"
[     8.113] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[     8.113] (**) Option "xkb_layout" "us"
[     8.114] (II) event0  - Power Button: is tagged by udev as: Keyboard
[     8.114] (II) event0  - Power Button: device is a keyboard
[     8.116] (II) config/udev: Adding input device VMware VMware Virtual USB Mouse (/dev/input/event1)
[     8.116] (**) VMware VMware Virtual USB Mouse: Applying InputClass "devname"
[     8.116] (**) VMware VMware Virtual USB Mouse: Applying InputClass "libinput pointer catchall"
[     8.116] (II) Using input driver 'libinput' for 'VMware VMware Virtual USB Mouse'
[     8.116] (**) VMware VMware Virtual USB Mouse: always reports core events
[     8.116] (**) Option "Device" "/dev/input/event1"
[     8.175] (II) event1  - VMware VMware Virtual USB Mouse: is tagged by udev as: Mouse
[     8.175] (II) event1  - VMware VMware Virtual USB Mouse: device is a pointer
[     8.175] (II) event1  - VMware VMware Virtual USB Mouse: device removed
[     8.690] (II) libinput: VMware VMware Virtual USB Mouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[     8.690] (II) libinput: VMware VMware Virtual USB Mouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[     8.690] (II) libinput: VMware VMware Virtual USB Mouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[     8.690] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb2/2-1/2-1:1.0/0003:0E0F:0003.0001/input/input1/event1"
[     8.690] (II) XINPUT: Adding extended input device "VMware VMware Virtual USB Mouse" (type: MOUSE, id 7)
[     8.690] (**) Option "AccelerationScheme" "none"
[     8.690] (**) VMware VMware Virtual USB Mouse: (accel) selected scheme none/0
[     8.690] (**) VMware VMware Virtual USB Mouse: (accel) acceleration factor: 2.000
[     8.690] (**) VMware VMware Virtual USB Mouse: (accel) acceleration threshold: 4
[     8.748] (II) event1  - VMware VMware Virtual USB Mouse: is tagged by udev as: Mouse
[     8.748] (II) event1  - VMware VMware Virtual USB Mouse: device is a pointer
[     8.749] (II) config/udev: Adding input device VMware VMware Virtual USB Mouse (/dev/input/mouse0)
[     8.749] (**) VMware VMware Virtual USB Mouse: Applying InputClass "devname"
[     8.749] (II) Using input driver 'libinput' for 'VMware VMware Virtual USB Mouse'
[     8.749] (**) VMware VMware Virtual USB Mouse: always reports core events
[     8.749] (**) Option "Device" "/dev/input/mouse0"
[     8.800] (II) mouse0  - not using input device '/dev/input/mouse0'.
[     8.800] (EE) libinput: VMware VMware Virtual USB Mouse: Failed to create a device for /dev/input/mouse0
[     8.800] (EE) PreInit returned 2 for "VMware VMware Virtual USB Mouse"
[     8.800] (II) UnloadModule: "libinput"
[     8.800] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event2)
[     8.800] (**) AT Translated Set 2 keyboard: Applying InputClass "devname"
[     8.800] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
[     8.800] (**) AT Translated Set 2 keyboard: Applying InputClass "system-keyboard"
[     8.800] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
[     8.800] (**) AT Translated Set 2 keyboard: always reports core events
[     8.800] (**) Option "Device" "/dev/input/event2"
[     8.801] (II) event2  - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[     8.801] (II) event2  - AT Translated Set 2 keyboard: device is a keyboard
[     8.802] (II) event2  - AT Translated Set 2 keyboard: device removed
[     8.820] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input2/event2"
[     8.820] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 8)
[     8.820] (**) Option "xkb_layout" "us"
[     8.821] (II) event2  - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[     8.821] (II) event2  - AT Translated Set 2 keyboard: device is a keyboard
[     8.822] (II) config/udev: Adding input device VirtualPS/2 VMware VMMouse (/dev/input/event5)
[     8.822] (**) VirtualPS/2 VMware VMMouse: Applying InputClass "devname"
[     8.822] (**) VirtualPS/2 VMware VMMouse: Applying InputClass "libinput pointer catchall"
[     8.822] (II) Using input driver 'libinput' for 'VirtualPS/2 VMware VMMouse'
[     8.822] (**) VirtualPS/2 VMware VMMouse: always reports core events
[     8.822] (**) Option "Device" "/dev/input/event5"
[     8.823] (II) event5  - VirtualPS/2 VMware VMMouse: is tagged by udev as: Mouse
[     8.823] (II) event5  - VirtualPS/2 VMware VMMouse: device is a pointer
[     8.823] (II) event5  - VirtualPS/2 VMware VMMouse: device removed
[     8.863] (II) libinput: VirtualPS/2 VMware VMMouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[     8.863] (II) libinput: VirtualPS/2 VMware VMMouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[     8.863] (II) libinput: VirtualPS/2 VMware VMMouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[     8.863] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input5/event5"
[     8.863] (II) XINPUT: Adding extended input device "VirtualPS/2 VMware VMMouse" (type: MOUSE, id 9)
[     8.863] (**) Option "AccelerationScheme" "none"
[     8.863] (**) VirtualPS/2 VMware VMMouse: (accel) selected scheme none/0
[     8.863] (**) VirtualPS/2 VMware VMMouse: (accel) acceleration factor: 2.000
[     8.863] (**) VirtualPS/2 VMware VMMouse: (accel) acceleration threshold: 4
[     8.864] (II) event5  - VirtualPS/2 VMware VMMouse: is tagged by udev as: Mouse
[     8.865] (II) event5  - VirtualPS/2 VMware VMMouse: device is a pointer
[     8.865] (II) config/udev: Adding input device VirtualPS/2 VMware VMMouse (/dev/input/mouse2)
[     8.865] (**) VirtualPS/2 VMware VMMouse: Applying InputClass "devname"
[     8.865] (II) Using input driver 'libinput' for 'VirtualPS/2 VMware VMMouse'
[     8.865] (**) VirtualPS/2 VMware VMMouse: always reports core events
[     8.865] (**) Option "Device" "/dev/input/mouse2"
[     8.897] (II) mouse2  - not using input device '/dev/input/mouse2'.
[     8.897] (EE) libinput: VirtualPS/2 VMware VMMouse: Failed to create a device for /dev/input/mouse2
[     8.897] (EE) PreInit returned 2 for "VirtualPS/2 VMware VMMouse"
[     8.897] (II) UnloadModule: "libinput"
[     8.897] (II) config/udev: Adding input device VirtualPS/2 VMware VMMouse (/dev/input/event4)
[     8.897] (**) VirtualPS/2 VMware VMMouse: Applying InputClass "devname"
[     8.897] (**) VirtualPS/2 VMware VMMouse: Applying InputClass "libinput pointer catchall"
[     8.897] (II) Using input driver 'libinput' for 'VirtualPS/2 VMware VMMouse'
[     8.897] (**) VirtualPS/2 VMware VMMouse: always reports core events
[     8.897] (**) Option "Device" "/dev/input/event4"
[     8.898] (II) event4  - VirtualPS/2 VMware VMMouse: is tagged by udev as: Mouse
[     8.899] (II) event4  - VirtualPS/2 VMware VMMouse: device is a pointer
[     8.899] (II) event4  - VirtualPS/2 VMware VMMouse: device removed
[     8.930] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input6/event4"
[     8.930] (II) XINPUT: Adding extended input device "VirtualPS/2 VMware VMMouse" (type: MOUSE, id 10)
[     8.930] (**) Option "AccelerationScheme" "none"
[     8.930] (**) VirtualPS/2 VMware VMMouse: (accel) selected scheme none/0
[     8.930] (**) VirtualPS/2 VMware VMMouse: (accel) acceleration factor: 2.000
[     8.930] (**) VirtualPS/2 VMware VMMouse: (accel) acceleration threshold: 4
[     8.931] (II) event4  - VirtualPS/2 VMware VMMouse: is tagged by udev as: Mouse
[     8.931] (II) event4  - VirtualPS/2 VMware VMMouse: device is a pointer
[     8.932] (II) config/udev: Adding input device VirtualPS/2 VMware VMMouse (/dev/input/mouse1)
[     8.932] (**) VirtualPS/2 VMware VMMouse: Applying InputClass "devname"
[     8.932] (II) Using input driver 'libinput' for 'VirtualPS/2 VMware VMMouse'
[     8.932] (**) VirtualPS/2 VMware VMMouse: always reports core events
[     8.932] (**) Option "Device" "/dev/input/mouse1"
[     8.963] (II) mouse1  - not using input device '/dev/input/mouse1'.
[     8.963] (EE) libinput: VirtualPS/2 VMware VMMouse: Failed to create a device for /dev/input/mouse1
[     8.963] (EE) PreInit returned 2 for "VirtualPS/2 VMware VMMouse"
[     8.963] (II) UnloadModule: "libinput"
[     8.964] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
[     8.964] (**) PC Speaker: Applying InputClass "devname"
[     8.964] (II) Using input driver 'libinput' for 'PC Speaker'
[     8.964] (**) PC Speaker: always reports core events
[     8.964] (**) Option "Device" "/dev/input/event3"
[     8.965] (II) event3  - PC Speaker: not tagged as supported input device
[     8.996] (II) event3  - not using input device '/dev/input/event3'.
[     8.996] (EE) libinput: PC Speaker: Failed to create a device for /dev/input/event3
[     8.996] (EE) PreInit returned 2 for "PC Speaker"
[     8.996] (II) UnloadModule: "libinput"
[     9.005] (!!) vmware(0): New layout.
[     9.005] (!!) vmware(0): 0: 0 0 3440 1440
[     9.005] (!!) vmware(0):

This is without the `xdotool key "XF86LogGrabInfo"`, can upload that bit too if desired. Otherwise this is just what shows up after starting the device. There's no change upon lock-up.

I did indeed get ssh working earlier, however, I wasn't able to figure out a way to restart i3 and get control back. Restarting i3 would kick my (locked-up) user back to the lock screen but I couldn't log in -- still no input.

Last edited by rschristian (2023-12-09 08:34:12)

Offline

#8 2023-12-09 16:43:45

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,334

Re: [SOLVED] How to debug input lock-out seeming caused by GPU use?

The interesting questions would have been whether
1. the PID matches the grab
2. i3 is eg. stopped (state "T") or a zombie (D)

[     8.800] (EE) libinput: VMware VMware Virtual USB Mouse: Failed to create a device for /dev/input/mouse0
[     8.800] (EE) PreInit returned 2 for "VMware VMware Virtual USB Mouse"
[     8.897] (EE) libinput: VirtualPS/2 VMware VMMouse: Failed to create a device for /dev/input/mouse2
[     8.897] (EE) PreInit returned 2 for "VirtualPS/2 VMware VMMouse"
[     8.963] (EE) libinput: VirtualPS/2 VMware VMMouse: Failed to create a device for /dev/input/mouse1
[     8.963] (EE) PreInit returned 2 for "VirtualPS/2 VMware VMMouse"

There seems some hassle to add the mouse device hmm

Unfortunately I couldn't switch TTY after the lock-up occurred

Restarting i3 would kick my (locked-up) user back to the lock screen but I couldn't log in -- still no input.

And apparently that's not related to the (running) X11 server.

What's the vmware host? Can you try the same VM on a different host system?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#9 2023-12-09 22:44:00

rschristian
Member
Registered: 2021-03-11
Posts: 7

Re: [SOLVED] How to debug input lock-out seeming caused by GPU use?

There seems some hassle to add the mouse device hmm

Yeah, noticed that, but doesn't seem like too much of an issue. That's only comes from startup, after which I have a working mouse any noticeable problems. Might be something funky with the USB sharing or whatnot.

What's the vmware host? Can you try the same VM on a different host system?

Win 10, whatever the latest version is there. Unfortunately no, I don't own any other devices to try.

I have tried on a fresh VM, still could reproduce.

Thanks for all the pointers you've given, even if there isn't an answer to this one.

Offline

#10 2023-12-10 09:35:21

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,334

Re: [SOLVED] How to debug input lock-out seeming caused by GPU use?

You could try to
- keep "dmesg -w" rolling in a visible (on top) terminal
- restart w/ https://wiki.archlinux.org/title/Keyboa … el_(SysRq) (to preserve the journal and see whether the most basic kernel shortcut still works)
- save the VM and restart it (if the problem is exclusive to the host)
- see whether virtualbox behaves better…

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#11 2023-12-18 06:37:10

rschristian
Member
Registered: 2021-03-11
Posts: 7

Re: [SOLVED] How to debug input lock-out seeming caused by GPU use?

Apologies with the long-time without response, I've felt bad but couldn't get anything to produce useful information until tonight.

Happened across this VMWare thread and it looks like it's a bug in VMWare's "Enhanced Keyboard Driver" in 17.5 (latest version) which is installed by default. The solutions presented are to uninstall & reinstall VMWare on the host machine, choosing to forgo this driver, or set the following config in the `.vmx` file:

keyboard.allowBothIRQs = "FALSE"
keyboard.vusb.enable = "TRUE"

Thanks for all your help seth, even if I found the answer in some forum deep in a google search, I wouldn't have gotten there without you helping me figure and rule out some other stuff. I really appreciate it. Thanks!

Last edited by rschristian (2023-12-18 06:38:14)

Offline

Pages: 1

Board footer

Powered by FluxBB