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

2018-12-19 Thread Patrick O'Callaghan
On Tue, 2018-12-18 at 13:20 -0700, home user via users wrote:
> Patrick said
>  > >  So you're still having the problem?...
>  > Yes.
> and
>  > I update my system every morning. Not sure how
>  > grub2-mkconfig would help.
> 
> Then I think it was just a coincidence for me.
> 
> This is now way over my pay-grade, and way beyond my training and 
> experience.  Can someone else help Patrick?

It doesn't bother me. I've been getting these messages for years and
have concluded that they are due to a non-compliant ACPI implementation
in my mobo, which apparently is quite common. It would be nice to turn
off the messages but that's all.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org


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

2018-12-18 Thread home user via users

Patrick said
> >  So you're still having the problem?...
> Yes.
and
> I update my system every morning. Not sure how
> grub2-mkconfig would help.

Then I think it was just a coincidence for me.

This is now way over my pay-grade, and way beyond my training and 
experience.  Can someone else help Patrick?

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org


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

2018-12-17 Thread Patrick O'Callaghan
On Sun, 2018-12-16 at 20:24 -0700, home user via users wrote:
> So you're still having the problem?  (I notice your messages are dated 
> Dec. 15.)

Yes.

> 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).

I update my system every morning. Not sure how grub2-mkconfig would
help. (I looked at its output and although it's different from what I
currently have I didn't see anything obviously related to this).


poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org


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

2018-12-16 Thread home user via users


> > (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 92ef8e0db488), 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 92ef8e0db488), 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 92ef8e0dbac8), AE_NOT_FOUND 
(20160930/psparse-543)
[ 1.00] 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 92ef8e0db348), 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 92ef8e0dbac8), 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 92ef8e0db348), 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@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org


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

2018-12-16 Thread Patrick O'Callaghan
On Sun, 2018-12-16 at 15:04 -0700, home user via users wrote:
> Good afternoon,
> 
> (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.

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)
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)
Dec 15 09:44:39 bree kernel: ACPI BIOS Error (bug): Could not resolve 
[\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
Dec 15 09:44:39 bree kernel: ACPI Error: Method parse/execution failed 
\_SB.PCI0.SAT0.SPT2._GTF, AE_NOT_FOUND (20180810/psparse-516)
Dec 15 09:44:39 bree kernel: ACPI BIOS Error (bug): Could not resolve 
[\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
Dec 15 09:44:39 bree kernel: ACPI Error: Method parse/execution failed 
\_SB.PCI0.SAT0.SPT2._GTF, AE_NOT_FOUND (20180810/psparse-516)
Dec 15 09:44:39 bree kernel: ACPI BIOS Error (bug): Could not resolve 
[\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
Dec 15 09:44:39 bree kernel: ACPI Error: Method parse/execution failed 
\_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20180810/psparse-516)
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)
Dec 15 09:44:39 bree kernel: ACPI BIOS Error (bug): Could not resolve 
[\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
Dec 15 09:44:39 bree kernel: ACPI Error: Method parse/execution failed 
\_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20180810/psparse-516)
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)

poc

PS Please quote context when posting via the web page. It doesn't do so
automatically. Or use a real mail client.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org


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

2018-12-16 Thread home user via users

Good afternoon,

(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.


Bill.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org