- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hello,
CRB(with E3845), the firmware built from Intel Firmware Engine(IFE), and 4.2.3 kernel showed ACPI Errors below while COTS(with E3845), its firmware, and 4.2.3 kernel(very same kernel) didn't show any ACPI Error. What are these errors? How can I fix?
[ 0.111143] ACPI Error: [TPME] Namespace lookup failure, AE_NOT_FOUND (20150619/psargs-359)
[ 0.111154] ACPI Error: Method parse/execution failed [\_SB_.TPM_._STA] (Node ffff8800768917a8), AE_NOT_FOUND (20150619/psparse-536)
[ 0.111193] ACPI Error: [TPME] Namespace lookup failure, AE_NOT_FOUND (20150619/psargs-359)
[ 0.111201] ACPI Error: Method parse/execution failed [\_SB_.TPM_._STA] (Node ffff8800768917a8), AE_NOT_FOUND (20150619/psparse-536)
[ 0.132503] ACPI Error: [TPME] Namespace lookup failure, AE_NOT_FOUND (20150619/psargs-359)
[ 0.132514] ACPI Error: Method parse/execution failed [\_SB_.TPM_._STA] (Node ffff8800768917a8), AE_NOT_FOUND (20150619/psparse-536)
[ 0.147881] ACPI Error: [TPME] Namespace lookup failure, AE_NOT_FOUND (20150619/psargs-359)
[ 0.147891] ACPI Error: Method parse/execution failed [\_SB_.TPM_._STA] (Node ffff8800768917a8), AE_NOT_FOUND (20150619/psparse-536)
- 태그:
- Firmware
링크가 복사됨
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
I will forward this to the team for investigation. Can you also run the LUV OS Image from 01.org and see if you get a similar error?
https://01.org/linux-uefi-validation
You may see other warnings/errors, but I'm primarily interested in seeing if the LUV kernel has the same error. Thanks.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Jong: please verify the version of the MinnowBoard Max project you are using with Intel Firmware Engine (1.0.0, 2.0.0 or 2.1.0)?
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hello Brain,
According to the 2.1.0 release note(http://firmware.intel.com/sites/default/files/Release%20Notes%20MinnowBoard%20Max%202.1.0.pdf) it looks like only two changes(see below). Other than Branding is there difference between 2.0.0 and 2.1.0?
NEW FEATURES AND CHANGES
1. See New Features and Changes for release 2.0.0
2. This release has changes for Trademark and Branding strings.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hello Brian
LUV kernel has the same errors. See below. I've attached the full serial console output, luv-live-imagelog.txt. What are these errors? How can I fix?
[ 1.221189] ACPI Error: [TPME] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
[ 1.230678] ACPI Error: Method parse/execution failed [\_SB_.TPM_._STA] (Node ffff8800764987a8), AE_NOT_FOUND (20150410/psparse-536)
[ 1.244364] ACPI Error: [TPME] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
[ 1.253804] ACPI Error: Method parse/execution failed [\_SB_.TPM_._STA] (Node ffff8800764987a8), AE_NOT_FOUND (20150410/psparse-536)
[ 1.645060] ACPI Error: [TPME] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
[ 1.654528] ACPI Error: Method parse/execution failed [\_SB_.TPM_._STA] (Node ffff8800764987a8), AE_NOT_FOUND (20150410/psparse-536)
[ 2.258558] ACPI Error: [TPME] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
[ 2.268047] ACPI Error: Method parse/execution failed [\_SB_.TPM_._STA] (Node ffff8800764987a8), AE_NOT_FOUND (20150410/psparse-536)
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hello Brian,
While looking at the luv-live-imagelog.txt(attached in previous one), I found a critical failure like below:
summary ;SUM Critical failures: 1
summary ;SUM method: Detected error 'Not found' when evaluating '\_SB_.TPM_._STA'.
It looks like related to the original issue based on the "\_SB_.TPM_._STA". CRB doesn't have TPM. Can I disble TPM in IFE? If yes, how?
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hello Brian,
For your information I tired 0.84 firmware from https://firmware.intel.com/projects/minnowboard-max on both CRB(RC10) and MinnowBoard MAX. None of those had the '\_SB_.TPM_._STA' error. I think the firmware built from the Intel Firmware Engine had some problem. What do you think?
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
We're investigating the 0.84 codebase differences already. There may be some delay on our end due to the Christmas holiday, but I'll keep you posted. Thanks.