ACPI errors at boot

[Patrick O'Callaghan]

I just updated to kernel 4.9.3-200.fc25.x86_64 and am now seeing this
on boot:

Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
(20160831/psargs-359)
Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
[\_SB.PCI0.SAT0.SPT2._GTF] (Node ffff8e820d0ce5c8), AE_NOT_FOUND (20160831/psparse-543)
Jan 16 11:07:14 bree kernel: ata3.00: ATA-8: TOSHIBA DT01ACA100, MS2OA750, max UDMA/133
Jan 16 11:07:14 bree kernel: ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth
31/32), AA
Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
(20160831/psargs-359)
Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
[\_SB.PCI0.SAT0.SPT0._GTF] (Node ffff8e820d0ce410), AE_NOT_FOUND (20160831/psparse-543)
Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
(20160831/psargs-359)
Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
[\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff8e820d0cea78), AE_NOT_FOUND (20160831/psparse-543)
Jan 16 11:07:14 bree kernel: ata2.00: ATAPI: TSSTcorp CDDVDW SH-224BB, SB00, max UDMA/100
Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
(20160831/psargs-359)
Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
[\_SB.PCI0.SAT0.SPT2._GTF] (Node ffff8e820d0ce5c8), AE_NOT_FOUND (20160831/psparse-543)
Jan 16 11:07:14 bree kernel: ata1.00: supports DRM functions and may not be fully
accessible
Jan 16 11:07:14 bree kernel: ata3.00: configured for UDMA/133
Jan 16 11:07:14 bree kernel: ata1.00: NCQ Send/Recv Log not supported
Jan 16 11:07:14 bree kernel: ata1.00: ATA-9: Samsung SSD 840 EVO 120GB, EXT0BB6Q, max
UDMA/133
Jan 16 11:07:14 bree kernel: ata1.00: 234441648 sectors, multi 1: LBA48 NCQ (depth 31/32),
AA
Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
(20160831/psargs-359)
Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
[\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff8e820d0cea78), AE_NOT_FOUND (20160831/psparse-543)
Jan 16 11:07:14 bree kernel: ata2.00: configured for UDMA/100
Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
(20160831/psargs-359)
Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
[\_SB.PCI0.SAT0.SPT0._GTF] (Node ffff8e820d0ce410), AE_NOT_FOUND (20160831/psparse-543)

However the boot proceeds and the system seems OK for the moment. I'm
mentioning this because it's new for me, but Google shows a number of
similar reports going back several years.

Should I worry?

poc

[Ed Greshko]

On 01/16/17 19:16, Patrick O'Callaghan wrote:
>  I just updated to kernel 4.9.3-200.fc25.x86_64 and am now seeing
> this
>  on boot:
>
>  Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
> (20160831/psargs-359)
>  Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
> [\_SB.PCI0.SAT0.SPT2._GTF] (Node ffff8e820d0ce5c8), AE_NOT_FOUND (20160831/psparse-543)
>  Jan 16 11:07:14 bree kernel: ata3.00: ATA-8: TOSHIBA DT01ACA100, MS2OA750, max UDMA/133
>  Jan 16 11:07:14 bree kernel: ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth
> 31/32), AA
>  Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
> (20160831/psargs-359)
>  Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
> [\_SB.PCI0.SAT0.SPT0._GTF] (Node ffff8e820d0ce410), AE_NOT_FOUND (20160831/psparse-543)
>  Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
> (20160831/psargs-359)
>  Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
> [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff8e820d0cea78), AE_NOT_FOUND (20160831/psparse-543)
>  Jan 16 11:07:14 bree kernel: ata2.00: ATAPI: TSSTcorp CDDVDW SH-224BB, SB00, max
> UDMA/100
>  Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
> (20160831/psargs-359)
>  Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
> [\_SB.PCI0.SAT0.SPT2._GTF] (Node ffff8e820d0ce5c8), AE_NOT_FOUND (20160831/psparse-543)
>  Jan 16 11:07:14 bree kernel: ata1.00: supports DRM functions and may not be fully
> accessible
>  Jan 16 11:07:14 bree kernel: ata3.00: configured for UDMA/133
>  Jan 16 11:07:14 bree kernel: ata1.00: NCQ Send/Recv Log not supported
>  Jan 16 11:07:14 bree kernel: ata1.00: ATA-9: Samsung SSD 840 EVO 120GB, EXT0BB6Q, max
> UDMA/133
>  Jan 16 11:07:14 bree kernel: ata1.00: 234441648 sectors, multi 1: LBA48 NCQ (depth
> 31/32), AA
>  Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
> (20160831/psargs-359)
>  Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
> [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff8e820d0cea78), AE_NOT_FOUND (20160831/psparse-543)
>  Jan 16 11:07:14 bree kernel: ata2.00: configured for UDMA/100
>  Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
> (20160831/psargs-359)
>  Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
> [\_SB.PCI0.SAT0.SPT0._GTF] (Node ffff8e820d0ce410), AE_NOT_FOUND (20160831/psparse-543)
>
>  However the boot proceeds and the system seems OK for the moment. I'm
>  mentioning this because it's new for me, but Google shows a number of
>  similar reports going back several years.
>
>  Should I worry?
>
>  
Depends on what you've learned from your googling.   If you found that folks
had failures
after seeing these messages and ended up replacing HW to fix it, yes by all means worry.

If you found out that folks got the messages but experienced no ill effects or they
changed a setting or something else and the issue went away....then probably no need to
worry.

I suppose it is safe to assume you've booted again into an earlier kernel and
didn't see
those errors?  So, just something that the latest kernel is checking that wasn't
being
checked before and is harmless is likely.


-- 
Fedora Users List - The place to go to get others to do the work for you

[Zoltan Hoppar]

The real problem is not only that acpi faliures, else that Intel 915 fifo
buffer underrun error has came back, and returns every time when I get
kernel update. Worse, because WMI is also messed up, and I needed to return
3 kernel versions back and run the whole system on X instead of wayland. I
don't know, I really annoying that every kernel has this flickering bug,
and freezing out my machine so deeply that I loose my monitors when it gets
sleep or suspend.

Z

2017-01-16 14:50 GMT+01:00 Ed Greshko <ed.greshko(a)greshko.com&gt;:

>  On 01/16/17 19:16, Patrick O'Callaghan wrote:
>  > I just updated to kernel 4.9.3-200.fc25.x86_64 and am now seeing this
>  > on boot:
>  >
>  > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup
>  failure, AE_NOT_FOUND (20160831/psargs-359)
>  > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
>  [\_SB.PCI0.SAT0.SPT2._GTF] (Node ffff8e820d0ce5c8), AE_NOT_FOUND
>  (20160831/psparse-543)
>  > Jan 16 11:07:14 bree kernel: ata3.00: ATA-8: TOSHIBA DT01ACA100,
>  MS2OA750, max UDMA/133
>  > Jan 16 11:07:14 bree kernel: ata3.00: 1953525168 sectors, multi 16:
>  LBA48 NCQ (depth 31/32), AA
>  > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup
>  failure, AE_NOT_FOUND (20160831/psargs-359)
>  > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
>  [\_SB.PCI0.SAT0.SPT0._GTF] (Node ffff8e820d0ce410), AE_NOT_FOUND
>  (20160831/psparse-543)
>  > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup
>  failure, AE_NOT_FOUND (20160831/psargs-359)
>  > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
>  [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff8e820d0cea78), AE_NOT_FOUND
>  (20160831/psparse-543)
>  > Jan 16 11:07:14 bree kernel: ata2.00: ATAPI: TSSTcorp CDDVDW SH-224BB,
>  SB00, max UDMA/100
>  > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup
>  failure, AE_NOT_FOUND (20160831/psargs-359)
>  > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
>  [\_SB.PCI0.SAT0.SPT2._GTF] (Node ffff8e820d0ce5c8), AE_NOT_FOUND
>  (20160831/psparse-543)
>  > Jan 16 11:07:14 bree kernel: ata1.00: supports DRM functions and may not
>  be fully accessible
>  > Jan 16 11:07:14 bree kernel: ata3.00: configured for UDMA/133
>  > Jan 16 11:07:14 bree kernel: ata1.00: NCQ Send/Recv Log not supported
>  > Jan 16 11:07:14 bree kernel: ata1.00: ATA-9: Samsung SSD 840 EVO 120GB,
>  EXT0BB6Q, max UDMA/133
>  > Jan 16 11:07:14 bree kernel: ata1.00: 234441648 sectors, multi 1: LBA48
>  NCQ (depth 31/32), AA
>  > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup
>  failure, AE_NOT_FOUND (20160831/psargs-359)
>  > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
>  [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff8e820d0cea78), AE_NOT_FOUND
>  (20160831/psparse-543)
>  > Jan 16 11:07:14 bree kernel: ata2.00: configured for UDMA/100
>  > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup
>  failure, AE_NOT_FOUND (20160831/psargs-359)
>  > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
>  [\_SB.PCI0.SAT0.SPT0._GTF] (Node ffff8e820d0ce410), AE_NOT_FOUND
>  (20160831/psparse-543)
>  >
>  > However the boot proceeds and the system seems OK for the moment. I'm
>  > mentioning this because it's new for me, but Google shows a number of
>  > similar reports going back several years.
>  >
>  > Should I worry?
>  >
>  >
>  Depends on what you've learned from your googling.   If you found that
>  folks had failures
>  after seeing these messages and ended up replacing HW to fix it, yes by
>  all means worry.
>
>  If you found out that folks got the messages but experienced no ill
>  effects or they
>  changed a setting or something else and the issue went away....then
>  probably no need to worry.
>
>  I suppose it is safe to assume you've booted again into an earlier kernel
>  and didn't see
>  those errors?  So, just something that the latest kernel is checking that
>  wasn't being
>  checked before and is harmless is likely.
>
>
>  --
>  Fedora Users List - The place to go to get others to do the work for you
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>  


