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@xxxxxxxxxxx>:
Depends on what you've learned from your googling. If you found that folks had failures
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?
>
>
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@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@lists.fedoraproject.org
--
PGP: 06853DF7
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
