Project

General

Profile

Actions
Copy link

Bug #516

closed

brya/var/crota: `ACPI BIOS Error (bug): Failure creating named object [\_SB.MPTS], AE_ALREADY_EXISTS (20210730/dswload2-327)`

Added by Paul Menzel about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
none
Start date:
12/02/2023
Due date:
% Done:

0%

Estimated time:
Affected versions:
4.18
Needs backport to:
Affected hardware:
google/brya
Affected OS:

Description

On the Dell Latitude 5430 Chromebook (brya/var/crota) with ChromeOS, Linux 5.15.133 reports an ACPI error:

[    0.000000] Linux version 5.15.133-20573-g839a3133d611 (chrome-bot@chromeos-release-builder-us-central1-a-x32-6-ibti) (Chromium OS 17.0_pre498229-r6 clang version 17.0.0 (/mnt/host/source/src/third_party/llvm-project 14f0776550b5a49e1c42f49a00213f7f3fa047bf), LLD 17.0.0) #1 SMP PREEMPT Sun Nov 26 18:55:03 PST 2023
2023-12-01T11:43:58.591525Z INFO kernel: [    0.000000] Command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure drm.trace=0x106 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 6348800 verity payload=PARTUUID=12e8cf21-bcc0-49b5-85bb-56fb8102f7d4/PARTNROFF=1 hashtree=PARTUUID=12e8cf21-bcc0-49b5-85bb-56fb8102f7d4/PARTNROFF=1 hashstart=6348800 alg=sha256 root_hexdigest=4ad313ce4c441485f2be87533efe22a0d8b61bffb78260d17ccd2672e7edb538 salt=8051d68355ccfca99de821939b957ff34d38b866a2951a595e4c0613a1c51f97" noinitrd vt.global_cursor_default=0 kern_guid=12e8cf21-bcc0-49b5-85bb-56fb8102f7d4 add_efi_memmap noresume i915.modeset=1 ramoops.ecc=1 tpm_tis.force=0 intel_pmc_core.warn_on_s0ix_failures=1 i915.enable_guc=3 i915.enable_dc=4 xdomain=0 swiotlb=65536 intel_iommu=on i915.enable_psr=1
[…]
[    0.000000] DMI: Google Crota/Crota, BIOS Google_Crota.14505.456.0 04/21/2023
[…]
[    0.146114] ACPI BIOS Error (bug): Failure creating named object [\_SB.MPTS], AE_ALREADY_EXISTS (20210730/dswload2-327)
[    0.146117] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
[…]
Actions
Copy link
 #1

Updated by Matt DeVillier about 1 year ago

hi Paul,

can you check if this is exists with upstream coreboot as well? It's somewhat hard to debug Google's downstream firmware given it's branched off. If the issue doesn't exist upstream, I'd recommend filing an issue at https://issuetracker.google.com/issues.

Actions
Copy link
 #2

Updated by Reka Norman about 1 year ago

This should be fixed by https://review.coreboot.org/c/coreboot/+/70146, which was cherry-picked to the brya firmware branch a couple of months ago: https://chromium-review.googlesource.com/c/chromiumos/third_party/coreboot/+/4891571

Actions
Copy link
 #3

Updated by Paul Menzel about 1 year ago

  • Status changed from New to Resolved
  • Affected hardware set to google/brya
  • Affected versions 4.18 added

Reka, thank you for pointing to commit 1d49d3e40b1b (mb/google/brya: Don't add MPTS to both DSDT and SSDT).

Is there a way on ChromeOS to update to the latest ChromeOS firmware branch for this device?

Actions
Copy link
 #4

Updated by Reka Norman about 1 year ago

No, not without building your own firmware, etc. Via official processes you can only get the currently pinned firmware version. This will be updated at some point, but only for example when there's a serious bug, so it can take around a few months to a year.

Actions
Copy link

Also available in: Atom PDF