[4.14][4.15] ACPI Error: Needed type [Reference], found [Integer] ASUS K55VM MOBO

FYI since 4.14 and 4.15 so on kernel releases I have this errors during boot:

[    0.222044] ACPI Error: Needed type [Reference], found [Integer] 00000000cfdd7926 (20170831/exresop-103)
[    0.222055] ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [Store] (20170831/dswexec-461)
[    0.222063] ACPI Error: Method parse/execution failed \_PR.CPU0._PDC, AE_AML_OPERAND_TYPE (20170831/psparse-550)

This not happen on 4.9.x series.

BUG REPORT with logs and details is here

Regards

Hello!
Same happens on a Lenovo T450s:

Feb 15 06:51:40 hk-01 kernel: Error parsing PCC subspaces from PCCT
...
Feb 15 06:51:40 hk-01 kernel: ACPI Error: Needed type [Reference], found [Integer] 000000002c22b965 (20170831/exresop-103)
Feb 15 06:51:40 hk-01 kernel: ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [Store] (20170831/dswexec-461)
Feb 15 06:51:40 hk-01 kernel: ACPI Error: Method parse/execution failed \_PR.CPU0._PDC, AE_AML_OPERAND_TYPE (20170831/psparse-550)

I was told that is due to an “old” bios/uefi despite having the very latest (actually later than whats on the website as they pulled it due to meltdown/spectre patch trouble) ^^

So, please share details of your HW dmesg, dmidecode and most important DECODE ACPI tables in bug report on bugzilla, hope helps Intel Devs find out whats is mess up. :wink:

For prepare AML files first install iasl package, download simply bash script from me and run in separate folder

sudo pacman -S iasl
mkdir -p asl-log && cd asl-log

wget https://raw.githubusercontent.com/FadeMind/b4sh/master/acpi_tables_tools/ACPI.EXTRACT.TABLES.LOG.BASH

Run as normal user

bash ACPI.EXTRACT.TABLES.LOG.BASH

DMESG and DMI save in separated logs:

cd ~ ; sudo dmidecode > dmi.log && dmesg > dmesg.log

ZIP all files (LOG, and extracted ACPI files) and attach to Bug Report. Thanks!

3 Likes

Thanks for the easy to follow step by step =D
I did so, thoug I don’t have (or usually need) a bugzilla account. Mind if you could post my logs?
( https://cloud.hknet.at/index.php/s/kyf3gPyTGAAQaS5 Pass: Forbugzilla1 )

Content of asl-dmi-demesg-logs.zip
   - asl-log [folder]
   - dmesg.log [file]
   - dmi.log [file]

Thanks a lot! TZ

Done. See lastest post on bug report site.

1 Like

I assume you mean 4.14 and 4.15?

1 Like

YEP. Fixed xD Thanks for hint.

1 Like

Thank you very much!

Erik Schmauss 2018-02-15 19:25:14 UTC
Thanks for all of the information. Here’s what’s going on: we have confirmed that executing ASL/AML code like the one I’ve listed in comment #1 results in an error on windows. Also, we have confirmed that we were allowing this code to execute without error in older versions (20160831) but we have made this into an error in more recent versions to match the behavior on windows. Basically, this is a firmware issue…

Erik Schmauss 2018-02-15 20:42:31 UTC
So from our perspective, the two possible next steps are to contact the firmware vendor to correct the firmware or check to see if there are updates for this firmware

2 Likes

Thank you!

The tl;dr is - wont fix, not our error; Nobody will solve it XD

1 Like

WORKAROUND

Edit /etc/default/grub and add in GRUB_CMDLINE_LINUX_DEFAULT line AFTER quiet word these: vga=current loglevel=3 rd.systemd.show_status=auto rd.udev.log_priority=3
Next update grub : sudo update-grub.
Last thing is creating SYSCTL rule:

sudo bash -c "echo ‘kernel.printk = 3 3 3 3’ > /etc/sysctl.d/20-quiet-printk.conf’"

and reboot. This will just HIDE error msgs during boot, still exists in dmesg results.

@Th3Z0ne

4 Likes

Forum kindly sponsored by Bytemark