kern/57391: A few minutes system hang during Xorg startup

[bsdprg%tuta.io@localhost]

>Number:         57391
>Category:       kern
>Synopsis:       A few minutes system hang during Xorg startup
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri May 05 19:10:00 +0000 2023
>Originator:     Salil Wadnerkar
>Release:        10.0_BETA
>Organization:
>Environment:
NetBSD xps 10.0_BETA NetBSD 10.0_BETA (GENERIC) #0: Tue May  2 21:31:56 UTC 2023  mkrepro%mkrepro.NetBSD.org@localhost:/usr/src/sys/arch/amd64/compile/GENERIC amd64
>Description:
When we start Xorg either by xinit or xdm, the system hangs for a minute or two. My dmesg shows:
[     6.856758] wsdisplay0: screen 1 added (default, vt100 emulation)
[     6.856758] wsdisplay0: screen 2 added (default, vt100 emulation)
[     6.856758] wsdisplay0: screen 3 added (default, vt100 emulation)
[     6.856758] wsdisplay0: screen 4 added (default, vt100 emulation)
[    17.306724] pms0: autoconfiguration error: command error 0xf5
[    18.316720] pms0: autoconfiguration error: command error 0xe6
[    19.316717] pms0: autoconfiguration error: command error 0xe6
[    24.356700] autoconfiguration error: synaptics: set mode error
[    25.356697] pms0: autoconfiguration error: command error 0xe6
[    26.366693] pms0: autoconfiguration error: command error 0xe6
[    32.396677] pckbport: command timeout
[    42.556640] autoconfiguration error: pms_enable: command error 35
[    43.556640] pckbport: command timeout
[    53.716603] autoconfiguration error: pms_disable: command error
[    54.734644] pms0: autoconfiguration error: command error 0xf5
[    55.740782] pms0: autoconfiguration error: command error 0xe6
[    56.746912] pms0: autoconfiguration error: command error 0xe6
[    61.783168] autoconfiguration error: synaptics: set mode error

Xorg eventually starts.

>How-To-Repeat:
This happens every time we start Xorg. And this happens on 9.x also. I just thought someone might have reported it, and this would have been solved in 10.0.
>Fix: