Unexpected errors in dmesg on VP4670 v2 with 1.2.0

[pkubaj]

Device

VP4670 v2

Dasharo version

1.2.0

Affected component(s) or functionality

Unknown.

Brief summary

Unexpected errors in dmesg on VP4670 v2 with 1.2.0

How reproducible

100%

How to reproduce

sudo dmesg -T -l err,crit,alert,emerg

Expected behavior

No errors.

Actual behavior

x86/cpu: SGX disabled by BIOS.
ath10k_pci 0000:07:00.0: AER:   Error of this Agent is reported first

Screenshots

No response

Additional context

No response

Solutions you've tried

No response

[macpijan]

@mkopec Should we worry about that?
Do you suggest we extend the list of allowed failures, take a closer look into it, or perhaps adjust the dmesg command ?

[mkopec]

The SGX error is harmless and can be ignored. The PCI AER error is a bit more worrying and may be worth a closer look

[macpijan]

@pkubaj was it after the WiFi workaround from Protectli wiki, and the card worked in general?

[pkubaj]

I actually did not have to do any Wifi workaround and all the Wifi tests passed just fine. However, it's reasonable to assume that @Psotas applied it when he prepared the platform.

[macpijan]

Yes, he has, it is a one-time post-installation step.

[pietrushnic]

Does it mean SGX could be supported on this platform? We are looking for verification of SGX in light of HAP disabled ME.

[miczyg1]

It is one of the platforms where SGX is still present. So theoretically yes, it could be supported. @pietrushnic

[pietrushnic]

@marmarek cc

[miczyg1]

@pietrushnic looks like something you would like to bite soon, so: Dasharo/coreboot#598

Apparently the platform was already HAP disabled when tested it (when trying to flash the descriptor with a HAP bit set flashrom said the content is already identical). Looks like it works despite HAP (although did not launch any enclaves)...

[pietrushnic]

@miczyg1 thanks; this is good information and a useful data point.

[pietrushnic]

@miczyg1 shall we consider this closed?

[miczyg1]

Not sure. The atheros error may still show up. Althoguh they are known to cause such errors...

If it was up to me, I would close this issue when PR gets merged.