Bug #1584407 “ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace ...” : Bugs : linux package : Ubuntu

Revision history for this message

SunBear (sunbear-c22) wrote on 2016-05-22:

#1

AlsaInfo.txt Edit (65.8 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (422 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (65.1 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.2 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (8.1 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (10.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (572 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (8.9 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (334 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (4.7 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (7.0 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (27.8 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (218.3 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (87.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Brad Figg (brad-figg) wrote on 2016-05-22: Status changed to Confirmed

#2

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

SunBear (sunbear-c22) wrote on 2016-05-22: Re: Ubuntu 16.04 LTS --> Kernal --> ACPI Errors: Namespace lookup failure and 1 table load failures

#3

acpidump.out files e.g. DSDT, SSDTs, etc Edit (356.1 KiB, application/x-tar)

I executed instructions 1 to 3 of https://01.org/linux-acpi/utilities in an attempt to understand the failure msg mentioned above. The generated files from instructions 1 to 3 are attached. SSDT 2,3,4 & 6 were dissembled with reference to DSDT, e.g. $ iasl -e dsdt.dat -d ssdt2.dat, and DSDT.dat was dissembled with reference to SSDT*.dat.

My findings:

1. from acpidump.out, SB_PCI0XHC_RHUBHS11 is refer to in the 5th SSDT table.
  0340: 88 55 48 53 44 0A 09 00 0A 0A 10 3C 5C 2F 05 5F .UHSD......<\/._
  0350: 53 42 5F 50 43 49 30 58 48 43 5F 52 48 55 42 48 SB_PCI0XHC_RHUBH
  0360: 53 31 31 14 0C 5F 55 50 43 00 A4 47 55 50 43 01 S11.._UPC..GUPC.
  0370: 14 16 5F 50 4C 44 00 A4 47 50 4C 44 83 88 55 48 .._PLD..GPLD..UH
  0380: 53 44 0A 0A 00 0A 0B 10 3C 5C 2F 05 5F 53 42 5F SD......<\/._SB_

2.From SSDT5.dat, this file contains instructions for INTEL Table ID "xh_rvp08". It seems to be instructions for all \_SB.PCI0.XHC.RHUB devices. Specifically for \_SB.PCI0.XHC.RHUB.HS11, it is to return information concerning the USB Port Capabilities _UPC and Physical Location of Device _PLD (details of these is given in http://www.acpi.info/DOWNLOADS/ACPI_5_Errata%20A.pdf) :
    Scope (\_SB.PCI0.XHC.RHUB.HS11)
    {
        Method (_UPC, 0, NotSerialized) // _UPC: USB Port Capabilities
        {
            Return (GUPC (One))
        }

        Method (_PLD, 0, NotSerialized) // _PLD: Physical Location of Device
        {
            Return (GPLD (DerefOf (UHSD [0x0A]), 0x0B))
        }
    }

3. During $ iasl -e ssdt*.dat -d dsdt.dat, the resulting file dsdt.dsl warned:
     * iASL Warning: There were 19 external control methods found during
     * disassembly, but only 10 were resolved (9 unresolved).
   I tried $ iasl -e ssdt*.dat facp.dat -d dsdt.dat, because facp.dat was the only other aml type file provided by acpidump, by this command created a lot ACPI ERRORs and finally resulted in "Segmentation fault (core dumped)".
   There is a command to cause the objects defined in HS11 to be created relative to a new location _SB.PCI0.XHC.RHUB in the namespace under certain condition.
    If (PCHV () == SPTH)
    {
        Scope (_SB.PCI0.XHC.RHUB)
        {
            Device (HS11)
            {
                Name (_ADR, 0x0B) // _ADR: Address
            }

4. "$ iasl -sa dsdt.dsl" reported 3 errors.

Intel ACPI Component Architecture
ASL+ Optimizing Compiler version 20160422-64
Copyright (c) 2000 - 2016 Intel Corporation

Compiler aborting due to parser-detected syntax error(s)
dsdt.dsl 14493: Arg1
Error 6126 - ^ syntax error, unexpected PARSEOP_ARG1

dsdt.dsl 17932: }
Error 6126 - ^ syntax error, unexpected '}'

dsdt.dsl 33570:
Error 6126 - syntax error, unexpected $end and premature End-Of-File

ASL Input: dsdt.dsl - 33570 lines, 1067589 bytes, 16115 keywords
ASM Source: dsdt.asm - 193 bytes

Compilation complete. 3 Errors, 0 Warnings, 0 Remarks, 0 Optimizations

I executed instructions 1 to 3 of https://01.org/linux-acpi/utilities in an attempt to understand the failure msg mentioned above. The generated files from instructions 1 to 3 are attached. SSDT 2,3,4 & 6 were dissembled with reference to DSDT, e.g. $ iasl -e dsdt.dat -d ssdt2.dat, and DSDT.dat was dissembled with reference to SSDT*.dat.

My findings:

1. from acpidump.out, SB_PCI0XHC_RHUBHS11 is refer to in the 5th SSDT table.
  0340: 88 55 48 53 44 0A 09 00 0A 0A 10 3C 5C 2F 05 5F  .UHSD......<\/._
  0350: 53 42 5F 50 43 49 30 58 48 43 5F 52 48 55 42 48  SB_PCI0XHC_RHUBH
  0360: 53 31 31 14 0C 5F 55 50 43 00 A4 47 55 50 43 01  S11.._UPC..GUPC.
  0370: 14 16 5F 50 4C 44 00 A4 47 50 4C 44 83 88 55 48  .._PLD..GPLD..UH
  0380: 53 44 0A 0A 00 0A 0B 10 3C 5C 2F 05 5F 53 42 5F  SD......<\/._SB_

2.From SSDT5.dat, this file contains instructions for INTEL Table ID "xh_rvp08". It seems to be instructions for all \_SB.PCI0.XHC.RHUB devices. Specifically for \_SB.PCI0.XHC.RHUB.HS11, it is to return information concerning the USB Port Capabilities _UPC and Physical Location of Device _PLD (details of these is given in http://www.acpi.info/DOWNLOADS/ACPI_5_Errata%20A.pdf) : 
    Scope (\_SB.PCI0.XHC.RHUB.HS11)
    {
        Method (_UPC, 0, NotSerialized)  // _UPC: USB Port Capabilities
        {
            Return (GUPC (One))
        }

Method (_PLD, 0, NotSerialized)  // _PLD: Physical Location of Device
        {
            Return (GPLD (DerefOf (UHSD [0x0A]), 0x0B))
        }
    }

3. During $ iasl -e ssdt*.dat -d dsdt.dat, the resulting file dsdt.dsl warned:
     * iASL Warning: There were 19 external control methods found during
     * disassembly, but only 10 were resolved (9 unresolved). 
   I tried $ iasl -e ssdt*.dat facp.dat -d dsdt.dat, because facp.dat was the only other aml type file provided by acpidump, by this command created a lot ACPI ERRORs and finally resulted in "Segmentation fault (core dumped)".
   There is a command to cause the objects defined in HS11 to be created relative to a new location _SB.PCI0.XHC.RHUB in the namespace under certain condition.
    If (PCHV () == SPTH)
    {
        Scope (_SB.PCI0.XHC.RHUB)
        {
            Device (HS11)
            {
                Name (_ADR, 0x0B)  // _ADR: Address
            }

4. "$ iasl -sa dsdt.dsl" reported 3 errors.

Intel ACPI Component Architecture
ASL+ Optimizing Compiler version 20160422-64
Copyright (c) 2000 - 2016 Intel Corporation

Compiler aborting due to parser-detected syntax error(s)
dsdt.dsl  14493:                     Arg1
Error    6126 -                        ^ syntax error, unexpected PARSEOP_ARG1

dsdt.dsl  17932:         }
Error    6126 -         ^ syntax error, unexpected '}'

dsdt.dsl  33570: 
Error    6126 - syntax error, unexpected $end and premature End-Of-File

ASL Input:     dsdt.dsl - 33570 lines, 1067589 bytes, 16115 keywords
ASM Source:    dsdt.asm - 193 bytes

Compilation complete. 3 Errors, 0 Warnings, 0 Remarks, 0 Optimizations

penalvch (penalvch) on 2016-05-22

tags:	added: bios-outdated-1703
Changed in linux (Ubuntu):
importance:	Undecided → Low
status:	Confirmed → Incomplete

Revision history for this message

SunBear (sunbear-c22) wrote on 2016-05-23:

#5

ACPI_Z170M-PLUS-ASUS-1803.tar.gz Edit (377.7 KiB, application/x-tar)

Christopher,

I have updated the bios with Z170M-PLUS-ASUS-1803.CAP.
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
1803
05/09/2016

The same ACPI failures still appears in my syslog. See below. Thus, the updated bios did not fix the failures/bugs.

May 23 10:43:10 Eliot kernel: [ 0.000022] ACPI: Core revision 20150930
May 23 10:43:10 Eliot kernel: [ 0.017217] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)
May 23 10:43:10 Eliot kernel: [ 0.017220] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20150930/psobject-227)
May 23 10:43:10 Eliot kernel: [ 0.017248] ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table (20150930/tbxfload-193)
May 23 10:43:10 Eliot kernel: [ 0.022535] ACPI Error: 1 table load failures, 8 successful (20150930/tbxfload-214)

I ran the same acpidump commands and got the same findings, other than ssdt6.dat now contains the instructions to return information concerning the USB Port Capabilities _UPC and Physical Location of Device _PLD of \_SB.PCI0.XHC.RHUB.HS11 instead of ssdt5.dat and there are now 12 ssdt files instead of 7.

Like to clarify that I created a new report because I was asked to.

What is the next course of action to fix this issue?

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

SunBear (sunbear-c22) wrote on 2016-05-23:

#6

Download full text (6.8 KiB)

Christoper,

I reviewed my syslog concerning all Kernel-->ACPI logs via:
cat /var/log/syslog | grep kernel | grep ACPI

I have 2 questions and hope you can help me understand:

1. ACPI loaded the 8 SSDT tables. I assume these equate to the ssdt1.dat to ssdt8.dat files obtained from acpidump. However, ssdt9.dat to ssdt12.dat were not shown to be loaded. Why did it not report 4 table load failures but 1 in the ACPI Error? Below are the relevant tables reported in my syslogs?

May 23 09:35:47 Eliot kernel: [ May 23 09:35:47 Eliot kernel: [ May 23 09:35:47 Eliot kernel: [ May 23 09:35:47 Eliot kernel: [ May 23 09:35:47 Eliot kernel: [ May 23 09:35:47 Eliot kernel: [ May 23 09:35:47 Eliot kernel: [ May 23 09:35:47 Eliot kernel: [ May 23 09:35:47 Eliot kernel: [ May 23 09:35:47 Eliot kernel: [ May 23 09:35:47 Eliot kernel: [ May 23 09:35:47 Eliot kernel: [ May 23 09:35:47 Eliot kernel: [ May 23 09:35:47 Eliot kernel: [ May 23 09:35:47 Eliot kernel: [ May 23 09:35:47 Eliot kernel: [ May 23 09:35:47 Eliot kernel: [ May 23 09:35:47 Eliot kernel: [ May 23 09:35:47 Eliot kernel: [ May 23 09:35:47 Eliot kernel: [ May 23 09:35:47 Eliot kernel: [ May 23 09:35:47 Eliot kernel: [ May 23 09:35:47 Eliot kernel: [ 0.000000] ACPI: Early table checksum verification disabled
0.000000] ACPI: RSDP 0x00000000CDD39000 000024 (v02 ALASKA)
0.000000] ACPI: XSDT 0x00000000CDD390A0 0000BC (v01 ALASKA A M I 01072009 AMI 00010013)
0.000000] ACPI: FACP 0x00000000CDD5CB78 00010C (v05 ALASKA A M I 01072009 AMI 00010013)
0.000000] ACPI: DSDT 0x00000000CDD391F8 02397B (v02 ALASKA A M I 01072009 INTL 20120913)
0.000000] ACPI: FACS 0x00000000D751BF80 000040
0.000000] ACPI: APIC 0x00000000CDD5CC88 0000BC (v03 ALASKA A M I 01072009 AMI 00010013)
0.000000] ACPI: FPDT 0x00000000CDD5CD48 000044 (v01 ALASKA A M I 01072009 AMI 00010013)
0.000000] ACPI: FIDT 0x00000000CDD5CD90 00009C (v01 ALASKA A M I 01072009 AMI 00010013)
0.000000] ACPI: MCFG 0x00000000CDD5CE30 00003C (v01 ALASKA A M I 01072009 MSFT 00000097)
0.000000] ACPI: HPET 0x00000000CDD5CE70 000038 (v01 ALASKA A M I 01072009 AMI. 0005000B)
0.000000] ACPI: SSDT 0x00000000CDD5CEA8 00036D (v01 SataRe SataTabl 00001000 INTL 20120913)
0.000000] ACPI: LPIT 0x00000000CDD5D218 000094 (v01 INTEL SKL 00000000 MSFT 0000005F)
0.000000] ACPI: SSDT 0x00000000CDD5D2B0 000248 (v02 INTEL sensrhub 00000000 INTL 20120913)
0.000000] ACPI: SSDT 0x00000000CDD5D4F8 002BAE (v02 INTEL PtidDevc 00001000 INTL 20120913)
0.000000] ACPI: SSDT 0x00000000CDD600A8 000BE3 (v02 INTEL Ther_Rvp 00001000 INTL 20120913)
0.000000] ACPI: SSDT 0x00000000CDD60C90 0004A3 (v02 INTEL zpodd 00001000 INTL 20120913)
0.000000] ACPI: DBGP 0x00000000CDD61138 000034 (v01 INTEL 00000000 MSFT 0000005F)
0.000000] ACPI: DBG2 0x00000000CDD61170 000054 (v00 INTEL 00000000 MSFT 0000005F)
0.000000] ACPI: SSDT 0x00000000CDD611C8 000705 (v02 INTEL xh_rvp08 00000000 INTL 20120913)
0.000000] ACPI: SSDT 0x00000000CDD618D0 005359 (v02 SaSsdt SaSsdt 00003000 INTL 20120913)
0.000000] ACPI: UEFI 0x00000000CDD66C30 000042 (v01 00000000 00000000)
0....

Christoper,

I reviewed my syslog concerning all Kernel-->ACPI logs via:
cat /var/log/syslog | grep kernel | grep ACPI

I have 2 questions and hope you can help me understand:

1. ACPI loaded the 8 SSDT tables. I assume these equate to the ssdt1.dat to ssdt8.dat files obtained from acpidump. However, ssdt9.dat to ssdt12.dat were not shown to be loaded. Why did it not report 4 table load failures but 1 in the ACPI Error? Below are the relevant tables reported in my syslogs?

May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: Early table checksum verification disabled
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: RSDP 0x00000000CDD39000 000024 (v02 ALASKA)
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: XSDT 0x00000000CDD390A0 0000BC (v01 ALASKA A M I    01072009 AMI  00010013)
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: FACP 0x00000000CDD5CB78 00010C (v05 ALASKA A M I    01072009 AMI  00010013)
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: DSDT 0x00000000CDD391F8 02397B (v02 ALASKA A M I    01072009 INTL 20120913)
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: FACS 0x00000000D751BF80 000040
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: APIC 0x00000000CDD5CC88 0000BC (v03 ALASKA A M I    01072009 AMI  00010013)
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: FPDT 0x00000000CDD5CD48 000044 (v01 ALASKA A M I    01072009 AMI  00010013)
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: FIDT 0x00000000CDD5CD90 00009C (v01 ALASKA A M I    01072009 AMI  00010013)
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: MCFG 0x00000000CDD5CE30 00003C (v01 ALASKA A M I    01072009 MSFT 00000097)
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: HPET 0x00000000CDD5CE70 000038 (v01 ALASKA A M I    01072009 AMI. 0005000B)
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: SSDT 0x00000000CDD5CEA8 00036D (v01 SataRe SataTabl 00001000 INTL 20120913)
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: LPIT 0x00000000CDD5D218 000094 (v01 INTEL  SKL      00000000 MSFT 0000005F)
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: SSDT 0x00000000CDD5D2B0 000248 (v02 INTEL  sensrhub 00000000 INTL 20120913)
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: SSDT 0x00000000CDD5D4F8 002BAE (v02 INTEL  PtidDevc 00001000 INTL 20120913)
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: SSDT 0x00000000CDD600A8 000BE3 (v02 INTEL  Ther_Rvp 00001000 INTL 20120913)
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: SSDT 0x00000000CDD60C90 0004A3 (v02 INTEL  zpodd    00001000 INTL 20120913)
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: DBGP 0x00000000CDD61138 000034 (v01 INTEL           00000000 MSFT 0000005F)
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: DBG2 0x00000000CDD61170 000054 (v00 INTEL           00000000 MSFT 0000005F)
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: SSDT 0x00000000CDD611C8 000705 (v02 INTEL  xh_rvp08 00000000 INTL 20120913)
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: SSDT 0x00000000CDD618D0 005359 (v02 SaSsdt SaSsdt   00003000 INTL 20120913)
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: UEFI 0x00000000CDD66C30 000042 (v01                 00000000      00000000)
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: SSDT 0x00000000CDD66C78 000E73 (v02 CpuRef CpuSsdt  00003000 INTL 20120913)
May 23 09:35:47 Eliot kernel: [    0.000000] ACPI: BGRT 0x00000000CDD67B48 000038 (v01 ALASKA A M I    01072009 AMI  00010013)

2. The ACPI Error concerning \_SB_.PCI0.XHC_.RHUB.HS11 Namespace lookup failure said dswload is affected. I understand dsw to mean "Device Sleep Wake". Does this mean the Namespace lookup failure caused the following pci device System wakeup to be disabled? 
May 23 10:43:10 Eliot kernel: [    0.183971] pci 0000:00:01.0: System wakeup disabled by ACPI
May 23 10:43:10 Eliot kernel: [    0.184348] pci 0000:00:14.0: System wakeup disabled by ACPI
May 23 10:43:10 Eliot kernel: [    0.184828] pci 0000:00:1b.0: System wakeup disabled by ACPI
May 23 10:43:10 Eliot kernel: [    0.184979] pci 0000:00:1c.0: System wakeup disabled by ACPI
May 23 10:43:10 Eliot kernel: [    0.185130] pci 0000:00:1d.0: System wakeup disabled by ACPI
May 23 10:43:10 Eliot kernel: [    0.185618] pci 0000:00:1f.3: System wakeup disabled by ACPI
May 23 10:43:10 Eliot kernel: [    0.186086] pci 0000:00:1f.6: System wakeup disabled by ACPI
May 23 10:43:10 Eliot kernel: [    0.186230] pci 0000:01:00.0: System wakeup disabled by ACPI
Based on lspci, these device appears to be:
00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x16) (rev 07)
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev f1)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1)
00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31)
01:00.0 VGA compatible controller: NVIDIA Corporation GK110 [GeForce GTX TITAN] (rev a1)

However, when I run commands $ acpitool -w, I see the S-state of USB and Ethernet controller enabled while the S-state of the other PCI devices disabled. What is the relations?  
   Device	S-state	  Status   Sysfs node
  ---------------------------------------
  1. PEG0	  S4	*disabled  pci:0000:00:01.0
  2. PEGP	  S4	*disabled  pci:0000:01:00.0
  3. PEG1	  S4	*disabled
  4. PEGP	  S4	*disabled
  5. PEG2	  S4	*disabled
  6. PEGP	  S4	*disabled
  7. UAR1	  S4	*disabled  pnp:00:02
  8. PS2K	  S3	*disabled
  9. PS2M	  S3	*disabled
  10. RP09	  S4	*disabled  pci:0000:00:1d.0
  11. PXSX	  S4	*disabled
  12. RP10	  S4	*disabled
  13. PXSX	  S4	*disabled
  14. RP11	  S4	*disabled
  15. PXSX	  S4	*disabled
  16. RP12	  S4	*disabled
  17. PXSX	  S4	*disabled
  18. RP13	  S4	*disabled
  19. PXSX	  S4	*disabled
  20. RP01	  S4	*disabled  pci:0000:00:1c.0
  21. PXSX	  S4	*disabled
  22. RP02	  S4	*disabled
  23. PXSX	  S4	*disabled
  24. RP03	  S4	*disabled
  25. PXSX	  S4	*disabled
  26. RP04	  S4	*disabled
  27. PXSX	  S4	*disabled
  28. RP05	  S4	*disabled
  29. PXSX	  S4	*disabled
  30. RP06	  S4	*disabled
  31. PXSX	  S4	*disabled
  32. RP07	  S4	*disabled
  33. PXSX	  S4	*disabled
  34. RP08	  S4	*disabled
  35. PXSX	  S4	*disabled
  36. RP17	  S4	*disabled  pci:0000:00:1b.0
  37. PXSX	  S4	*disabled
  38. RP18	  S4	*disabled
  39. PXSX	  S4	*disabled
  40. RP19	  S4	*disabled
  41. PXSX	  S4	*disabled
  42. RP20	  S4	*disabled
  43. PXSX	  S4	*disabled
  44. RP14	  S4	*disabled
  45. PXSX	  S4	*disabled
  46. RP15	  S4	*disabled
  47. PXSX	  S4	*disabled
  48. RP16	  S4	*disabled
  49. PXSX	  S4	*disabled
  50. GLAN	  S4	*enabled   pci:0000:00:1f.6
  51. XHC	  S4	*enabled   pci:0000:00:14.0
  52. XDCI	  S4	*disabled
  53. HDAS	  S4	*disabled  pci:0000:00:1f.3

Appreciate your advice.

penalvch (penalvch) on 2016-05-23

tags:

added: latest-bios-1803
removed: bios-outdated-1703

Revision history for this message

penalvch (penalvch) wrote on 2016-05-23:

#7

SunBear, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results.

Thank you for your understanding.

summary:	- Ubuntu 16.04 LTS --> Kernal --> ACPI Errors: Namespace lookup failure - and 1 table load failures + ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, + AE_NOT_FOUND (20150930/dswload-210)
Changed in linux (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

SunBear (sunbear-c22) wrote on 2016-05-24: Re: [Bug 1584407] Re: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)

#8

Hi Christopher,

I will give it a try but it may take some time. I have to learn to
backup my system first.

Appreciate if you can answer the 2 questions in my earlier post. This is
to help me understand the error messages and how they affects my setup.

Thanks.

On 23/05/2016 19:34, Christopher M. Penalver wrote:
> SunBear, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
> 1) The one to test is at the very top line at the top of the page (not the daily folder).
> 2) The release names are irrelevant.
> 3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
> 4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .
>
> If testing on your main install would be inconvenient, one may:
> 1) Install Ubuntu to a different partition and then test this there.
> 2) Backup, or clone the primary install.
>
> If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
> kernel-fixed-upstream
> kernel-fixed-upstream-X.Y-rcZ
>
> Where X, and Y are the first two numbers of the kernel version, and Z is
> the release candidate number if it exists.
>
> If the mainline kernel does not fix the issue, please add the following tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-X.Y-rcZ
>
> Please note, an error to install the kernel does not fit the criteria of
> kernel-bug-exists-upstream.
>
> Also, you don't need to apport-collect further unless specifically
> requested to do so.
>
> Once testing of the latest upstream kernel is complete, please mark this
> report Status Confirmed. Please let us know your results.
>
> Thank you for your understanding.
>
> ** Summary changed:
>
> - Ubuntu 16.04 LTS --> Kernal --> ACPI Errors: Namespace lookup failure and 1 table load failures
> + ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>

Hi Christopher,

I will give it a try but it may take some time. I have to learn to 
backup my system first.

Appreciate if you can answer the 2 questions in my earlier post. This is 
to help me understand the error messages and how they affects my setup.

Thanks.

On 23/05/2016 19:34, Christopher M. Penalver wrote:
> SunBear, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
> 1) The one to test is at the very top line at the top of the page (not the daily folder).
> 2) The release names are irrelevant.
> 3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
> 4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .
>
> If testing on your main install would be inconvenient, one may:
> 1) Install Ubuntu to a different partition and then test this there.
> 2) Backup, or clone the primary install.
>
> If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
> kernel-fixed-upstream
> kernel-fixed-upstream-X.Y-rcZ
>
> Where X, and Y are the first two numbers of the kernel version, and Z is
> the release candidate number if it exists.
>
> If the mainline kernel does not fix the issue, please add the following tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-X.Y-rcZ
>
> Please note, an error to install the kernel does not fit the criteria of
> kernel-bug-exists-upstream.
>
> Also, you don't need to apport-collect further unless specifically
> requested to do so.
>
> Once testing of the latest upstream kernel is complete, please mark this
> report Status Confirmed. Please let us know your results.
>
> Thank you for your understanding.
>
> ** Summary changed:
>
> - Ubuntu 16.04 LTS --> Kernal --> ACPI Errors: Namespace lookup failure and 1 table load failures
> + ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)
>
> ** Changed in: linux (Ubuntu)
>         Status: Confirmed => Incomplete
>

Revision history for this message

Launchpad Janitor (janitor) wrote on 2016-07-23:

#9

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status:	Incomplete → Expired

Revision history for this message

Czikus (czikus-gmail) wrote on 2016-12-05:

#10

I am seeing the exact same problem on Ubuntu 16.04 with kernel 4.9 rc7 on Dell Precision 5510 with the latest BIOS. The error was not there on kernel 4.7.

Any ideas what I can do to debug the issue?

Czikus (czikus-gmail) on 2016-12-14

Changed in linux (Ubuntu):
status:	Expired → Incomplete

Revision history for this message

penalvch (penalvch) wrote on 2016-12-18:

#11

Czikus, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-02-16:

#12

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status:	Incomplete → Expired

Revision history for this message

Jeffrey Walton (noloader) wrote on 2017-03-10:

#13

Not sure if it changes things... ASUS released an update for the AMI UEFI on the Z170M-E DE board. Its now version 2202, dated 02/15/2017. The issue is still present.

penalvch (penalvch) on 2017-03-11

tags:

added: bios-outdated-3301 needs-upstream-testing
removed: latest-bios-1803

Revision history for this message

htrex (hantarex) wrote on 2017-04-07:

#14

I'm seeing the same error on a Dell XPS 9560 using Ubuntu 16.04.2 with kernel hwe-edge
4.10.0-14-generic #16~16.04.1-Ubuntu SMP Fri Mar 17 17:28:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

I've filed a report with ubuntu-bug linux it's on #1680268

Revision history for this message

SunBear (sunbear-c22) wrote on 2017-04-07:

#15

I had reported this bug error. However, i don't have this error anymore on a same system using Ubuntu16.04.2 with kernel 4.4.0-6x and kernel 4.8.0-xx. I suspect it is related to changes in UEFI/BIOS and using the more updated UEFI/BIOS driver versions.

Below are my UEFI settings and hope it help you (I don't know if they are correct for you or not). I am using ASUS Z170M-Plus motherboard.

Advance Setting -->Platform Misc Configuration
Platform Misc Configuration
--PCI Express Native Power Management (Enabled)
--Native ASPM (Enabled)
PCH-PCI Express
--PCH DMI ASPM (Enabled)
--ASPM (Auto)
SA-PCI Express
--DMI Link ASPM Control (L1)
--PEG-ASPM (Auto)

Advance Setting -->USB Configuration
Legacy USB Support (Enabled)
XHCI Hand-off (Enable)

Advance --> Boot
Fast Boot (Disabled)
CSM(Compatibility Support Module) --> Launch CSM (Disabled)
Secure Boot (Other OS)

penalvch (penalvch) on 2017-05-07

no longer affects:

linux (Ubuntu)

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-05-07:

#16

Status changed to 'Confirmed' because the bug affects multiple users.

Revision history for this message

penalvch (penalvch) wrote on 2017-05-07:

#17

SunBear, this report is being closed due to your last comment https://bugs.launchpad.net/archlinux/+source/linux/+bug/1584407/comments/15 regarding this being fixed with a BIOS update.

Launchpad Janitor (janitor) on 2017-05-07

Changed in linux (Ubuntu):
status:	New → Confirmed

penalvch (penalvch) on 2017-05-07

affects:	linux (Arch Linux) → linux (Ubuntu)
Changed in linux (Ubuntu):
status:	New → Invalid

Revision history for this message

Piotr Kołaczkowski (pkolaczk-u) wrote on 2017-05-20:

#18

I have the same bug on Dell Precision 5520 and Ubuntu 17.04 with either officially supported kernel 4.10.0-21 as well as mainline kernel 4.11.1.

[ 0.037469] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170119/dswload-210)
[ 0.037476] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170119/psobject-227)
[ 0.037516] ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp11) while loading table (20170119/tbxfload-228)
[ 0.040436] ACPI Error: 1 table load failures, 12 successful (20170119/tbxfload-246)

Revision history for this message

Adam (asarenski) wrote on 2017-05-31:

#19

I would like to report that I have the same issue as well when trying to use an ubuntu live usb.
Mainboard:
Gigabyte Technology co. Ltd.
Z170X-Gaming 7

Revision history for this message

Tian Yong (htian) wrote on 2017-06-19:

#20

Linus reported this bug last year, https://lkml.org/lkml/2016/10/5/299

Revision history for this message

htrex (hantarex) wrote on 2017-06-20:

#21

Same error on Dell XPS 9560, Ubuntu 16.04.2 kernel 4.10.0-22-generic

Revision history for this message

MV (mvidal) wrote on 2017-10-28:

#22

Same kind of error with ubuntu 17.10 on a MEDION computer with bios updated 110H4W0X.110 :

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

Revision history for this message

WinEunuchs2Unix (ricklee518) wrote on 2017-12-13:

#23

Error remains Dell based Skylake 6700HQ, HM170, nVidia 384.98, NVMe Gen3x4 M.2 SSD, Ubuntu 16.04.3, Kernel 4.14.4:

Dec 12 19:08:16 alien kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170728/dswload-210)
Dec 12 19:08:16 alien kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170728/psobject-252)
Dec 12 19:08:16 alien kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp10) while loading table (20170728/tbxfload-228)
Dec 12 19:08:16 alien kernel: ACPI Error: 1 table load failures, 9 successful (20170728/tbxfload-246)
Dec

Revision history for this message

WinEunuchs2Unix (ricklee518) wrote on 2017-12-14:

#24

#15 says problem went away but is on Kernel 4.4 and Kerne 4.8 where message was "hacked" to not display. With kernels 4.9, 4.10, etc. the message reappears as per bug report here: https://bugzilla.kernel.org/show_bug.cgi?id=193531

#17 closing this bug based upon #15 should be reconsidered.

Also note this bug is a duplicate of: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690502 which has fewer subscribers but more accurate information.

There is a third duplicate bug report in launchpad which I don't have the link for just now.

Revision history for this message

Jeffrey Walton (noloader) wrote on 2017-12-14:

#25

> #15 says problem went away but is on Kernel 4.4 and Kerne 4.8
> where message was "hacked" to not display. With kernels 4.9, 4.10,
> etc...

That's not the first time the kernel folks have done that. They do it in the crypto subsystem to hide messages that folks would want to see and fix, like the random number generator having no entropy but startup programs trucking on as if get_random_{u32,u64,int,long} succeeded.

It would be nice to see the problem fixed rather than covering them up.

Revision history for this message

dmytriy (dmdmdiy) wrote on 2017-12-20:

#26

I discovered the same problem on Alienware 15r2. I suspect this causes/indicates that a bug in ACPI disables the suspend and hibernate function. Specifically, after closing the lid on a laptop, it goes into suspend mode, but then after opening the screen stays black. If it helps: the hard drive starts spinning and the battery indicator blinks non-stop. Can anyone suggest a fix, please ?

Revision history for this message

dmytriy (dmdmdiy) wrote on 2017-12-20:

#27

By the way, I am using Ubuntu 17.10

Revision history for this message

WinEunuchs2Unix (ricklee518) wrote on 2017-12-21:

#28

@dmytriy--I suspect your suspend/resume problems are unrelated simply because there are hundreds of different problems in that area. I suggest searching Ask Ubuntu or Linux & Unix sites. For example, my Alienware AW17R3 with i-7 6700HQ (Skylake) wouldn't suspend/resume because of NVMe M.2 Gen 3.0 x 4 SSD. The solution, for me and a few others, was to put a kernel command line parameter in /etc/default/grub.

Revision history for this message

dmytriy (dmdmdiy) wrote on 2017-12-21:

#29

Thank you for your reply. I tried adding a parameter in grub file also (acpihp.disable = 1), but that didn't works for me :( Anyways, I will keep looking, thanks

Revision history for this message

mrswescott (mrswescott) wrote on 2017-12-21:

#30

I would like to report the same issue on a Zotac ZBOX-SN970-P.

The issue prevents booting from any Live USB install of the following distros :

Ubuntu 16.04.3 LTS, Ubuntu 17.10, Mint 18.3, Arch Linux 2017.12.01

The BIOS is as up to date as possible.

Revision history for this message

Luis Alberto Pabón (copong) wrote on 2018-01-05:

#31

Same issue on Dell XPS 15 9560:

[ 0.004000] ACPI: Core revision 20170531
[ 0.004000] ACPI: Overriding _REV return value to 5
[ 0.038137] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170531/dswload-210)
[ 0.038142] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170531/psobject-252)
[ 0.038181] ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp11) while loading table (20170531/tbxfload-228)
[ 0.041005] ACPI Error: 1 table load failures, 12 successful (20170531/tbxfload-246)

Linux luis-XPS-15-9560 4.13.0-21-generic #24-Ubuntu SMP Mon Dec 18 17:29:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Ubuntu 17.10

Revision history for this message

Luis Alberto Pabón (copong) wrote on 2018-01-05:

#32

I haven't noticed any adverse effects yet, but the laptop is relatively new and I'm not yet 100% familiar with its nooks and crannies.

Revision history for this message

Varisht Ghedia (varishtsg) wrote on 2018-02-11:

#33

I too face the same issue on my dell Inspiron 15 7577 i5 7th Gen laptop. So far no negative effects other than long boot times despite using a full SSD system(256GB NVMe + 256GB SATA3). I have the latest bios as well.

Revision history for this message

William Klock (wklock) wrote on 2018-02-21:

#34

I have this issue as well. ThinkPad P51, 4.15.4-041504-generic, Ubuntu 17.10

Revision history for this message

blszyn (blszyn) wrote on 2018-04-13:

#35

Another ThinkPad P51
5.15.0-13-generic, Ubuntu 18.04

[ 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:ProjSsdt) while loading table (20170831/tbxfload-228)
[ 0.000000] ACPI Error: 1 table load failures, 11 successful (20170831/tbxfload-246)

Revision history for this message

Rik (riksoft) wrote on 2018-04-24:

#36

Same problem with Asrock z370 Extreme4

Apr 24 08:31:48 localhost kernel: [ 0.033049] ACPI: Added _OSI(Processor Aggregator Device)
Apr 24 08:31:48 localhost kernel: [ 0.037493] ACPI Error: [_SB_.PCI0.RP05.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload2-191)
Apr 24 08:31:48 localhost kernel: [ 0.037502] No Local Variables are initialized for Method [PXSX]
Apr 24 08:31:48 localhost kernel: [ 0.037503] No Arguments are initialized for method [PXSX]
Apr 24 08:31:48 localhost stunnel4[947]: SSL tunnels disabled, see /etc/default/stunnel4
Apr 24 08:31:48 localhost kernel: [ 0.037504] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252)
Apr 24 08:31:48 localhost kernel: [ 0.037507] ACPI Error: Method parse/execution failed \_SB.PCI0.RP04.PXSX, AE_NOT_FOUND (20170831/psparse-550)
Apr 24 08:31:48 localhost kernel: [ 0.037938] ACPI Error: [_SB_.PCI0.RP09.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload2-191)
Apr 24 08:31:48 localhost systemd[1]: Started LSB: Start or stop stunnel 4.x (SSL tunnel for network daemons).
Apr 24 08:31:48 localhost kernel: [ 0.037943] No Local Variables are initialized for Method [PXSX]
Apr 24 08:31:48 localhost kernel: [ 0.037944] No Arguments are initialized for method [PXSX]
Apr 24 08:31:48 localhost anacron[984]: Normal exit (0 jobs run)
Apr 24 08:31:48 localhost kernel: [ 0.037945] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252)
Apr 24 08:31:48 localhost kernel: [ 0.037948] ACPI Error: Method parse/execution failed \_SB.PCI0.RP08.PXSX, AE_NOT_FOUND (20170831/psparse-550)

Revision history for this message

Devin Taietta (devintaietta) wrote on 2018-05-08:

#37

Same here

ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload-210)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp10) while loading table (20170831/tbxfload-228)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Error: 1 table load failures, 12 successful (20170831/tbxfload-246)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
mag 08 21:41:17 devin-XPS-15-9550 kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Error: [\_SB_.PCI0.LPCB.H_EC.CHRG] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
mag 08 21:41:17 devin-XPS-15-9550 kernel: No Local Variables are initialized for Method [PNOT]
mag 08 21:41:17 devin-XPS-15-9550 kernel: No Arguments are initialized for method [PNOT]
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Error: Method parse/execution failed \PNOT, AE_NOT_FOUND (20170831/psparse-550)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Error: Method parse/execution failed \_SB.AC._PSR, AE_NOT_FOUND (20170831/psparse-550)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Exception: AE_NOT_FOUND, Error reading AC Adapter state (20170831/ac-139)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
mag 08 21:41:17 devin-XPS-15-9550 kernel:
Initialized Local Variables for Method [FNCL]:
mag 08 21:41:17 devin-XPS-15-9550 kernel: Local0: 00000000371c4672 <Obj> Integer 0000000000000001
mag 08 21:41:17 devin-XPS-15-9550 kernel: Local1: 000000009fadc1b6 <Obj> Integer 0000000000000000
mag 08 21:41:17 devin-XPS-15-9550 kernel: Local2: 00000000a1728e58 <Obj> Integer 0000000000000000
mag 08 21:41:17 devin-XPS-15-9550 kernel: Local3: 0000000029024229 <Obj> Integer 0000000000000000
mag 08 21:41:17 devin-XPS-15-9550 kernel: Local4: 00000000236db817 <Obj> Integer 0000000000000000
mag 08 21:41:17 devin-XPS-15-9550 kernel: Local5: 000000009a01c773 <Obj> Integer 0000000000000000
mag 08 21:41:17 devin-XPS-15-9550 kernel: Local6: 00000000c88fc2bf <Obj> Integer 0000000000000000
mag 08 21:41:17 devin-XPS-15-9550 kernel: No Arguments are initialized for method [FNCL]
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Error: Method parse/execution failed \_TZ.FNCL, AE_NOT_FOUND (20170831/psparse-550)

Same here

ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload-210)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp10) while loading table (20170831/tbxfload-228)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Error: 1 table load failures, 12 successful (20170831/tbxfload-246)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
mag 08 21:41:17 devin-XPS-15-9550 kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Error: [\_SB_.PCI0.LPCB.H_EC.CHRG] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
mag 08 21:41:17 devin-XPS-15-9550 kernel: No Local Variables are initialized for Method [PNOT]
mag 08 21:41:17 devin-XPS-15-9550 kernel: No Arguments are initialized for method [PNOT]
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Error: Method parse/execution failed \PNOT, AE_NOT_FOUND (20170831/psparse-550)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Error: Method parse/execution failed \_SB.AC._PSR, AE_NOT_FOUND (20170831/psparse-550)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Exception: AE_NOT_FOUND, Error reading AC Adapter state (20170831/ac-139)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
mag 08 21:41:17 devin-XPS-15-9550 kernel: 
                                          Initialized Local Variables for Method [FNCL]:
mag 08 21:41:17 devin-XPS-15-9550 kernel:   Local0: 00000000371c4672 <Obj>           Integer 0000000000000001
mag 08 21:41:17 devin-XPS-15-9550 kernel:   Local1: 000000009fadc1b6 <Obj>           Integer 0000000000000000
mag 08 21:41:17 devin-XPS-15-9550 kernel:   Local2: 00000000a1728e58 <Obj>           Integer 0000000000000000
mag 08 21:41:17 devin-XPS-15-9550 kernel:   Local3: 0000000029024229 <Obj>           Integer 0000000000000000
mag 08 21:41:17 devin-XPS-15-9550 kernel:   Local4: 00000000236db817 <Obj>           Integer 0000000000000000
mag 08 21:41:17 devin-XPS-15-9550 kernel:   Local5: 000000009a01c773 <Obj>           Integer 0000000000000000
mag 08 21:41:17 devin-XPS-15-9550 kernel:   Local6: 00000000c88fc2bf <Obj>           Integer 0000000000000000
mag 08 21:41:17 devin-XPS-15-9550 kernel: No Arguments are initialized for method [FNCL]
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Error: Method parse/execution failed \_TZ.FNCL, AE_NOT_FOUND (20170831/psparse-550)

Revision history for this message

Zbigniew Lisiecki (zlisiecki) wrote on 2018-06-07:

#38

Hi, I had the same error on ASUS Z170 PRO GAMING with a new opensuse Linux Leap 15 . No errors with former suse versions !
Now I updated the BIOS to Z170 PRO GAMING Ver 3805 build on 05/16/2018 and the error seems to disappear.

A assume: with Opensuse or ubuntu the same kernel module is involved in this case

Revision history for this message

htrex (hantarex) wrote on 2018-08-16:

#39

On an Dell XPS 9560
Ubuntu 18.04.1
Linux OrionXPS 4.15.0-32-generic #35-Ubuntu SMP Fri Aug 10 17:58:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

[ 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_rvp11) while loading table (20170831/tbxfload-228)
[ 0.000000] ACPI Error: 1 table load failures, 12 successful (20170831/tbxfload-246)

Revision history for this message

mercury (leisch) wrote on 2019-01-04:

#40

$ lsb_release -rd
Description: Ubuntu 18.04.1 LTS
Release: 18.04

$ uname -r
4.15.0-43-generic

[ 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, 7 successful (20170831/tbxfload-246)

Revision history for this message

Leon Yeoh (bitdash) wrote on 2019-01-29:

#41

Description: Ubuntu 18.04.1 LTS
Release: 18.04

4.15.0-43-generic
also have tried 4.15.0-43-generic (same error)
I do not have older kernel on my system now, how to recover it? Thank you

now I cannot boot into my kubuntu
only can get to emergency mode (recovery mode failed as well)

journalctl -xb in emergency mode and found below errors (same as others in this thread)
ACPI Error [\_SB_.PCIO. xxxxxxx ] Namespace lookup failure, AE_NOT_FOUND

Revision history for this message

curlysue (curlywalter) wrote on 2019-02-04:

#42

suddenly the same here
4.15.0-33-generic works fine
4.15.0-34-generic not
bios updated
it is a striped raid here

Revision history for this message

curlysue (curlywalter) wrote on 2019-02-05:

#43

Description: Ubuntu 18.04.1 LTS
Release: 18.04
CPU~Quad core Intel Core i5-6600 (-MCP-) speed/max~1056/3900 MHz Kernel~4.15.0-33-generic x86_64 Up~22:28 Mem~2305.8/15714.8MB HDD~500.1GB(22.0% used) Procs~315 Client~Shell inxi~2.3.56
Produkt: H170M Pro4S
Hersteller: ASRock

Revision history for this message

Seiichi Nakashima (ubuntu-linuxer) wrote on 2019-03-16:

#44

same error
ACPI Error: [\_SB_.PCIO.XHC_RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload-210)
ubuntu-18.04
4.15.0-46-generic
ASRock MB
Intel i3-7100

Brad Figg (brad-figg) on 2019-07-24

tags:

added: cscc

Ubuntu
linux package

ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)

Bug Description

Other bug subscribers

Related questions

Bug attachments

Remote bug watches

Ubuntulinux package

ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)

Bug Description

Other bug subscribers

Related questions

Bug attachments

Remote bug watches

Ubuntu
linux package