T470s
Qubes-HCL-LENOVO-20NX000GMZ-20210810-145438.yml (786 Bytes)
Thank you @oijawyuh once again for your HCL report, which is now part of this pull request and will be visible on the website soon!
2 Likes
@oijawyuh a reporter on qubes-users pointed out that the model code 20nx000gmz identifies a ThinkPad T490s. Can you confirm that this HCL is for a T490s?
Never mind, I see what happened. You reported the same machine again at a later time correctly:
… so I’ll simply remove the erroneous T470s entry.
1 Like
Remarks
Sleep works properly when SMT (Multi-threading) is disabled in the BIOS. Also 40% speed boost with SMT disabled in the BIOS.
Attachments
Qubes-HCL-LENOVO-20JTS3HB00-20220602-144034.yml (982 Bytes)
2 Likes
Thank you @flavio for your HCL report, which is online now!
Qubes OS disables SMT by default regardless of the BIOS setting as far as I understand. I can see how changing it in the BIOS can fix the sleep issue (probable dependencies in UEFI/ME) but what could cause the 40% performance boost?
PS: I moved your post into this thread to have one thread per machine in the HCL reports category.
That is a great question! But unfortunately, one that I don’t have an answer for. Look at the following boot times, with the only change being the SMT configuration in the BIOS (both with the latest 4.1 patches). It seems that starting new Qubes is where most of the time difference is.
SMT Disabled in the BIOS:
[flavio@dom0 ~]$ systemd-analyze
Startup finished in 15.718s (firmware) + 3.991s (loader) + 10.076s (kernel) + 9.945s (initrd) + 50.683s (userspace) = 1min 30.415s
graphical.target reached after 50.636s in userspace
[flavio@dom0 ~]$ systemd-analyze blame
43.176s qubes-vm@sys-whonix.service >
32.495s qubes-vm@sys-firewall.service >
27.216s qubes-vm@sys-usb.service >
18.018s qubes-vm@sys-net.service >
7.179s dracut-initqueue.service >
5.793s systemd-cryptsetup@luks\x2d90d3ac5e\x2d2114\x2d43b7\x2d9d35\x2d0f540bdf>
3.780s systemd-udev-settle.service >
2.752s lvm2-pvscan@253:0.service >
2.377s lvm2-monitor.service >
1.381s plymouth-quit-wait.service >
1.314s qubes-qmemman.service >
678ms upower.service >
649ms qubesd.service >
637ms dracut-cmdline.service >
538ms initrd-switch-root.service >
431ms systemd-vconsole-setup.service >
388ms systemd-logind.service >
305ms accounts-daemon.service >
296ms systemd-udev-trigger.service >
294ms initrd-parse-etc.service >
262ms user@1000.service >
262ms xenstored.service >
260ms qubes-core.service >
229ms systemd-homed.service >
216ms polkit.service >
191ms libvirtd.service >
185ms systemd-journal-flush.service >
175ms systemd-udevd.service >
156ms systemd-journald.service >
114ms lightdm.service >
105ms dev-mqueue.mount >
103ms proc-xen.mount >
103ms dev-mapper-qubes_dom0\x2dswap.swap >
101ms sys-kernel-debug.mount >
99ms sys-kernel-tracing.mount >
97ms systemd-tmpfiles-setup-dev.service >
91ms kmod-static-nodes.service >
89ms xen-init-dom0.service >
84ms plymouth-start.service >
83ms systemd-fsck@dev-disk-by\x2duuid-1A97\x2dECC5.service >
79ms sys-kernel-config.mount >
77ms modprobe@fuse.service >
75ms systemd-random-seed.service >
72ms dracut-pre-udev.service >
72ms systemd-tmpfiles-setup.service >
63ms dmraid-activation.service >
62ms systemd-fsck@dev-disk-by\x2duuid-b4cecd7b\x2db58a\x2d4778\x2d8abe\x2df0>
61ms systemd-modules-load.service >
60ms systemd-tmpfiles-clean.service >
58ms systemd-repart.service >
58ms tmp.mount >
57ms systemd-sysctl.service >
55ms qubes-db-dom0.service >
54ms xenconsoled.service >
49ms systemd-userdbd.service >
43ms boot-efi.mount >
42ms systemd-remount-fs.service >
40ms systemd-rfkill.service >
37ms systemd-fsck-root.service >
37ms systemd-update-utmp-runlevel.service >
36ms systemd-backlight@backlight:intel_backlight.service >
34ms initrd-cleanup.service >
32ms plymouth-switch-root.service >
30ms dbus-broker.service >
28ms systemd-update-utmp.service >
27ms systemd-backlight@leds:tpacpi::kbd_backlight.service >
25ms var-lib-xenstored.mount >
25ms systemd-user-sessions.service >
22ms sys-fs-fuse-connections.mount >
21ms initrd-udevadm-cleanup-db.service >
21ms dracut-shutdown.service >
21ms user-runtime-dir@1000.service >
20ms plymouth-read-write.service >
12ms rtkit-daemon.service >
12ms boot.mount >
11ms sysroot.mount >
SMT Enabled in the BIOS
[flavio@dom0 ~]$ systemd-analyze
Startup finished in 16.048s (firmware) + 4.161s (loader) + 10.179s (kernel) + 10.404s (initrd) + 1min 43.542s (userspace) = 2min 24.337s
graphical.target reached after 1min 43.488s in userspace
[flavio@dom0 ~]$ systemd-analyze blame
1min 36.019s qubes-vm@sys-whonix.service >
52.232s qubes-vm@sys-firewall.service >
29.600s qubes-vm@sys-net.service >
26.122s qubes-vm@sys-usb.service >
7.599s dracut-initqueue.service >
6.099s systemd-cryptsetup@luks\x2d90d3ac5e\x2d2114\x2d43b7\x2d9d35\x2d0f5>
3.836s systemd-udev-settle.service >
2.802s lvm2-pvscan@253:0.service >
2.513s lvm2-monitor.service >
1.348s qubes-qmemman.service >
1.227s plymouth-quit-wait.service >
677ms upower.service >
658ms qubesd.service >
611ms dracut-cmdline.service >
542ms initrd-switch-root.service >
406ms systemd-vconsole-setup.service >
377ms systemd-logind.service >
298ms systemd-udev-trigger.service >
290ms initrd-parse-etc.service >
265ms user@1000.service >
261ms qubes-core.service >
246ms xenstored.service >
237ms libvirtd.service >
235ms systemd-journal-flush.service >
193ms systemd-homed.service >
189ms systemd-udevd.service >
147ms accounts-daemon.service >
145ms systemd-journald.service >
126ms xen-init-dom0.service >
112ms systemd-fsck@dev-disk-by\x2duuid-1A97\x2dECC5.service >
111ms dev-mapper-qubes_dom0\x2dswap.swap >
109ms dev-mqueue.mount >
107ms proc-xen.mount >
104ms sys-kernel-debug.mount >
104ms polkit.service >
97ms sys-kernel-tracing.mount >
94ms kmod-static-nodes.service >
90ms sys-kernel-config.mount >
89ms lightdm.service >
89ms modprobe@fuse.service >
84ms plymouth-start.service >
77ms systemd-remount-fs.service >
73ms dracut-pre-udev.service >
73ms systemd-modules-load.service >
72ms systemd-repart.service >
67ms systemd-tmpfiles-setup.service >
64ms systemd-tmpfiles-setup-dev.service >
64ms systemd-fsck@dev-disk-by\x2duuid-b4cecd7b\x2db58a\x2d4778\x2d8abe>
57ms systemd-sysctl.service >
55ms dmraid-activation.service >
53ms systemd-random-seed.service >
50ms qubes-db-dom0.service >
46ms systemd-userdbd.service >
46ms xenconsoled.service >
37ms systemd-update-utmp-runlevel.service >
37ms dbus-broker.service >
36ms initrd-cleanup.service >
36ms plymouth-read-write.service >
35ms systemd-fsck-root.service >
34ms plymouth-switch-root.service >
33ms user-runtime-dir@1000.service >
32ms systemd-update-utmp.service >
30ms boot-efi.mount >
27ms systemd-backlight@backlight:intel_backlight.service >
26ms rtkit-daemon.service >
25ms dracut-shutdown.service >
25ms systemd-user-sessions.service >
23ms systemd-rfkill.service >
22ms boot.mount >
22ms sys-fs-fuse-connections.mount >
20ms tmp.mount >
19ms initrd-udevadm-cleanup-db.service >
19ms systemd-backlight@leds:tpacpi::kbd_backlight.service >
18ms sysroot.mount >
15ms var-lib-xenstored.mount >
1 Like