v0.5.0 RC3 testing results

[macpijan]

1. Restored original UEFI firmware on my x230 (Intel, TPM1.2). TXT enabled in firmware setup. Result:

2. Tried also on my desktop just for fun (Ryzen 5 5600). Result:

[SergiiDmytruk]

1. TXT heap is not configured correctly

That's before GRUB started doing anything. Looks like firmware doesn't configure TXT or it's not supported.

That's expected output. If there is no more output, it might actually be booting with uninitialized console. That's what happens on VP4670 which has serial console, but not the vga one.

[macpijan]

That's before GRUB started doing anything. Looks like firmware doesn't configure TXT or it's not supported.

I think it should be supported in general on this device. But maybe my backup is lacking.

Booted also DTS to run txt-suite:

root@DasharoToolsSuite:~# txt-suite  exec-tests
For more information about the documents and chapters, run: txt-suite -m

All tests
_________
2025/04/14 21:57:13 address =dabfe014
2025/04/14 21:57:13 signature RSD PTR 
00 - Intel CPU                               : PASS                
01 - Weybridge or later                      : PASS                
02 - CPU supports TXT                        : PASS                
03 - TXT register space accessible           : PASS                
04 - CPU supports SMX                        : PASS                
05 - CPU supports VMX                        : PASS                
06 - IA32_FEATURE_CONTROL                    : PASS                
07 - TXT not disabled by BIOS                : PASS                
08 - BIOS ACM has run                        : FAIL                 (Bootstatus register incorrect)
09 - IBB is trusted                          : FAIL                 (IBB not trusted)
10 - TXT registers are locked                : FAIL                 (TXT register space is NOT locked)
11 - IA32 debug interface is disabled        : PASS                
12 - TPM connection                          : INTERNAL_ERROR       (TPM device not available)
13 - TPM is present                          : DEPENDENCY_FAILED    (TPM connection failed)
14 - TPM NVRAM is locked                     : DEPENDENCY_FAILED    (TPM is present failed)
15 - PS Index has correct config             : DEPENDENCY_FAILED    (TPM is present failed)
16 - AUX Index has correct config            : DEPENDENCY_FAILED    (TPM is present failed)
17 - AUX Index has the correct hash          : DEPENDENCY_FAILED    (TPM is present failed)
18 - PO Index has correct config             : DEPENDENCY_FAILED    (TPM is present failed)
19 - PS index has valid LCP Policy           : DEPENDENCY_FAILED    (TPM is present failed)
20 - PO index has valid LCP Policy           : DEPENDENCY_FAILED    (TPM is present failed)
21 - PCR 0 is set correctly                  : DEPENDENCY_FAILED    (TPM is present failed)
22 - NPW mode is deactivated in PS policy    : DEPENDENCY_FAILED    (PS index has valid LCP Policy failed)
23 - TXT mode is valid                       : DEPENDENCY_FAILED    (PS index has valid LCP Policy failed)
24 - Valid FIT vector                        : FAIL                 (FitPointer must be in ValidFitRange)
25 - Valid FIT                               : DEPENDENCY_FAILED    (Valid FIT vector failed)
26 - Microcode update entry in FIT           : DEPENDENCY_FAILED    (Valid FIT failed)
27 - BIOS ACM entry in FIT                   : DEPENDENCY_FAILED    (Valid FIT failed)
28 - IBB entry in FIT                        : DEPENDENCY_FAILED    (Valid FIT failed)
29 - BIOS Policy entry in FIT                : DEPENDENCY_FAILED    (TXT mode is valid failed)
30 - IBB covers reset vector                 : DEPENDENCY_FAILED    (IBB entry in FIT failed)
31 - IBB covers FIT vector                   : DEPENDENCY_FAILED    (IBB entry in FIT failed)
32 - IBB covers FIT                          : DEPENDENCY_FAILED    (IBB entry in FIT failed)
33 - IBBs doesn't overlap each other         : DEPENDENCY_FAILED    (IBB entry in FIT failed)
34 - BIOS ACM does not overlap IBBs          : DEPENDENCY_FAILED    (BIOS ACM entry in FIT failed)
35 - IBB and BIOS ACM below 4GiB             : DEPENDENCY_FAILED    (BIOS ACM entry in FIT failed)
36 - TXT not disabled by LCP Policy          : DEPENDENCY_FAILED    (Valid FIT failed)
37 - BIOSACM header valid                    : DEPENDENCY_FAILED    (BIOS ACM entry in FIT failed)
38 - BIOSACM size check                      : DEPENDENCY_FAILED    (BIOS ACM entry in FIT failed)
39 - BIOSACM alignment check                 : DEPENDENCY_FAILED    (BIOS ACM entry in FIT failed)
40 - BIOSACM matches chipset                 : DEPENDENCY_FAILED    (BIOS ACM entry in FIT failed)
41 - BIOSACM matches processor               : DEPENDENCY_FAILED    (BIOS ACM entry in FIT failed)
42 - SINIT/BIOS ACM has no NPW flag set      : DEPENDENCY_FAILED    (BIOS ACM entry in FIT failed)
43 - SINIT ACM supports used TPM             : DEPENDENCY_FAILED    (BIOS ACM entry in FIT failed)
44 - TXT heap ranges valid                   : FAIL                 (Heap must be at least 917504)
45 - TXT public area reserved in e820        : FAIL                 (TXTPublic area is not marked reserved in e820 map)
46 - TXT private area reserved in e820       : FAIL                 (TXTPrivate area is not marked reserved in e820 map)
47 - TXT memory reserved in e820             : DEPENDENCY_FAILED    (TXT heap ranges valid failed)
48 - MMIO TPMDecode space reserved in e820   : FAIL                 (TPMDecode area not reserved in e820)
49 - TXT memory in a DMA protected range     : DEPENDENCY_FAILED    (TXT heap ranges valid failed)
50 - TXT DPR register locked                 : FAIL                 (TXTDPR is not locked)
51 - CPU DPR equals hostbridge DPR           : FAIL                 (Hostbridge DPR Top doesn't match TXT DPR Top)
52 - CPU hostbridge DPR register locked      : DEPENDENCY_FAILED    (CPU DPR equals hostbridge DPR failed)
53 - TXT region contains SINIT ACM           : INTERNAL_ERROR       (EOF)
54 - SINIT ACM matches chipset               : DEPENDENCY_FAILED    (TXT region contains SINIT ACM failed)
55 - SINIT ACM matches CPU                   : DEPENDENCY_FAILED    (TXT region contains SINIT ACM failed)
56 - SINIT ACM startup successful            : FAIL                 (SINIT Error detected)
57 - BIOS DATA REGION present                : INTERNAL_ERROR       (EOF)
58 - BIOS DATA REGION valid                  : DEPENDENCY_FAILED    (BIOS DATA REGION present failed)
59 - CPU supports MTRRs                      : PASS                
60 - CPU supports SMRRs                      : PASS                
61 - SMRR covers SMM memory                  : FAIL                 (TSEG base isn't aligned to SMRR Physmask)
62 - SMRR protection active                  : PASS                
63 - IOMMU/VT-d active                       : FAIL                 (Failed to check SMRR DMA protection: No IOMMU found: /sys/class/iommu/*/intel-iommu/address does not exists or is malformed)
64 - TXT server mode enabled                 : PASS                
65 - ACPI RSDP exists and has valid checksum : PASS                
66 - ACPI MCFG is present                    : PASS                
67 - ACPI DMAR is present                    : PASS                
68 - ACPI DMAR is valid                      : PASS                
69 - ACPI MADT is present                    : PASS                
70 - ACPI MADT is valid                      : PASS                
72 - ACPI RSDT is valid                      : PASS                
73 - ACPI XSDT present                       : PASS                
74 - ACPI XSDT is valid                      : PASS                
75 - ACPI RSDT or XSDT is valid              : PASS                
txt-suite: error: Tests ran with errors

[SergiiDmytruk]

...
08 - BIOS ACM has run                        : FAIL                 (Bootstatus register incorrect)
...
10 - TXT registers are locked                : FAIL                 (TXT register space is NOT locked)
...
24 - Valid FIT vector                        : FAIL                 (FitPointer must be in ValidFitRange)
...
44 - TXT heap ranges valid                   : FAIL                 (Heap must be at least 917504)
45 - TXT public area reserved in e820        : FAIL                 (TXTPublic area is not marked reserved in e820 map)
46 - TXT private area reserved in e820       : FAIL                 (TXTPrivate area is not marked reserved in e820 map)
...

It's not supposed to work with this firmware.

[macpijan]

@SergiiDmytruk Tried the same image on Lenovo M920q with BIOS as written here: Dasharo/dasharo-issues#579 (comment)

Can I ask for a suggestion whether it looks promising or not so much? Can I provide any more info?

Result:

1. Linux with TB - platform resets to the BIOS - I guess it was not supposed to work in this version?
2. Xen with TB (EFI)

• boots into shell - is it any form of success result, or not so much?
• no /dev/tpm0 device, cannot see PCR list (there is one when booting normally into Linux)
• dmesg log for reference: https://paste.dasharo.com/?1debf1de8fb9f8f2#CHvJUzyckUQrnTpnY5ByHprNwfajqcGc8vP9oEm31PBn

txt-suite result for reference (executed on DTS):

00 - Intel CPU                               : PASS                
01 - Weybridge or later                      : PASS                
02 - CPU supports TXT                        : FAIL                 (CPU is not listed in any Intel CPU list)
03 - TXT register space accessible           : PASS                
04 - CPU supports SMX                        : PASS                
05 - CPU supports VMX                        : PASS                
06 - IA32_FEATURE_CONTROL                    : PASS                
07 - TXT not disabled by BIOS                : PASS                
08 - BIOS ACM has run                        : PASS                
09 - IBB is trusted                          : FAIL                 (IBB not trusted)
10 - TXT registers are locked                : FAIL                 (TXT register space is NOT locked)
11 - IA32 debug interface is disabled        : FAIL                 (ia32 jtag is force enabled by a hardware strap)
12 - TPM connection                          : PASS                
13 - TPM is present                          : PASS                
14 - TPM NVRAM is locked                     : PASS                
15 - PS Index has correct config             : PASS                
16 - AUX Index has correct config            : PASS                
17 - AUX Index has the correct hash          : PASS                
18 - PO Index has correct config             : FAIL                 (PO index not set)
19 - PS index has valid LCP Policy           : PASS                
20 - PO index has valid LCP Policy           : FAIL                 (PO index not set)
21 - PCR 0 is set correctly                  : PASS                
22 - NPW mode is deactivated in PS policy    : PASS                
23 - TXT mode is valid                       : PASS                
24 - Valid FIT vector                        : PASS                
25 - Valid FIT                               : PASS                
26 - Microcode update entry in FIT           : PASS                
27 - BIOS ACM entry in FIT                   : PASS                
28 - IBB entry in FIT                        : FAIL                 (Fit has no BIOS Startup Module Entry, but at least one is required)
29 - BIOS Policy entry in FIT                : PASS                
30 - IBB covers reset vector                 : DEPENDENCY_FAILED    (IBB entry in FIT failed)
31 - IBB covers FIT vector                   : DEPENDENCY_FAILED    (IBB entry in FIT failed)
32 - IBB covers FIT                          : DEPENDENCY_FAILED    (IBB entry in FIT failed)
33 - IBBs doesn't overlap each other         : DEPENDENCY_FAILED    (IBB entry in FIT failed)
34 - BIOS ACM does not overlap IBBs          : PASS                
35 - IBB and BIOS ACM below 4GiB             : PASS                
36 - TXT not disabled by LCP Policy          : PASS                
37 - BIOSACM header valid                    : PASS                
38 - BIOSACM size check                      : PASS                
39 - BIOSACM alignment check                 : PASS                
40 - BIOSACM matches chipset                 : FAIL                 (BIOS StartUp Module and Chipset doens't match)
41 - BIOSACM matches processor               : FAIL                 (BIOS Startup Module and CPU doesn't match)
42 - SINIT/BIOS ACM has no NPW flag set      : PASS                
43 - SINIT ACM supports used TPM             : FAIL                 (SINIT ACM does not support used TPM)
44 - TXT heap ranges valid                   : PASS                
45 - TXT public area reserved in e820        : PASS                
46 - TXT private area reserved in e820       : PASS                
47 - TXT memory reserved in e820             : PASS                
48 - MMIO TPMDecode space reserved in e820   : PASS                
49 - TXT memory in a DMA protected range     : FAIL                 (TXT heap region must end at top of DPR region)
50 - TXT DPR register locked                 : PASS                
51 - CPU DPR equals hostbridge DPR           : PASS                
52 - CPU hostbridge DPR register locked      : PASS                
53 - TXT region contains SINIT ACM           : FAIL                 (SINIT in TXT: ACM ModuleType not 2)
54 - SINIT ACM matches chipset               : DEPENDENCY_FAILED    (TXT region contains SINIT ACM failed)
55 - SINIT ACM matches CPU                   : DEPENDENCY_FAILED    (TXT region contains SINIT ACM failed)
56 - SINIT ACM startup successful            : FAIL                 (SINIT Error detected)
57 - BIOS DATA REGION present                : PASS                
58 - BIOS DATA REGION valid                  : FAIL                 (BIOS DATA region is too small)
59 - CPU supports MTRRs                      : PASS                
60 - CPU supports SMRRs                      : PASS                
61 - SMRR covers SMM memory                  : FAIL                 (TSEG base isn't aligned to SMRR Physmask)
62 - SMRR protection active                  : PASS                
63 - IOMMU/VT-d active                       : FAIL                 (Failed to check SMRR DMA protection: No IOMMU found: /sys/class/iommu/*/intel-iommu/address does not exists or is malf)
64 - TXT server mode enabled                 : PASS                
65 - ACPI RSDP exists and has valid checksum : PASS                
66 - ACPI MCFG is present                    : PASS                
67 - ACPI DMAR is present                    : PASS                
68 - ACPI DMAR is valid                      : PASS                
69 - ACPI MADT is present                    : PASS                
70 - ACPI MADT is valid                      : PASS                
72 - ACPI RSDT is valid                      : PASS                
73 - ACPI XSDT present                       : PASS                
74 - ACPI XSDT is valid                      : PASS                
75 - ACPI RSDT or XSDT is valid              : PASS 

[miczyg1]

02 - CPU supports TXT : FAIL (CPU is not listed in any Intel CPU list)

This can be false negative. The suite has a hardcoded list of CPUs known to support TXT. It can be easily confirmed with cat /proc/cpuinfo |grep smx (should not be empty for TXT supported CPU)

09 - IBB is trusted : FAIL (IBB not trusted)

I think that's only possible with BTG enabled. The definition in the BWGs are not precise when this should be set.

10 - TXT registers are locked : FAIL (TXT register space is NOT locked)

That is probably only a guideline to follow. Shouldn't restrict the capability to perform dynamic launch.

11 - IA32 debug interface is disabled : FAIL (ia32 jtag is force enabled by a hardware strap)

This will prevent SINIT ACM from executing dynamic launch. BIOS needs to disable the interface via MSR_IA32_DEBUG_INTERFACE (0xc80) and lock that MSR.

18 - PO Index has correct config : FAIL (PO index not set)
20 - PO index has valid LCP Policy : FAIL (PO index not set)

PO index is not mandatory and is optional for Platform Owner (PO) to create it and put an LCP policy in there. Does not affect the capability to perform measured launch.

28 - IBB entry in FIT : FAIL (Fit has no BIOS Startup Module Entry, but at least one is required)
30 - IBB covers reset vector : DEPENDENCY_FAILED (IBB entry in FIT failed)
31 - IBB covers FIT vector : DEPENDENCY_FAILED (IBB entry in FIT failed)
32 - IBB covers FIT : DEPENDENCY_FAILED (IBB entry in FIT failed)
33 - IBBs doesn't overlap each other : DEPENDENCY_FAILED (IBB entry in FIT failed)

BIOS Startup Module Entries are needed only on server TXT before CBnT was introduced. On client it was never needed. So these are false negative for client systems.

40 - BIOSACM matches chipset : FAIL (BIOS StartUp Module and Chipset doens't match)
41 - BIOSACM matches processor : FAIL (BIOS Startup Module and CPU doesn't match)

That's weird. Worth checking ACM header against the CPUID, chipset ID and TXT device ID to see if it is really true. That may be a blocker to perform dynamic launch.

43 - SINIT ACM supports used TPM : FAIL (SINIT ACM does not support used TPM)

That is probably caused by lack of /dev/tpm0 in DTS? I think the suite can not query TPM interface capabilities and match it with SINIT ACM capabilities in its header.

49 - TXT memory in a DMA protected range : FAIL (TXT heap region must end at top of DPR region)

That may be a problem. Spec says the heap must occupy the top of DPR.

53 - TXT region contains SINIT ACM : FAIL (SINIT in TXT: ACM ModuleType not 2)
54 - SINIT ACM matches chipset : DEPENDENCY_FAILED (TXT region contains SINIT ACM failed)
55 - SINIT ACM matches CPU : DEPENDENCY_FAILED (TXT region contains SINIT ACM failed)
56 - SINIT ACM startup successful : FAIL (SINIT Error detected)

BIOS doesn't necessarily have to place SINIT ACM in the TXT heap region. it can be done by TBOOT or any other dynamic launch preparation environment. If these are still FAIl after a dynamic launch attempt, then something is wrong.

58 - BIOS DATA REGION valid : FAIL (BIOS DATA region is too small)

As above, BISO does not have to place SINTI ACM in the TXT heap region. BIOS DATA region holds the information abotu ACMs placed in memory. This should not be FAIL after a dynamic launch attempt.

61 - SMRR covers SMM memory : FAIL (TSEG base isn't aligned to SMRR Physmask)

Looks like a BIOS bug in memory map allocation. Not sure how serious it is, but it may prevent dynamic launch if the ACM checks for this.

63 - IOMMU/VT-d active : FAIL (Failed to check SMRR DMA protection: No IOMMU found: /sys/class/iommu/*/intel-iommu/address does not exists or is malf)

The VT-d / IOMMU may be disabled in BIOS, thus the error. However, the DMAR is present. Maybe IOMMU drivers missing in DTS?

[macpijan]

This can be false negative. The suite has a hardcoded list of CPUs known to support TXT. It can be easily confirmed with cat /proc/cpuinfo |grep smx (should not be empty for TXT supported CPU

Correct this is not empty. I recall there is hardcoded list of CPUs in this tool.

I think that's only possible with BTG enabled. The definition in the BWGs are not precise when this should be set.

BTG is clearly not enabled on this platform.

This will prevent SINIT ACM from executing dynamic launch. BIOS needs to disable the interface via MSR_IA32_DEBUG_INTERFACE (0xc80) and lock that MSR.

So this platform is excluded from using DRTM/TrenchBoot, or something can be done about it? The error says about hw strap, any chance I should look for some jumpers, etc? If so, which signals am I interested in?

That's weird. Worth checking ACM header against the CPUID, chipset ID and TXT device ID to see if it is really true. That may be a blocker to perform dynamic launch.

To be checked later

That is probably caused by lack of /dev/tpm0 in DTS? I think the suite can not query TPM interface capabilities and match it with SINIT ACM capabilities in its header.

/dev/tpm0 is in DTS (where this test fails). I mentioned that it was not present in the meta-trenchboot Xen image for some reason. What may be interesting, it is present when booting xen normally, but is gone when booting with TrenchBoot (UEFI) option from: https://github.com/zarhus/meta-trenchboot/blob/0.5.0-rc4-components/wic/grub-full.cfg#L69

@SergiiDmytruk @krystian-hebel are there any more tests worth executing after booting this menu entry, if the /dev/tpm0 device is not present?

If I can boot this entry with no visible errors, does it mean anything in terms of success, or not so much, until we check the TPM registers?

The VT-d / IOMMU may be disabled in BIOS, thus the error. However, the DMAR is present. Maybe IOMMU drivers missing in DTS?

VT-d was set to enabled in BIOS and DTS has CONFIG_INTEL_IOMMU=y

[SergiiDmytruk]

Linux with TB - platform resets to the BIOS - I guess it was not supposed to work in this version?

I think it should be working.

Xen with TB (EFI)

boots into shell - is it any form of success result, or not so much?

Coupled with the absence of TPM, I doubt it's a success. Maybe it booted when it shouldn't? Although that would be unexpected, but not impossible if something goes wrong and unnoticed but isn't disruptive for the boot process.

are there any more tests worth executing after booting this menu entry, if the /dev/tpm0 device is not present?

xl dmesg since it's Xen which deals with DRTM.

[krystian-hebel]

@macpijan I would check whether TPM uses TIS or CRB, it should be shown somewhere in plain Linux's dmesg, without TrenchBoot or Xen to mess with things. We haven't tested TrenchBoot with CRB yet, except for AMD fTPM's CRB-wannabe, which doesn't work for different reasons.

[macpijan]

I think it should be working.

Well, it's not. It asks me to press the key, I press it, it reboots with no information whatsoever. What would be the recommended additional steps that could be done to deliver TrenchBoot developers some useful information on this particular case?

I would check whether TPM uses TIS or CRB, it should be shown somewhere in plain Linux's dmesg

dmesg from regular Linux boot

Relevant line: [ 2.353272] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0x1B, rev-id 16)

So I assume it's TIS.

xl dmesg since it's Xen which deals with DRTM.

xl dmesg when booting with TrenchBoot

Is there anything specific we should look for in these logs?

[SergiiDmytruk]

I think it should be working.

Well, it's not. It asks me to press the key, I press it, it reboots with no information whatsoever. What would be the recommended additional steps that could be done to deliver TrenchBoot developers some useful information on this particular case?

What asks you to press the key? GRUB? ACM and Linux reboot without printing errors, you have to do slaunch and slaunch_state in GRUB after reboot to see TXT.ERROR register for the reason behind reboot.

xl dmesg when booting with TrenchBoot

Is there anything specific we should look for in these logs?

slaunch keyword. I thought maybe there will be an error which lacks panic, but I don't see it.

[macpijan]

What asks you to press the key? GRUB?

Yes, it looks the same as in the 2nd img in the first message of this issue.

[andyhhp]

Just as I happen to be here, from your Xen log:

(XEN) Failed to bring up CPU 1 (error -5)
(XEN) Failed to bring up CPU 2 (error -5)
(XEN) Failed to bring up CPU 3 (error -5)
(XEN) Failed to bring up CPU 4 (error -5)
(XEN) Brought up 2 CPUs

That looks like a bug handling the APs under TXT.

[krystian-hebel]

I've never seen a case where 2 CPUs would be brought up, it was either all but one, or just one. In most cases this happened after something in ACM went terribly wrong due to misconfiguration in one of the TXT heap structures, and the failure was sticky in a way that even a cold boot didn't resolve, I had to do a full power cycle.

[macpijan]

I have tried reproducing the build from: https://github.com/zarhus/meta-trenchboot/releases/tag/v0.5.0-rc4
and wanted to include txt-suite into the TrenchBoot image as well.

I failed as the branch was not existing anymore. Updated to the latest commit from our release tag: 7ade504

Result now when selecting Xen with TB option:

Enabling slaunch ...
Loading ACMs ...
error: it does not look like SINIT ACM.
error: SINIT ACM does not match platform.
error: SINIT ACM does not match platform.
error: SINIT ACM does not match platform.
error: SINIT ACM does not match platform.
error: SINIT ACM does not match platform.
error: SINIT ACM does not match platform.
error: SINIT ACM does not match platform.
error: SINIT ACM does not match platform.
error: SINIT ACM does not match platform.
Loading Xen ...
Loading Linux ...

Press any key to continue...
ERR: Bootloader shutdown EFI x64 boot services!

[krystian-hebel]

ERR: Bootloader shutdown EFI x64 boot services!

You would have to either bump GRUB or boot in legacy mode.