-- 
PGP:  06853DF7

[Patrick O'Callaghan]

On Mon, 2017-01-16 at 21:50 +0800, Ed Greshko wrote:
>  
>  On 01/16/17 19:16, Patrick O'Callaghan wrote:
>  > I just updated to kernel 4.9.3-200.fc25.x86_64 and am now seeing this
>  > on boot:
>  > 
>  > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure,
> AE_NOT_FOUND (20160831/psargs-359)
>  > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
> [\_SB.PCI0.SAT0.SPT2._GTF] (Node ffff8e820d0ce5c8), AE_NOT_FOUND (20160831/psparse-543)
>  > Jan 16 11:07:14 bree kernel: ata3.00: ATA-8: TOSHIBA DT01ACA100, MS2OA750, max
> UDMA/133
>  > Jan 16 11:07:14 bree kernel: ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth
> 31/32), AA
>  > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure,
> AE_NOT_FOUND (20160831/psargs-359)
>  > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
> [\_SB.PCI0.SAT0.SPT0._GTF] (Node ffff8e820d0ce410), AE_NOT_FOUND (20160831/psparse-543)
>  > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure,
> AE_NOT_FOUND (20160831/psargs-359)
>  > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
> [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff8e820d0cea78), AE_NOT_FOUND (20160831/psparse-543)
>  > Jan 16 11:07:14 bree kernel: ata2.00: ATAPI: TSSTcorp CDDVDW SH-224BB, SB00, max
> UDMA/100
>  > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure,
> AE_NOT_FOUND (20160831/psargs-359)
>  > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
> [\_SB.PCI0.SAT0.SPT2._GTF] (Node ffff8e820d0ce5c8), AE_NOT_FOUND (20160831/psparse-543)
>  > Jan 16 11:07:14 bree kernel: ata1.00: supports DRM functions and may not be fully
> accessible
>  > Jan 16 11:07:14 bree kernel: ata3.00: configured for UDMA/133
>  > Jan 16 11:07:14 bree kernel: ata1.00: NCQ Send/Recv Log not supported
>  > Jan 16 11:07:14 bree kernel: ata1.00: ATA-9: Samsung SSD 840 EVO 120GB, EXT0BB6Q,
> max UDMA/133
>  > Jan 16 11:07:14 bree kernel: ata1.00: 234441648 sectors, multi 1: LBA48 NCQ (depth
> 31/32), AA
>  > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure,
> AE_NOT_FOUND (20160831/psargs-359)
>  > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
> [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff8e820d0cea78), AE_NOT_FOUND (20160831/psparse-543)
>  > Jan 16 11:07:14 bree kernel: ata2.00: configured for UDMA/100
>  > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure,
> AE_NOT_FOUND (20160831/psargs-359)
>  > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed
> [\_SB.PCI0.SAT0.SPT0._GTF] (Node ffff8e820d0ce410), AE_NOT_FOUND (20160831/psparse-543)
>  > 
>  > However the boot proceeds and the system seems OK for the moment. I'm
>  > mentioning this because it's new for me, but Google shows a number of
>  > similar reports going back several years.
>  > 
>  > Should I worry?
>  > 
>  > 
>  
>  Depends on what you've learned from your googling.   If you found that folks had
> failures
>  after seeing these messages and ended up replacing HW to fix it, yes by all means worry.
>  
>  If you found out that folks got the messages but experienced no ill effects or they
>  changed a setting or something else and the issue went away....then probably no need to
> worry.
>  
>  I suppose it is safe to assume you've booted again into an earlier kernel and
> didn't see
>  those errors?  So, just something that the latest kernel is checking that wasn't
> being
>  checked before and is harmless is likely. 
I rebooted as you say and some of the errors are there while others
aren't (basically the namespace loojup failure is not there while the
parse/execution error is). Also, in the new kernel these errors are
flagged in red, which is why I saw them. In the earlier kernel they
aren't in red.

