Re: New ACPI Errors
On 02/13/2018 17:34, Claude Buisson wrote: > On 02/13/2018 22:49, Pete Wright wrote: >> Hello, >> I have started seeing a lot of these messages spam my system log: >> >> ACPI Error: No pointer back to namespace node in package >> 0xf8000f79a080 (20180209/dsargs-472) >> ACPI Error: Method parse/execution failed \134_SB.AC.ADJP, >> AE_AML_INTERNAL (20180209/psparse-677) >> ACPI Error: Method parse/execution failed \134_SB.AC._PSR, >> AE_AML_INTERNAL (20180209/psparse-677) >> >> I noticed this starting from a CURRENT build i installed two weeks >> ago, and still see it from a world/kernel i built last night. two >> questions: >> 1) has anyone else noticed this? >> 2) is this something to worry about? >> >> i can help debug the issue but am not sure where to start poking. >> >> thanks! >> -pete >> > Here I have > > ACPI Error: No pointer back to namespace node in package > 0xf8000171f700 (20180209/dsargs-472) > ACPI Error: AE_AML_INTERNAL, While resolving operands for [OpcodeName > unavailable] (20180209/dswexec-606) > ACPI Error: Method parse/execution failed > \134_PR.CPU0._CST,AE_AML_INTERNAL (20180209/psparse-677) > > with svn 329142 on a Lenovo ThinkCentre M83 > ACPI APIC Table: > > Claude Buisson This problem should be fixed now (r80). Sorry for the delay. Jung-uk Kim signature.asc Description: OpenPGP digital signature
Re: New ACPI Errors
On 02/16/2018 13:54, Pete Wright wrote: On 02/15/2018 13:37, Jung-uk Kim wrote: On 02/13/2018 17:34, Claude Buisson wrote: On 02/13/2018 22:49, Pete Wright wrote: Hello, I have started seeing a lot of these messages spam my system log: ACPI Error: No pointer back to namespace node in package 0xf8000f79a080 (20180209/dsargs-472) ACPI Error: Method parse/execution failed \134_SB.AC.ADJP, AE_AML_INTERNAL (20180209/psparse-677) ACPI Error: Method parse/execution failed \134_SB.AC._PSR, AE_AML_INTERNAL (20180209/psparse-677) I noticed this starting from a CURRENT build i installed two weeks ago, and still see it from a world/kernel i built last night. two questions: 1) has anyone else noticed this? 2) is this something to worry about? i can help debug the issue but am not sure where to start poking. thanks! -pete Here I have ACPI Error: No pointer back to namespace node in package 0xf8000171f700 (20180209/dsargs-472) ACPI Error: AE_AML_INTERNAL, While resolving operands for [OpcodeName unavailable] (20180209/dswexec-606) ACPI Error: Method parse/execution failed \134_PR.CPU0._CST,AE_AML_INTERNAL (20180209/psparse-677) with svn 329142 on a Lenovo ThinkCentre M83 ACPI APIC Table: Claude Buisson I believe you can silence the errors with the attached patch. Please try it and let me know. hrm still getting errors: Feb 16 13:49:45 runner kernel: ACPI Error: No pointer back to namespace node in package 0xf80003c8c080 (20180209/dsargs-472) Feb 16 13:49:45 runner kernel: ACPI Error: Method parse/execution failed \_SB.AC.ADJP, AE_AML_INTERNAL (20180209/psparse-677) Feb 16 13:49:45 runner kernel: ACPI Error: Method parse/execution failed \_SB.AC._PSR, AE_AML_INTERNAL (20180209/psparse-677) here's my diff: diff --git a/sys/contrib/dev/acpica/include/platform/acfreebsd.h b/sys/contrib/dev/acpica/include/platform/acfreebsd.h index 905dffb7a40..df89399a369 100644 --- a/sys/contrib/dev/acpica/include/platform/acfreebsd.h +++ b/sys/contrib/dev/acpica/include/platform/acfreebsd.h @@ -166,6 +166,7 @@ #define ACPI_UINTPTR_T uintptr_t +#define ACPI_IGNORE_PACKAGE_RESOLUTION_ERRORS #define ACPI_USE_DO_WHILE_0 #define ACPI_USE_LOCAL_CACHE #define ACPI_USE_NATIVE_DIVIDE hi there - i was wondering if anyone has taken a look at this issue. I am still seeing these ACPI errors on recent CURRENT systems: ACPI Error: No pointer back to namespace node in package 0xf803e71fff00 (20180313/dsargs-472) ACPI Error: Method parse/execution failed \134_SB.AC.ADJP, AE_AML_INTERNAL (20180313/psparse-677) ACPI Error: Method parse/execution failed \134_SB.AC._PSR, AE_AML_INTERNAL (20180313/psparse-677) I have two amd64 (skylake and kabylake) systems that are exhibiting this behavior and am more than happy to test patches or other things. cheers! -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New ACPI Errors
On 02/15/2018 13:37, Jung-uk Kim wrote: On 02/13/2018 17:34, Claude Buisson wrote: On 02/13/2018 22:49, Pete Wright wrote: Hello, I have started seeing a lot of these messages spam my system log: ACPI Error: No pointer back to namespace node in package 0xf8000f79a080 (20180209/dsargs-472) ACPI Error: Method parse/execution failed \134_SB.AC.ADJP, AE_AML_INTERNAL (20180209/psparse-677) ACPI Error: Method parse/execution failed \134_SB.AC._PSR, AE_AML_INTERNAL (20180209/psparse-677) I noticed this starting from a CURRENT build i installed two weeks ago, and still see it from a world/kernel i built last night. two questions: 1) has anyone else noticed this? 2) is this something to worry about? i can help debug the issue but am not sure where to start poking. thanks! -pete Here I have ACPI Error: No pointer back to namespace node in package 0xf8000171f700 (20180209/dsargs-472) ACPI Error: AE_AML_INTERNAL, While resolving operands for [OpcodeName unavailable] (20180209/dswexec-606) ACPI Error: Method parse/execution failed \134_PR.CPU0._CST,AE_AML_INTERNAL (20180209/psparse-677) with svn 329142 on a Lenovo ThinkCentre M83 ACPI APIC Table: Claude Buisson I believe you can silence the errors with the attached patch. Please try it and let me know. hrm still getting errors: Feb 16 13:49:45 runner kernel: ACPI Error: No pointer back to namespace node in package 0xf80003c8c080 (20180209/dsargs-472) Feb 16 13:49:45 runner kernel: ACPI Error: Method parse/execution failed \_SB.AC.ADJP, AE_AML_INTERNAL (20180209/psparse-677) Feb 16 13:49:45 runner kernel: ACPI Error: Method parse/execution failed \_SB.AC._PSR, AE_AML_INTERNAL (20180209/psparse-677) here's my diff: diff --git a/sys/contrib/dev/acpica/include/platform/acfreebsd.h b/sys/contrib/dev/acpica/include/platform/acfreebsd.h index 905dffb7a40..df89399a369 100644 --- a/sys/contrib/dev/acpica/include/platform/acfreebsd.h +++ b/sys/contrib/dev/acpica/include/platform/acfreebsd.h @@ -166,6 +166,7 @@ #define ACPI_UINTPTR_T uintptr_t +#define ACPI_IGNORE_PACKAGE_RESOLUTION_ERRORS #define ACPI_USE_DO_WHILE_0 #define ACPI_USE_LOCAL_CACHE #define ACPI_USE_NATIVE_DIVIDE -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New ACPI Errors
On 02/13/2018 17:34, Claude Buisson wrote: > On 02/13/2018 22:49, Pete Wright wrote: >> Hello, >> I have started seeing a lot of these messages spam my system log: >> >> ACPI Error: No pointer back to namespace node in package >> 0xf8000f79a080 (20180209/dsargs-472) >> ACPI Error: Method parse/execution failed \134_SB.AC.ADJP, >> AE_AML_INTERNAL (20180209/psparse-677) >> ACPI Error: Method parse/execution failed \134_SB.AC._PSR, >> AE_AML_INTERNAL (20180209/psparse-677) >> >> I noticed this starting from a CURRENT build i installed two weeks >> ago, and still see it from a world/kernel i built last night. two >> questions: >> 1) has anyone else noticed this? >> 2) is this something to worry about? >> >> i can help debug the issue but am not sure where to start poking. >> >> thanks! >> -pete >> > Here I have > > ACPI Error: No pointer back to namespace node in package > 0xf8000171f700 (20180209/dsargs-472) > ACPI Error: AE_AML_INTERNAL, While resolving operands for [OpcodeName > unavailable] (20180209/dswexec-606) > ACPI Error: Method parse/execution failed > \134_PR.CPU0._CST,AE_AML_INTERNAL (20180209/psparse-677) > > with svn 329142 on a Lenovo ThinkCentre M83 > ACPI APIC Table: > > Claude Buisson I believe you can silence the errors with the attached patch. Please try it and let me know. Jung-uk Kim Index: sys/contrib/dev/acpica/include/platform/acfreebsd.h === --- sys/contrib/dev/acpica/include/platform/acfreebsd.h (revision 329340) +++ sys/contrib/dev/acpica/include/platform/acfreebsd.h (working copy) @@ -166,6 +166,7 @@ #define ACPI_UINTPTR_T uintptr_t +#define ACPI_IGNORE_PACKAGE_RESOLUTION_ERRORS #define ACPI_USE_DO_WHILE_0 #define ACPI_USE_LOCAL_CACHE #define ACPI_USE_NATIVE_DIVIDE signature.asc Description: OpenPGP digital signature
Re: New ACPI Errors
On 02/13/2018 22:49, Pete Wright wrote: Hello, I have started seeing a lot of these messages spam my system log: ACPI Error: No pointer back to namespace node in package 0xf8000f79a080 (20180209/dsargs-472) ACPI Error: Method parse/execution failed \134_SB.AC.ADJP, AE_AML_INTERNAL (20180209/psparse-677) ACPI Error: Method parse/execution failed \134_SB.AC._PSR, AE_AML_INTERNAL (20180209/psparse-677) I noticed this starting from a CURRENT build i installed two weeks ago, and still see it from a world/kernel i built last night. two questions: 1) has anyone else noticed this? 2) is this something to worry about? i can help debug the issue but am not sure where to start poking. thanks! -pete Here I have ACPI Error: No pointer back to namespace node in package 0xf8000171f700 (20180209/dsargs-472) ACPI Error: AE_AML_INTERNAL, While resolving operands for [OpcodeName unavailable] (20180209/dswexec-606) ACPI Error: Method parse/execution failed \134_PR.CPU0._CST,AE_AML_INTERNAL (20180209/psparse-677) with svn 329142 on a Lenovo ThinkCentre M83 ACPI APIC Table: Claude Buisson ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
New ACPI Errors
Hello, I have started seeing a lot of these messages spam my system log: ACPI Error: No pointer back to namespace node in package 0xf8000f79a080 (20180209/dsargs-472) ACPI Error: Method parse/execution failed \134_SB.AC.ADJP, AE_AML_INTERNAL (20180209/psparse-677) ACPI Error: Method parse/execution failed \134_SB.AC._PSR, AE_AML_INTERNAL (20180209/psparse-677) I noticed this starting from a CURRENT build i installed two weeks ago, and still see it from a world/kernel i built last night. two questions: 1) has anyone else noticed this? 2) is this something to worry about? i can help debug the issue but am not sure where to start poking. thanks! -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
