You are not logged in.
Pages: 1
Basic info:
Mainboard: ASRock B150M Pro4S
System: Arch Linux x86_64 (of course)
My box keeps bothering some ACPI Errors:
8月 05 10:31:34 esper kernel: ACPI Error: 1 table load failures, 5 successful (20170303/tbxfload-246)
8月 05 10:31:34 esper kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table (20170303/tbxfload-228)
8月 05 10:31:34 esper kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170303/psobject-241)
8月 05 10:31:34 esper kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170303/dswload-210)
8月 05 10:31:34 esper kernel: ACPI: Core revision 20170303Sometimes, when the system tries to restore from sleeping mode, it might halt there without any response.
And I also encountered errors like this:
[ 7105.537203] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
[ 7105.538100] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[ 7105.538102] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff88026c8d64b0), AE_NOT_FOUND (20160831/psparse-543)I tried to follow the wikis ACPI modules and DSDT to disassembly and recompile my dsdt.dsl, but failed with these Errors:
Intel ACPI Component Architecture
ASL+ Optimizing Compiler/Disassembler version 20170303
Copyright (c) 2000 - 2017 Intel Corporation
Compiler aborting due to parser-detected syntax error(s)
dsdt.dsl 14228: Arg1
Error 6126 - ^ syntax error, unexpected PARSEOP_ARG1
dsdt.dsl 17661: }
Error 6126 - ^ syntax error, unexpected '}'
dsdt.dsl 34445:
Error 6126 - syntax error, unexpected $end and premature End-Of-File
ASL Input: dsdt.dsl - 34445 lines, 1081231 bytes, 16531 keywords
Hex Dump: dsdt.hex - 230 bytes
Compilation complete. 3 Errors, 0 Warnings, 0 Remarks, 0 OptimizationsThe dsdt.dsl also gives me this warning:
/*
* iASL Warning: There were 17 external control methods found during
* disassembly, but only 0 were resolved (17 unresolved). Additional
* ACPI tables may be required to properly disassemble the code. This
* resulting disassembler output file may not compile because the
* disassembler did not know how many arguments to assign to the
* unresolved methods. Note: SSDTs can be dynamically loaded at
* runtime and may or may not be available via the host OS.
....Then, I stuck there. ![]()
Offline
What machine have you? I have the same message with an ASUS P8B75M LX plus. But although I have these errors in dmesg, I see no problem with acpi. Things works as they should. Are you experiencing an issue with acpi? I thing this is harmless. This is probably due to a not compliant ACPI; for the manufacturers as long as Windows works, it is compliant.
Offline
Pages: 1