I'll probably do nothing unless the situation repeats in the next
update. So far I haven't seen any consequences.

poc

[Patrick O'Callaghan]

On Mon, 2017-01-16 at 16:42 +0100, Zoltan Hoppar wrote:
>  The real problem is not only that acpi faliures, else that Intel 915
> fifo
>  buffer underrun error has came back, and returns every time when I get
>  kernel update. Worse, because WMI is also messed up, and I needed to return
>  3 kernel versions back and run the whole system on X instead of wayland. I
>  don't know, I really annoying that every kernel has this flickering bug,
>  and freezing out my machine so deeply that I loose my monitors when it gets
>  sleep or suspend. 
Nothing in my message relates to Intel 915. Also, I'm not running
Wayland.

poc

[Andre Robatino]

I've seen errors somewhat similar to that on my machine since I bought it almost 3
years ago, and have always interpreted them as due to a BIOS bug (I'm using the latest
BIOS). Doesn't cause any problems AFAICT.

[    0.125788] ACPI Error: [CAPB] Namespace lookup failure, AE_ALREADY_EXISTS (2
0160831/dsfield-211)
[    0.125939] ACPI Error: Method parse/execution failed [\_SB.PCI0._OSC] (Node 
ffff8dbaedc9d488), AE_ALREADY_EXISTS (20160831/psparse-543)
[    0.126079] acpi PNP0A03:00: _OSC failed (AE_ALREADY_EXISTS); disabling ASPM
[    0.126147] acpi PNP0A03:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 0
0-10] only partially covers this bridge
[    0.126595] acpi PNP0A03:00: host bridge window expanded to [mem 0xe0000000-0
xfffffffe window]; [mem 0xfed40000-0xfed4ffff window] ignored

[Patrick O'Callaghan]

On Tue, 2017-01-17 at 20:15 +0000, Andre Robatino wrote:
>  I've seen errors somewhat similar to that on my machine since I
> bought it almost 3 years ago, and have always interpreted them as due to a BIOS bug
> (I'm using the latest BIOS). Doesn't cause any problems AFAICT.
>  
>  [    0.125788] ACPI Error: [CAPB] Namespace lookup failure, AE_ALREADY_EXISTS (2
>  0160831/dsfield-211)
>  [    0.125939] ACPI Error: Method parse/execution failed [\_SB.PCI0._OSC] (Node 
>  ffff8dbaedc9d488), AE_ALREADY_EXISTS (20160831/psparse-543)
>  [    0.126079] acpi PNP0A03:00: _OSC failed (AE_ALREADY_EXISTS); disabling ASPM
>  [    0.126147] acpi PNP0A03:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 0
>  0-10] only partially covers this bridge
>  [    0.126595] acpi PNP0A03:00: host bridge window expanded to [mem 0xe0000000-0
>  xfffffffe window]; [mem 0xfed40000-0xfed4ffff window] ignored 
OK, I was concerned because they are now flagged in red, and because
they appear on the console at boot, which they did not do before (this
is why I hadn't noticed them).

poc