dasharo-issues
dasharo-issues copied to clipboard
STB002.001 encounters unlisted error
Device
MinnowBoard Turbot B41
RTE version
OSFV version
branch: minnow-update
Affected component(s) or functionality
No response
Brief summary
STB002.001 encounters unlisted error regarding bluetooth
How reproducible
happens everytime
How to reproduce
dmesg -t -l err,crit,alert,emerg
Expected behavior
Pass
Actual behavior
an error occurs:
pwm-lpss 80860F09:00: can't request region for resource [mem 0x00000000-0x00000fff]: 'Bluetooth: hci0: Malformed MSFT vendor event: 0x02' does not contain 'tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead'
Link to screenshots or logs
Additional context
No response
Solutions you've tried
No response
'Bluetooth: hci0: Malformed MSFT vendor event: 0x02 standard thing, appears on almost all platforms.
tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead' - TPM is not supported, not sure why it is there.
pwm-lpss 80860F09:00: can't request region for resource [mem 0x00000000-0x00000fff] check and coreboot assigns the resources for this device properly. not sure why Linux complains.
the problems related to this test also occur on Protectli ADL (VP6670, VP6650)
This carries over to a newer dev build, on a different unit
on VP3210 Dasharo v0.9.0 rc4 there is Serial bus multi instantiate pseudo device driver INT3515:00: error -ENXIO: IRQ index 1 not found error
platform-stability.robot_log-unlisted_dmesg_err.zip
Fixed in https://github.com/Dasharo/coreboot/pull/594
Serial bus multi instantiate pseudo device driver INT3515:00: Instantiated 2 I2C devices.
ok, it turns out vp2430 has the same problem
Had the same problem on rc1. It has already been fixed, as wrote above.
Issue exists in Dasharo 1.2.1 tested on VP2420.
Issue exists in Dasharo v0.9.0 rc10 tested on VP3210.
PRs for TPM interrupt error:
https://github.com/Dasharo/coreboot/pull/641 https://github.com/Dasharo/open-source-firmware-validation/pull/751
Fix PR is not merged, issue reproduced on Protectli VP6670, Dasharo v0.9.2-rc1
Issue exists in Dasharo v0.9.2 rc1 tested on VP6650.
This issue pretty much belongs here as well: https://github.com/Dasharo/dasharo-issues/issues/817
Issue not reproduced on Dasharo v0.9.0, Protectli VP3210.
Instead:
snd_hda_intel 0000:00:1f.3: Unknown capability 0
Bluetooth: hci0: Failed to send body at 4 of 1857 (-110)
ath10k_pci 0000:03:00.0: wmi unified ready event not received
ath10k_pci 0000:03:00.0: could not init core (-110)
ath10k_pci 0000:03:00.0: could not probe fw (-110)
ath10k part is related to failed firmware downgrade procedure, which seems to be no longer valid on Ubuntu 24.
@matmacieje by downgrade procedure, do you mean https://kb.protectli.com/kb/wifi-on-the-vault/?intsrc=eu#articleTOC_5?
on VP6650 0.9.3-rc1 there is an error with:
genirq: Setting trigger mode 8 for irq 223 failed (intel_gpio_irq_type+0x0/0x160)
Also a problem on ASRock SPC741D8:
ubuntu@3mdeb:~$ sudo dmesg -t -l err,crit,alert,emerg
x86/cpu: SGX disabled or unsupported by BIOS.
ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0], AE_NOT_FOUND (20240827/dswload2-162)
ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20240827/psobject-220)
usb usb1-port12: over-current condition
usb usb1-port14: over-current condition
snd_hda_intel 0000:00:1f.3: no codecs found!
The ACPI errors are most likely what causes Windows to immediately BSOD with BIOS_ACPI_ERROR - https://github.com/Dasharo/dasharo-issues/issues/1598
Errors still appear in dmesg onASRock SPC741D8 v0.9.0-rc4
'x86/cpu: SGX disabled or unsupported by BIOS.',
'ERROR: Unable to locate IOAPIC for GSI 255',
'usb usb1-port12: over-current condition',
'usb usb1-port14: over-current condition',
'snd_hda_intel 0000:00:1f.3: no codecs found!
Protectli VP2445 (with VP2440 0.9.0 rom) has:
snd_hda_intel 0000:00:1f.3: Unknown capability 0
Protectli VP66xx 0.9.3-rc1:
genirq: Setting trigger mode 8 for irq 223 failed (intel_gpio_irq_type+0x0/0x160)
Protectli VP4651 v1.2.1-rc1
x86/cpu: SGX disabled or unsupported by BIOS.
Protectli VP4651 v1.2.1-rc1 x86/cpu: SGX disabled or unsupported by BIOS.
This test case was also not in scope of the old 1.2.0 release. We may also add it to known issues for a possible fix in the future release.