Bug 198051 - ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload-210)
Summary: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUN...
Alias: None
Product: ACPI
Classification: Unclassified
Component: ACPICA-Core (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Erik Kaneda
Depends on:
Reported: 2017-11-30 21:53 UTC by Mike Lothian
Modified: 2018-01-23 18:15 UTC (History)
5 users (show)

See Also:
Kernel Version: All
Regression: No
Bisected commit-id:

Dmesg (66.44 KB, text/plain)
2017-11-30 21:53 UTC, Mike Lothian
Output of commands (95.44 KB, text/plain)
2017-11-30 21:53 UTC, Mike Lothian
Compressed decoded acpidump files (327.76 KB, application/x-xz)
2017-11-30 21:56 UTC, Mike Lothian
Patch to enable parse_table_as_term_list (874 bytes, application/mbox)
2018-01-22 19:30 UTC, Erik Kaneda
Dmesg with Patch (71.42 KB, text/plain)
2018-01-23 00:22 UTC, Mike Lothian

Description Mike Lothian 2017-11-30 21:53:06 UTC
Created attachment 260969 [details]

I get the following errors during boot up:

[    0.000000] ACPI: Core revision 20170831
[    0.000000] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload-210)
[    0.000000] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252)
[    0.000000] ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp10) while loading table (20170831/tbxfload-228)
[    0.000000] ACPI Error: 1 table load failures, 10 successful (20170831/tbxfload-246)

I followed the instructions at https://01.org/linux-acpi/utilities
Comment 1 Mike Lothian 2017-11-30 21:53:31 UTC
Created attachment 260971 [details]
Output of commands
Comment 2 Mike Lothian 2017-11-30 21:56:35 UTC
Created attachment 260973 [details]
Compressed decoded acpidump files
Comment 3 Mike Lothian 2017-12-11 11:33:17 UTC
I think I assigned this to the wrong  Component
Comment 4 Erik Kaneda 2017-12-13 18:41:20 UTC
We've seen code like this before and it has to do with the firmware. RHUB.HS11 is being declared as a device object in a firmware table called the DSDT based on some conditional expression like so:

if (Expr)
    Device (HS11){...}

This means that HS11 is created only when Expr evaluates to true.
The scope operator opens the scope of a device (like HS11). In the SSDT4 firmware table, the ASL opens a scope under HS11 without any conditional expression:

Scope (HS11){...}

The message you see is a result of the Expr evaluating to 0 and failing to create HS11. By the time Scope (HS11) {.. is executed, the linux ACPI interpreter returns an error saying that this object does not exist.
Comment 5 Mike Lothian 2017-12-14 16:28:18 UTC
Is this something I need to worry about or maybe I should ask can it be fixed?
Comment 6 Erik Kaneda 2017-12-14 17:46:58 UTC
It could be some sort of BIOS option that could fix this but other than that, you may want to talk to the firmware vendor to see if they have newer firmware.
Comment 7 Erik Kaneda 2018-01-05 22:55:52 UTC
Actually, this could be an issue with module-level code. We are in the process of fixing this. Linking to this bug https://bugs.acpica.org/show_bug.cgi?id=963
As of now, we execute if statements at the root scope after all tables have been loaded. So this code

if (Expr)
    Device (HS11){...}

gets executed after

Scope (HS11){...}

We are working on changing the order so that the the if statements get executed in the correct order. If we have the correct order of execution and Expr evaluates to a non-zero value, Device HS11 will be declared and fix this error:

[    0.000000] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload-210)
Comment 8 Mike Lothian 2018-01-22 14:25:08 UTC
Is there a way to test AcpiGbl_ParseTableAsTermList enabled?
Comment 9 Erik Kaneda 2018-01-22 19:30:34 UTC
Created attachment 273793 [details]
Patch to enable parse_table_as_term_list
Comment 10 Mike Lothian 2018-01-23 00:22:51 UTC
Created attachment 273799 [details]
Dmesg with Patch

So I'd say that's an improvement but there's still a lot of these type of messages:

[    0.021138] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381)
[    0.021151] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381)
[    0.021162] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381)
[    0.021174] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381)

I was also hoping these ACPI errors might have been related to why my USB-C connector doesn't work under Linux
Comment 11 Erik Kaneda 2018-01-23 18:14:47 UTC
Hi Mike,

We are currently working on a fix for this issue. I'm going to mark this as a duplicate and you can track the issue here: https://bugs.acpica.org/show_bug.cgi?id=963

Note You need to log in before you can comment on or make changes to this bug.