Re: ACPI errors (was: f24 boot fails; need help). [CLOSED] [SOLVED]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> > (f-28)  I closed this about a year and a half ago because a bug was
> > already filed regarding the issue.  For the past few days, both
> > before and after doing my latest weekly patches, I noticed that
> > those "ACPI Error" messages no longer show up while the workstation
> > is booting.  So I'm promoting this thread from "CLOSED" to "SOLVED".
> > My thanks to the  people fixed the problem.  I hope it's fixed for
> > everyone else who  experienced the problem.

(Patrick said)
> You mean these?:
> Dec 15 09:44:39 bree kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) > Dec 15 09:44:39 bree kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT3._GTF, AE_NOT_FOUND (20180810/psparse-516)
> [... snip ...]
> Dec 15 09:44:39 bree kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) > Dec 15 09:44:39 bree kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20180810/psparse-516)

Those are boot error messages from your system on Dec. 15?
What I saw on my workstation in May(?) 2017 were these:
---------------
[ 1.218927] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) [ 1.219196] coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff92ef8e0db488), AE_NOT_FOUND (20160930/psparse-543) [ 1.219856] coyote kernel: ata2.00: ATA-8: ST2000DM001-1CH164, CC24, max UDMA/133 [ 1.220017] coyote kernel: ata2.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 1.220812] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) [ 1.221100] coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff92ef8e0db488), AE_NOT_FOUND (20160930/psparse-543) [ 1.221620] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) [ 1.221909] coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff92ef8e0dbac8), AE_NOT_FOUND (20160930/psparse-543) [ 1.222200] coyote kernel: ata6.00: ATAPI: HL-DT-ST BD-RE BH14NS40, 1.00, max UDMA/100
[ 1.222374] coyote kernel: ata2.00: configured for UDMA/133
[ 1.222582] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) [ 1.222908] coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT3._GTF] (Node ffff92ef8e0db348), AE_NOT_FOUND (20160930/psparse-543) [ 1.222919] coyote kernel: scsi 1:0:0:0: Direct-Access ATA ST2000DM001-1CH1 CC24 PQ: 0 ANSI: 5 [ 1.223466] coyote kernel: ata4.00: ATAPI: PIONEER BD-RW BDR-208M, 1.10, max UDMA/100
[ 1.226360] coyote kernel: ata7: SATA link down (SStatus 0 SControl 300)
[ 1.226407] coyote kernel: ata9: SATA link down (SStatus 0 SControl 300)
[ 1.226501] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) [ 1.226507] coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff92ef8e0dbac8), AE_NOT_FOUND (20160930/psparse-543)
[ 1.226519] coyote kernel: ata6.00: configured for UDMA/100
[ 1.227197] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) [ 1.227204] coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT3._GTF] (Node ffff92ef8e0db348), AE_NOT_FOUND (20160930/psparse-543)
---------------
> poc

So you're still having the problem? (I notice your messages are dated Dec. 15.) Either the weekly patches (dnf upgrade) fixed the problem on my workstation, or just maybe doing "grub2-mkconfig -o /etc/grub2.cfg" to get rid of grub error messages fixed the problem (separate thread).

> PS Please quote context when posting via the web page. It doesn't do
> so automatically. Or use a real mail client.

understood.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux