Bug 1413342 - Linux 4.9.3: ACPI Error: [_OSI] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
Linux 4.9.3: ACPI Error: [_OSI] Namespace lookup failure, AE_NOT_FOUND (20160...
Status: NEW
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
27
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
: Reopened
: 1415853 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-01-15 01:26 EST by Fadlun Akbar
Modified: 2017-12-12 05:08 EST (History)
40 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-12-12 05:03:16 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
dmesg-acpi-log (12.95 KB, text/plain)
2017-01-15 01:26 EST, Fadlun Akbar
no flags Details
Similar log messages in arch linux for kernel 4.9.6-1 (215.96 KB, text/plain)
2017-01-31 13:55 EST, Mike C
no flags Details
Output of: cat /sys/firmware/acpi/tables/DSDT > dsdt.dat & iasl -d dsdt.dat (1.07 MB, text/plain)
2017-04-15 10:19 EDT, Simon Rowe
no flags Details

  None (edit)
Description Fadlun Akbar 2017-01-15 01:26:05 EST
Created attachment 1240893 [details]
dmesg-acpi-log

Description of problem:

When I used kernel parameter acpi_osi= without any string (e.g: acpi_osi=Linux), I got some error messages:

[    0.297969] ACPI Error: [_OSI] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[    0.298152] ACPI Error: Method parse/execution failed [\_SB.BTKL._STA] (Node ffffa0b3a84cb2f8), AE_NOT_FOUND (20160831/psparse-543)
[    0.298396] ACPI Error: [_OSI] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[    0.298571] ACPI Error: Method parse/execution failed [\_SB.BTKL._STA] (Node ffffa0b3a84cb2f8), AE_NOT_FOUND (20160831/psparse-543)

Kernel version: 4.9.3-200.fc25.x86_64

Steps to Reproduce:
Boot 4.9.3-200.fc25.x86_64 with kernel parameter acpi_osi=

Actual results:
See attachment for full log

Expected results:
No error messages
Comment 1 Vinicius Reis 2017-01-16 06:28:39 EST
Same issue here since 4.9.3-200.fc25.x86_64, not using acpi_osi at all.
Previous kernel did not generate these messages.

$dmesg | grep -i 'lookup'
[    0.732689] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECWT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[    0.732802] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECWT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[    0.763406] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECRD] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[    0.763586] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECRD] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[    0.763710] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECRD] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[    0.763826] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECRD] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
Comment 2 Laura Abbott 2017-01-16 13:45:14 EST
I recommend running a bisect to figure out which commit introduced these messages for you. You could also file a bug on kernel.org since Intel maintainers are often responsive there.
Comment 3 mrh 2017-01-17 11:07:51 EST
Another example of same issue but system fails to boot, whereas this system boots fine using 4.8.15-300:

Jan 16 20:47:40 copernicus kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20160831/dsw
Jan 16 20:47:40 copernicus kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20160831/psobject-227)
Jan 16 20:47:40 copernicus kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table (20160831/tbxfload-228)
Jan 16 20:47:40 copernicus kernel: ACPI Error: 1 table load failures, 8 successful (20160831/tbxfload-246)

and further down the same boot log...

Jan 16 20:47:41 copernicus kernel: amdgpu 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff
Jan 16 20:47:41 copernicus kernel: ATOM BIOS: 67DFHB.15.50.0.0.AS37
Jan 16 20:47:41 copernicus kernel: [drm] GPU post is not needed
Jan 16 20:47:41 copernicus kernel: amdgpu 0000:01:00.0: Direct firmware load for amdgpu/polaris10_mc.bin failed with error -2
Jan 16 20:47:41 copernicus kernel: mc: Failed to load firmware "amdgpu/polaris10_mc.bin"
Jan 16 20:47:41 copernicus kernel: [drm:gmc_v8_0_sw_init [amdgpu]] *ERROR* Failed to load mc firmware!
Jan 16 20:47:41 copernicus kernel: [drm:amdgpu_device_init [amdgpu]] *ERROR* sw_init of IP block <gmc_v8_0> failed -2
Jan 16 20:47:41 copernicus kernel: amdgpu 0000:01:00.0: amdgpu_init failed
Jan 16 20:47:41 copernicus kernel: amdgpu 0000:01:00.0: Fatal error during GPU init
Jan 16 20:47:41 copernicus kernel: [drm] amdgpu: finishing device.
Jan 16 20:47:41 copernicus kernel: [TTM] Memory type 2 has not been initialized
Jan 16 20:47:41 copernicus kernel: amdgpu: probe of 0000:01:00.0 failed with error -2

Boot failure
Comment 4 Vinicius Reis 2017-01-18 09:46:01 EST
I can't do a bisect patch by patch since this  issue actually is happening on a production machine, what prevents a deep kernel compile/test/debug procedure; but I can provide any useful log needed for one working on this issue. 

What I can identify is the Fedora kernel release that introduced this issue on this machine. The last 'OK' release was 4.8.16-300.fc25.x86_64. The next release, 4.9.3-200.fc25.x86_64, introduced this issue.

Currently I can't say if something stopped to work, but as opposed to #3, the boot doesn't fail. For the sake of safety, we are booting with the previous kernel (4.8.16-300).
Comment 5 Alexander 2017-01-23 15:25:17 EST
Confirming this.

4.9.4-100.fc24.x86_64

янв 23 23:19:08 freelancer.localdomain kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20160831/dswload-210)
янв 23 23:19:08 freelancer.localdomain kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20160831/psobject-227)
янв 23 23:19:08 freelancer.localdomain kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table (20160831/tbxfload-228)
янв 23 23:19:08 freelancer.localdomain kernel: ACPI Error: 1 table load failures, 8 successful (20160831/tbxfload-246)

ASUS Z170-K motherboard and Intel 6700K CPU, if this is important.
Comment 6 Alexander 2017-01-23 15:28:04 EST
(In reply to Alexander from comment #5)
> Confirming this.

Systems boots as usually except this message in journal and at boot screen.
Comment 7 cyberalex4life 2017-01-24 11:15:03 EST
Here's how this bug looks on my laptop: 
(Lenovo G70-80, Intel Core i7-5500U @ 2.40GHz × 4, 8GB RAM, NVidia GF 920M 2GB, 120 GB SSD OCZ-AGILITY3, 1TB HDD Western Digital WDC WD10JPCX-24UE4T0)
https://i.imgur.com/tlUVoRl.jpg
https://i.imgur.com/ZJcf811.jpg
This happens from kernel 4.9.3 I think (the first 4.9 from updates). Another issue is that resuming from hibernate ends with my screen blocked with the image before hibernate. I usually have to force it off.

I am on 4.8.6, this is the last 4.8 in repo's, and things go generally well, including hibernating.

Here's what I have in /etc/default/grub:
GRUB_CMDLINE_LINUX="resume=/dev/disk/by-uuid/5b099b6f-8c16-4503-bd77-a1cd8ca5a756     nouveau.modeset=0 rd.driver.blacklist=nouveau rhgb quiet"
GRUB_CMDLINE_LINUX_DEFAULT="elevator=deadline usbhid.mousepoll=4" 

Also, bumblebee-nvidia fails to compile in the actual 4.9.5 (I'm not sure about 4.9.4)
Comment 8 Laura Abbott 2017-01-24 13:58:18 EST
*** Bug 1415853 has been marked as a duplicate of this bug. ***
Comment 9 Vinicius Reis 2017-01-25 08:18:37 EST
This issue still present on 4.9.5-200.fc25.x86_64
Comment 10 Greta Watson 2017-01-25 13:26:10 EST
Also fails in fedora 24 with kernel 4.9.5-100.fc24.x86_64.

Jan 25 02:15:43 sparky kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
...

System boots but spews out a bunch of error messages.
Comment 11 Vinicius Reis 2017-01-31 11:33:37 EST
With the new 4.9.6-200.fc25.x86_64 release, a new message is shown, but I'm not sure if it is related to the ones previously reported:
[    0.287520] platform wdat_wdt: failed to claim resource 4

So now, the following messages are shown at boot time:
[    0.287520] platform wdat_wdt: failed to claim resource 4
[    0.732858] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECWT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[    0.732902] ACPI Error: Method parse/execution failed [\_TZ.FN00._ON] (Node ffff9be4d60eff78), AE_NOT_FOUND (20160831/psparse-543)
[    0.732971] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECWT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[    0.733010] ACPI Error: Method parse/execution failed [\_TZ.FN00._ON] (Node ffff9be4d60eff78), AE_NOT_FOUND (20160831/psparse-543)
[    0.755676] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECRD] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[    0.755717] ACPI Error: Method parse/execution failed [\_TZ.TZ00._TMP] (Node ffff9be4d60efcf8), AE_NOT_FOUND (20160831/psparse-543)
[    0.755838] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECRD] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[    0.755878] ACPI Error: Method parse/execution failed [\_TZ.TZ00._TMP] (Node ffff9be4d60efcf8), AE_NOT_FOUND (20160831/psparse-543)
[    0.755958] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECRD] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[    0.755997] ACPI Error: Method parse/execution failed [\_TZ.TZ01._TMP] (Node ffff9be4d60f45a0), AE_NOT_FOUND (20160831/psparse-543)
[    0.756071] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECRD] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[    0.756109] ACPI Error: Method parse/execution failed [\_TZ.TZ01._TMP] (Node ffff9be4d60f45a0), AE_NOT_FOUND (20160831/psparse-543)


After that, system boots and is usable with no noticeable issues though.
Comment 12 Mike C 2017-01-31 13:55 EST
Created attachment 1246393 [details]
Similar log messages in arch linux for kernel 4.9.6-1

Given the analogous messages are also seen in a different distro this is likely an upstream bug so perhaps worth reporting at kernel bugzilla?
Comment 13 Mike C 2017-01-31 14:00:25 EST
Upstream bug is https://bugzilla.kernel.org/show_bug.cgi?id=193531
Comment 14 Patrick O'Callaghan 2017-03-06 11:45:47 EST
Another sufferer here, basically since F25. I see from the journal that these are not new messages, but they are now prominently displayed on the console when booting instead of being quietly added to the log. If they don't indicate a real problem, is there a way to get them to just shut up?
Comment 15 cyberalex4life 2017-03-06 17:02:37 EST
With the possibility of being ridiculous, I admit I asked myself the same question of few years, ago. However I have not found an easy answer so I let it go. And here comes the ridiculous part: maybe they are just there to annoy people so that they'll be fixed and also to point that there's always that problem that could be the cause of other failures.
If this is the case, the hardest workaround would be a patch from someone that knows what is doing, or multiple configuration files edited/added. 
The simplest may be one hidden config file somewhere in the system... I always thought that this should be a simple info to find, but it proved not.
Comment 16 Justin M. Forbes 2017-04-11 10:56:24 EDT
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-200.fc25.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.
Comment 17 Fadlun Akbar 2017-04-11 11:45:35 EDT
(In reply to Justin M. Forbes from comment #16)
> *********** MASS BUG UPDATE **************
> 
> We apologize for the inconvenience.  There is a large number of bugs to go
> through and several of them have gone stale.  Due to this, we are doing a
> mass bug update across all of the Fedora 25 kernel bugs.
> 
> Fedora 25 has now been rebased to 4.10.9-200.fc25.  Please test this kernel
> update (or newer) and let us know if you issue has been resolved or if it is
> still present with the newer kernel.
> 
> If you have moved on to Fedora 26, and are still experiencing this issue,
> please change the version to Fedora 26.
> 
> If you experience different issues, please open a new bug report for those.

The current kernel (4.10.8-200.fc25.x86_64) had solved this issue. Tested on:

System:    Host: nekodora Kernel: 4.10.8-200.fc25.x86_64 x86_64 (64 bit) Desktop: Budgie 10.2.9
           Distro: Fedora release 25 (Twenty Five)
Machine:   Device: laptop System: ASUSTeK product: X455LD v: 1.0
           Mobo: ASUSTeK model: X455LD v: 1.0 UEFI: American Megatrends v: X455LD.202 date: 06/11/2014
Battery    BAT0: charge: 13.8 Wh 63.8% condition: 21.6/37.3 Wh (58%)
CPU:       Dual core Intel Core i3-4030U (-HT-MCP-) speed/max: 799/1800 MHz
Graphics:  Card-1: Intel Haswell-ULT Integrated Graphics Controller
           Card-2: NVIDIA GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M]
           Display Server: Fedora X.org 119.3 drivers: intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1366x768@60.00hz
           GLX Renderer: Mesa DRI Intel Haswell Mobile GLX Version: 3.0 Mesa 13.0.4
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
           Card-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k
Drives:    HDD Total Size: 500.1GB (30.0% used)
Info:      Processes: 236 Uptime: 1:50 Memory: 1828.0/5788.4MB Client: Shell (zsh) inxi: 2.3.8
Comment 18 Patrick O'Callaghan 2017-04-11 12:43:51 EDT
(In reply to Justin M. Forbes from comment #16)
> *********** MASS BUG UPDATE **************
> 
> We apologize for the inconvenience.  There is a large number of bugs to go
> through and several of them have gone stale.  Due to this, we are doing a
> mass bug update across all of the Fedora 25 kernel bugs.
> 
> Fedora 25 has now been rebased to 4.10.9-200.fc25.  Please test this kernel
> update (or newer) and let us know if you issue has been resolved or if it is
> still present with the newer kernel.
> 
> If you have moved on to Fedora 26, and are still experiencing this issue,
> please change the version to Fedora 26.
> 
> If you experience different issues, please open a new bug report for those.

Appears to be solved here, kernel 4.10.8-200.fc25.x86_64
Comment 19 Isaque Galdino 2017-04-11 13:38:34 EDT
I'm still seeing this issue:

$ uname -a
Linux fred.bedrock 4.10.8-200.fc25.x86_64 #1 SMP Fri Mar 31 13:20:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

$ dmesg | grep -i namespace
[    0.937396] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECWT] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.937527] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECWT] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.949988] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECRD] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.950154] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECRD] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.950275] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECRD] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.950388] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECRD] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
Comment 20 Jia Yuan Lo 2017-04-11 23:11:22 EDT
I believe all the namespace lookup failure (in ASUS laptops) is caused by acpi_osi=

which leads to going into untested route in DSDT

Since 4.10, I no longer need acpi_osi= for my ASUS X552LD (BIOS X550LD) and fn keys and backlight are working out of box now...

You guys can try remove acpi_osi=

If it doesn't, follow https://wiki.archlinux.org/index.php/DSDT#Recompiling_it_yourself

# dnf install acpica-tools
# cat /sys/firmware/acpi/tables/DSDT > dsdt.dat
$ iasl -d dsdt.dat

Then open dsdt.dsl with a text editor and search for Windows

You should get a list of OS strings that your ACPI known to support

then you can go add to grub and test it in descending order

acpi_osi=! acpi_osi="Windows [insert version here]"

acpi_osi= should not be the workaround and acpi_osi=Linux are not advised to use either
Comment 21 Greta Watson 2017-04-12 14:02:18 EDT
My ASUS laptop has never seen this issue.

My desktop, though, not only has seen this issue, but still sees it:

~ $ uname -a
Linux sparky 4.10.9-200.fc25.x86_64 #1 SMP Mon Apr 10 14:48:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
~ $ dmesg | grep "ACPI Error" | head -4
[    1.218406] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    1.218463] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT2._GTF] (Node ffff8bb24f4c2618), AE_NOT_FOUND (20160930/psparse-543)
[    1.218993] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    1.219045] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT2._GTF] (Node ffff8bb24f4c2618), AE_NOT_FOUND (20160930/psparse-543)
Comment 22 Fadlun Akbar 2017-04-13 15:37:19 EDT
(In reply to Jia Yuan Lo from comment #20)
> I believe all the namespace lookup failure (in ASUS laptops) is caused by
> acpi_osi=
> 
> which leads to going into untested route in DSDT
> 
> Since 4.10, I no longer need acpi_osi= for my ASUS X552LD (BIOS X550LD) and
> fn keys and backlight are working out of box now...
> 
> You guys can try remove acpi_osi=
> 
> If it doesn't, follow
> https://wiki.archlinux.org/index.php/DSDT#Recompiling_it_yourself
> 
> # dnf install acpica-tools
> # cat /sys/firmware/acpi/tables/DSDT > dsdt.dat
> $ iasl -d dsdt.dat
> 
> Then open dsdt.dsl with a text editor and search for Windows
> 
> You should get a list of OS strings that your ACPI known to support
> 
> then you can go add to grub and test it in descending order
> 
> acpi_osi=! acpi_osi="Windows [insert version here]"
> 
> acpi_osi= should not be the workaround and acpi_osi=Linux are not advised to
> use either

Yup, this is what I mean. With the the current kernel, I no longer need acpi_osi= too for my ASUS A455L, works great as you said.
Comment 23 Simon Rowe 2017-04-15 10:14:23 EDT
System is Alienware 13 R2 laptop running Fedora 25 (fresh net install) with updates applied:

Kernel version: 
Linux version 4.10.9-200.fc25.x86_64 (mockbuild@bkernel01.phx2.fedoraproject.org) (gcc version 6.3.1 20161221 (Red Hat 6.3.1-1) (GCC) ) #1 SMP Mon Apr 10 14:48:16 UTC 2017

journalctl -xb output ACPI errors:

ACPI Error: [\_SB_.PCI0.SAT1] Namespace lookup failure, AE_NOT_FOUND (20160930/dswload-210)
Apr 15 14:26:21 alienmoons kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20160930/psobject-227)
Apr 15 14:26:21 alienmoons kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:IdeTable) while loading table (20160930/tbxfload-228)
Apr 15 14:26:21 alienmoons kernel: ACPI Error: 1 table load failures, 10 successful (20160930/tbxfload-246)

Then later on in boot messages (not sure if it is related):

ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160930/nsarguments-95)
Apr 15 14:26:21 alienmoons kernel: ACPI Warning: \_SB.PCI0.RP01.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160930/nsarguments-95)
Apr 15 14:26:21 alienmoons kernel: ACPI Warning: \_SB.PCI0.RP01.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160930/nsarguments-95)
Comment 24 Simon Rowe 2017-04-15 10:19 EDT
Created attachment 1271816 [details]
Output of:  cat /sys/firmware/acpi/tables/DSDT > dsdt.dat   &   iasl -d dsdt.dat

As per suggested comments in this bug report, I ran the following:

dnf install acpica-tools
cat /sys/firmware/acpi/tables/DSDT > dsdt.dat
iasl -d dsdt.dat

Attached file is the output of the final command above - just in case it is useful to assist with working out what the issue is.
Comment 25 Panos Kavalagios 2017-04-20 10:15:31 EDT
I am also affected by this issue and there is no BIOS upgrade for my motherboard:

[    0.841257] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.841317] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffffa08c0e8cb050), AE_NOT_FOUND (20160930/psparse-543)
[    0.841668] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.841726] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT0._GTF] (Node ffffa08c0e8cb348), AE_NOT_FOUND (20160930/psparse-543)
[    0.842786] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.842844] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffffa08c0e8cb488), AE_NOT_FOUND (20160930/psparse-543)

and my system is:

BIOS Information
        Vendor: American Megatrends Inc.
        Version: 4.6.5
        Release Date: 12/18/2012
Base Board Information
        Manufacturer: WIBTEK
        Product Name: H61-M HDMI2 
        Version: 0.59
Comment 26 Norbert Makula 2017-04-20 17:23:58 EDT
Hello
Comment 27 Norbert Makula 2017-04-20 17:30:55 EDT
Sorry for that comment. I don't wanted send it...
I have this error too.

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

BIOS Information
Vendor: American Megatrends Inc.
	Version: P7.10
	Release Date: 11/30/2016

Base Board Information
	Manufacturer: ASRock
	Product Name: B150M Pro4
	Version:
Comment 28 Louis van Dyk 2017-04-22 19:29:11 EDT
Problem persists:

# uname -a
Linux fedora.localdomain 4.10.10-200.fc25.x86_64 #1 SMP Thu Apr 13 01:11:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

See below extract from dmesg:

[    0.938813] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    0.938835] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    0.938866] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    0.938887] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    0.938911] ata7: SATA link down (SStatus 0 SControl 300)
[    0.938922] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    0.938958] ata8: SATA link down (SStatus 0 SControl 300)
[    0.938960] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    0.939406] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.939482] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT3._GTF] (Node ffff8ae0ce0cff50), AE_NOT_FOUND (20160930/psparse-543)
[    0.939613] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.939688] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff8ae0ce0e6528), AE_NOT_FOUND (20160930/psparse-543)
[    0.939828] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.939920] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff8ae0ce0cfdc0), AE_NOT_FOUND (20160930/psparse-543)
[    0.940099] ata6.00: ATA-9: WDC WD40PURX-64GVNY0, 80.00A80, max UDMA/133
[    0.940101] ata6.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[    0.940165] ata4.00: ATA-9: ST4000DM000-1F2168, CC54, max UDMA/133
[    0.940168] ata4.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[    0.940196] ata2.00: ATA-8: ST3500418AS, CC38, max UDMA/133
[    0.940199] ata2.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[    0.940756] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.940830] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff8ae0ce0e6528), AE_NOT_FOUND (20160930/psparse-543)
[    0.940976] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.941053] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT3._GTF] (Node ffff8ae0ce0cff50), AE_NOT_FOUND (20160930/psparse-543)
[    0.941228] ata6.00: configured for UDMA/133
[    0.941355] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.941430] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff8ae0ce0cfdc0), AE_NOT_FOUND (20160930/psparse-543)
[    0.941631] ata4.00: configured for UDMA/133
[    0.941701] ata2.00: configured for UDMA/133
[    0.944377] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.944632] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT2._GTF] (Node ffff8ae0ce0cf5c8), AE_NOT_FOUND (20160930/psparse-543)
[    0.944921] ata3.00: ATAPI: HL-DT-ST DVDRAM GH22NS40, NL02, max UDMA/100
[    0.945013] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.945280] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff8ae0ce0cfeb0), AE_NOT_FOUND (20160930/psparse-543)
[    0.945700] ata5.00: ATA-8: SAMSUNG HD204UI, 1AQ10001, max UDMA/133
[    0.945702] ata5.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[    0.947907] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.948178] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT0._GTF] (Node ffff8ae0ce0cf898), AE_NOT_FOUND (20160930/psparse-543)
[    0.948688] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    0.948964] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT2._GTF] (Node ffff8ae0ce0cf5c8), AE_NOT_FOUND (20160930/psparse-543)


Hardware is MSI Motherboard: Z77A-G41 (MS-7758)
CPU: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz
Comment 29 Daniele Ottolina 2017-05-01 10:46:06 EDT
Fedora 4.10.12-200.fc25.x86_64
I also had no issue with legacy kernel 4.8.6-300. No error is displayed in /var/log/boot.log.

Motherboard: Asus Maximus IV Extreme P67(B3)
CPU: Intel(R) Core(TM) i5-2500k CPU

[1.512663] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[1.512715] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT0._GTF] (Node ffff995e5e0d1a28), AE_NOT_FOUND (20160930/psargs-543)

