On 2022/06/08 03:14 PM, Felix Miata wrote:
What needs to be changed to cut the wait time down from 90 seconds to 5 seconds when reboot is ordered by a root login on a vtty shell, and TDM is just sitting there on vtty7 doing nothing with nobody logged in? Current is Fedora 35, but this happens at random on any distro that uses systemd. Nothing shows up in journal to indicate any tde/tdm/twin problems. # tail -n22 tdm.log [FIXME] UNCLASSIFIED DEVICE name: ptp0 type: (null) subsystem: ptp driver: e1000e [Node Path: /dev/ptp0] [Syspath: /sys/devices/pci0000:00/0000:00:1f.6/ptp/ptp0] [8086:15b8] [FIXME] UNCLASSIFIED DEVICE name: wmi_bus-PNP0C14:00 type: (null) subsystem: wmi_bus driver: acpi-wmi [Node Path: (null)] [Syspath: /sys/devices/pci0000:00/PNP0C14:00/wmi_bus/wmi_bus-PNP0C14:00] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: F6CB5C3C-9CAE-4EBD-B577-931EA32A2CC0 type: method subsystem: wmi driver: (null) [Node Path: (null)] [Syspath: /sys/devices/pci0000:00/PNP0C14:00/wmi_bus/wmi_bus-PNP0C14:00/F6CB5C3C-9CAE-4EBD-B577-931EA32A2CC0] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: wmi_bus-PNP0C14:01 type: (null) subsystem: wmi_bus driver: acpi-wmi [Node Path: (null)] [Syspath: /sys/devices/platform/PNP0C14:01/wmi_bus/wmi_bus-PNP0C14:01] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: 05901221-D566-11D1-B2F0-00A0C9062910 type: data subsystem: wmi driver: wmi-bmof [Node Path: (null)] [Syspath: /sys/devices/platform/PNP0C14:01/wmi_bus/wmi_bus-PNP0C14:01/05901221-D566-11D1-B2F0-00A0C9062910] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: 466747A0-70EC-11DE-8A39-0800200C9A66 type: method subsystem: wmi driver: (null) [Node Path: (null)] [Syspath: /sys/devices/platform/PNP0C14:01/wmi_bus/wmi_bus-PNP0C14:01/466747A0-70EC-11DE-8A39-0800200C9A66] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: 97845ED0-4E6D-11DE-8A39-0800200C9A66 type: method subsystem: wmi driver: (null) [Node Path: (null)] [Syspath: /sys/devices/platform/PNP0C14:01/wmi_bus/wmi_bus-PNP0C14:01/97845ED0-4E6D-11DE-8A39-0800200C9A66] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: ABBC0F72-8EA1-11D1-00A0-C90629100000 type: event subsystem: wmi driver: (null) [Node Path: (null)] [Syspath: /sys/devices/platform/PNP0C14:01/wmi_bus/wmi_bus-PNP0C14:01/ABBC0F72-8EA1-11D1-00A0-C90629100000] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: wakeup22 type: (null) subsystem: wakeup driver: i8042 kbd [Node Path: (null)] [Syspath: /sys/devices/pnp0/00:01/wakeup/wakeup22] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: cmos_nvram0 type: (null) subsystem: nvmem driver: (null) [Node Path: (null)] [Syspath: /sys/devices/pnp0/00:04/cmos_nvram0] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: wakeup24 type: (null) subsystem: wakeup driver: alarmtimer [Node Path: (null)] [Syspath: /sys/devices/pnp0/00:04/rtc/rtc0/alarmtimer.0.auto/wakeup/wakeup24] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: wakeup23 type: (null) subsystem: wakeup driver: rtc_cmos [Node Path: (null)] [Syspath: /sys/devices/pnp0/00:04/wakeup/wakeup23] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: mc type: (null) subsystem: edac driver: (null) [Node Path: (null)] [Syspath: /sys/devices/system/edac/mc] [(null):(null)] /etc/trinity/tdm/Xsetup: line 7: syntax error: unexpected end of file /usr/bin/iceauth: creating new authority file /tmp/0935833680/.ICEauthority [2022/06/08 01:53:37.174] TQThreadInstance::start: Setting thread storage to 0x55bbcd43d050 [2022/06/08 01:53:37.234] TQObject::activate_signal: Invoking cross-thread method from object 0x55bbcd3f4b90 (member 2 receiver 0x55bbcd43fc60) (1) (II) AIGLX: Suspending AIGLX clients for VT switch [2022/06/08 01:55:45.951] twin: Fatal IO error: client killed (II) Server terminated successfully (0). Closing log file. # cat /etc/trinity/tdm/Xsetup #!/usr/bin/sh # Xsetup - run as root before the login dialog appears #xconsole -geometry 480x130-0-0 -notify -verbose -fn fixed -exitOnFail -file /dev/xconsole & if [ -x /home/setup ] ; then /home/setup # I have no idea why Xsetup: line 7: unexpected end of file occurs.
Hi Felix, the 90s delays is the default timeout in systemd when somethings does not start/stop correctly... super annoying. I usually edit the /etc/systemd/system.conf file and add these lines in: DefaultTimeoutStartSec=5s DefaultTimeoutStopSec=5s This reduces the wait to 5s, which should be more than enough for any normal executing process to do what it needs. Cheers Michele
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature
____________________________________________________ tde-devels mailing list -- devels@xxxxxxxxxxxxxxxxxx To unsubscribe send an email to devels-leave@xxxxxxxxxxxxxxxxxx Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@xxxxxxxxxxxxxxxxxx
