Unexpectid errors in dmesg | Protectli VP2420 | v1.2.1 rc4

[wiktormowinski]

Component

Dasharo firmware

Device

Protectli VP2420

Dasharo version

v1.2.1 rc4

Dasharo Tools Suite version

Test case ID

STB002.001

Brief summary

Platform encounters a few unlisted errors during boot

How reproducible

No response

How to reproduce

run STB002.001 test case on protectli 2420 with dasharo 1.2.1 rc4

Expected behavior

should be "errorless" or at least with expected errors

Actual behavior

log:

dasharo-performance.zip

Screenshots

No response

Additional context

No response

Solutions you've tried

No response

[miczyg1]

'Bluetooth: hci0: Malformed MSFT vendor event: 0x02',
 'tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead',

These two appear almost always. I have no idea what Linux expects the TP interrupt to be configured like in ACPI. Whatever I pass either Linux is happy but Windows isn;t and vice versa.

Bluetooth: hci0: No support for _PRR ACPI method

There are patches in upstream coreboot for that, so we can possibly get rid of this error.

'iwlwifi 0000:00:14.3: WRT: Invalid buffer destination'
'iwlwifi 0000:00:14.3: Not valid error log pointer 0x0027B0C0 for RT uCode'

These are clearly Intel WiFi issues inside their firmware blobs. Not sure if we can do anything about it. Future Linux kernel versions and the WiFi blobs may solve it eventually.

'i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy component didn't bind within the expected timeout"
'i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy handler failed to init'

Looks like some graphics problem, not sure what it is. Will need further investigation.

proc_thermal_pci 0000:00:04.0: error: proc_thermal_add, will continue

Looks like DPTF device incorrectly set to be visible in OS.

However, if I understand the test correctly, the above errors are the allowed ones? And the actual errors are:

'ata1.00: Read log 0x00 page 0x00 failed, Emask 0x4',
 'ath10k_pci 0000:05:00.0: wmi unified ready event not received',
 'ath10k_pci 0000:05:00.0: could not init core (-110)',
 'ath10k_pci 0000:05:00.0: could not probe fw (-110)'

The ath10k PCI driver is for WiFi cards and there is an issue with the WiFi card blob in Linux: https://kb.protectli.com/kb/wifi-on-the-vault/#articleTOC_5 (not sure how many times I have explained it already).

'ata1.00: Read log 0x00 page 0x00 failed, Emask 0x4

This looks weird. Not sure what it is, but related to SATA disk, if any is connected.