[1.514341] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[1.514389] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT0._GTF] (Node ffff995e5e0d1a28), AE_NOT_FOUND (20160930/psargs-543)

[1.514498] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[1.514546] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT2._GTF] (Node ffff995e5e0d1230), AE_NOT_FOUND (20160930/psargs-543)

[1.518696] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[1.518744] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT2._GTF] (Node ffff995e5e0d1230), AE_NOT_FOUND (20160930/psargs-543)
Comment 30 Artem S. Tashkinov 2017-05-25 06:46:06 EDT
This bug has been forever - the problem is that starting with kernel 4.9 the "quiet" option no longer hides these messages.

This is its latest reincarnation: https://bugzilla.kernel.org/show_bug.cgi?id=193531
Comment 31 bugzilla 2017-09-08 05:47:36 EDT
4.12.9-300.fc26.x86_64:

[    0.026841] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170303/dswload-210)
[    0.026846] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170303/psobject-241)
[    0.026873] ACPI Exception: AE_NOT_FOUND, (SSDT:DELL_SFF) while loading table (20170303/tbxfload-228)
[    0.027661] ACPI Error: 1 table load failures, 9 successful (20170303/tbxfload-246)
[    1.033370] Couldn't get size: 0x800000000000000e
Comment 32 Pacho Ramos 2017-09-08 05:56:21 EDT
It's still valid for upstream kernel 4.13 (under Gentoo)... I guess it will be unresolved until https://github.com/acpica/acpica/pull/189/ is not merged
Comment 33 Guillem Liarte 2017-10-09 04:24:45 EDT
I can confirm for 4.13.4.200, I get the same error, which makes the computer to get stuck at boot, with kernel 4.13.4.200.fc26.

It will only boot with an older kernel, and by hitting CTRL+C when these messages show.
Comment 34 Fedora End Of Life 2017-11-16 14:40:27 EST
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Comment 35 Phil 2017-12-09 10:16:07 EST
I’m seeing this in Fedora 27, and boot is now failing here. This is also true when booting from the rescue install.

I’m running an i5 8400 on a asrock z370 fatal1ty itx/ac board.

Ctrl+c doesn’t help me but the system is responsive to ctrl+alt+del, which restarts.
Comment 36 Fedora End Of Life 2017-12-12 05:03:16 EST
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 37 Christopher Tubbs 2017-12-12 05:08:37 EST
I'm still getting the following ACPI errors in F26. The comment above indicated this was still a problem in F27.

[    0.708980] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECWT] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[    0.709047] ACPI Error: Method parse/execution failed \_TZ.FN00._ON, AE_NOT_FOUND (20170531/psparse-550)
[    0.709088] acpi PNP0C0B:00: Failed to change power state to D0
[    0.709114] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECWT] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[    0.709149] ACPI Error: Method parse/execution failed \_TZ.FN00._ON, AE_NOT_FOUND (20170531/psparse-550)
[    0.709183] acpi PNP0C0B:00: Failed to set initial power state
[    0.709217] acpi PNP0C0B:00: Cannot transition from (unknown) to D3hot
[    0.719275] (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
[    0.721445] thermal LNXTHERM:00: registered as thermal_zone0
[    0.721447] ACPI: Thermal Zone [THM] (25 C)
[    0.721531] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECRD] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[    0.721570] ACPI Error: Method parse/execution failed \_TZ.TZ00._TMP, AE_NOT_FOUND (20170531/psparse-550)
[    0.721678] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECRD] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[    0.721713] ACPI Error: Method parse/execution failed \_TZ.TZ00._TMP, AE_NOT_FOUND (20170531/psparse-550)
[    0.721783] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECRD] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[    0.721818] ACPI Error: Method parse/execution failed \_TZ.TZ01._TMP, AE_NOT_FOUND (20170531/psparse-550)
[    0.721882] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECRD] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[    0.721916] ACPI Error: Method parse/execution failed \_TZ.TZ01._TMP, AE_NOT_FOUND (20170531/psparse-550)

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