Good evening,
One of the problems reported in the log file "rdsosreport.txt" generated by the failed boots discussed in the "f24 boot fails; need help" topic was a set of "ACPI" errors. Here are the relevant lines (with added line numbers) from that log file (the first and last lines are just for context):
----------
862 [ 1.218683] coyote kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) 863 [ 1.218927] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 864 [ 1.219196] coyote kernel: ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT1._GTF] (Node ffff92ef8e0db488), AE_NOT_FOUND (20160930/psparse-543) 865 [ 1.219856] coyote kernel: ata2.00: ATA-8: ST2000DM001-1CH164, CC24, max UDMA/133 866 [ 1.220017] coyote kernel: ata2.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA 867 [ 1.220812] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 868 [ 1.221100] coyote kernel: ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT1._GTF] (Node ffff92ef8e0db488), AE_NOT_FOUND (20160930/psparse-543) 869 [ 1.221620] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 870 [ 1.221909] coyote kernel: ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT5._GTF] (Node ffff92ef8e0dbac8), AE_NOT_FOUND (20160930/psparse-543) 871 [ 1.222200] coyote kernel: ata6.00: ATAPI: HL-DT-ST BD-RE BH14NS40, 1.00, max UDMA/100 872 [ 1.222374] coyote kernel: ata2.00: configured for UDMA/133 873 [ 1.222582] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 874 [ 1.222908] coyote kernel: ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT3._GTF] (Node ffff92ef8e0db348), AE_NOT_FOUND (20160930/psparse-543) 875 [ 1.222919] coyote kernel: scsi 1:0:0:0: Direct-Access ATA ST2000DM001-1CH1 CC24 PQ: 0 ANSI: 5 876 [ 1.223466] coyote kernel: ata4.00: ATAPI: PIONEER BD-RW BDR-208M, 1.10, max UDMA/100 877 [ 1.226360] coyote kernel: ata7: SATA link down (SStatus 0 SControl 300) 878 [ 1.226407] coyote kernel: ata9: SATA link down (SStatus 0 SControl 300) 879 [ 1.226501] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 880 [ 1.226507] coyote kernel: ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT5._GTF] (Node ffff92ef8e0dbac8), AE_NOT_FOUND (20160930/psparse-543) 881 [ 1.226519] coyote kernel: ata6.00: configured for UDMA/100 882 [ 1.227197] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 883 [ 1.227204] coyote kernel: ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT3._GTF] (Node ffff92ef8e0db348), AE_NOT_FOUND (20160930/psparse-543) 884 [ 1.227217] coyote kernel: ata4.00: configured for UDMA/100
----------
What is this all about? Is this a real problem or a false alarm? How do I fix it?
thanks, Bill.
On Fri, 19 May 2017 18:09:21 -0600 William mattison.computer@yahoo.com wrote:
Good evening,
One of the problems reported in the log file "rdsosreport.txt" generated by the failed boots discussed in the "f24 boot fails; need help" topic was a set of "ACPI" errors. Here are the relevant lines (with added line numbers) from that log file (the first and last lines are just for context):
863 [ 1.218927] coyote kernel: ACPI Error: [DSSP]Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[snip]
883 [ 1.227204] coyote kernel: ACPI Error: Methodparse/execution failed [_SB.PCI0.SAT0.SPT3._GTF] (Node ffff92ef8e0db348), AE_NOT_FOUND (20160930/psparse-543)
What is this all about? Is this a real problem or a false alarm? How do I fix it?
Is it still there? It might have been related to the disk problem, since it occurred during disk device discovery. Check by typing journalctl -b and looking for AE_NOT_FOUND, using /AE_NOT_FOUND as the command.
1. For several weeks, I've been seeing text fly by early during the boot process, before the blue and white line grows left to right at the bottom of the screen. But the text scrolls by too fast and disappears too fast for me to catch more than an isolated word or two. I also had no idea how to access appropriate logs. Then came the boot failure. I did what the dracut shell said, and I recognized that the first set of lines that I posted in one of the boot failure postings quite possibly was the text I had been seeing during boots for the past several weeks. 2. Since the boot problem was fixed, I continue to see what I believe is the same text, the same way as before the boot failure problem. As you advised, I did the journalctl command. I routed the output to a text file, and then did a "cat -n" to another file so we would have line numbers. Here's the result, with line numbers and an extra couple lines at the beginning and end for context:
---------------
698 May 21 11:22:13 coyote kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) 699 May 21 11:22:13 coyote kernel: ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) 700 May 21 11:22:13 coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 701 May 21 11:22:13 coyote kernel: ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT1._GTF] (Node ffff8db5ce0db2a8), AE_NOT_FOUND (20160930/psparse-543) 702 May 21 11:22:13 coyote kernel: ata2.00: ATA-8: ST2000DM001-1CH164, CC24, max UDMA/133 703 May 21 11:22:13 coyote kernel: ata2.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA 704 May 21 11:22:13 coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 705 May 21 11:22:13 coyote kernel: ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT1._GTF] (Node ffff8db5ce0db2a8), AE_NOT_FOUND (20160930/psparse-543) 706 May 21 11:22:13 coyote kernel: ata2.00: configured for UDMA/133 707 May 21 11:22:13 coyote kernel: scsi 1:0:0:0: Direct-Access ATA ST2000DM001-1CH1 CC24 PQ: 0 ANSI: 5 708 May 21 11:22:13 coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 709 May 21 11:22:13 coyote kernel: ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT5._GTF] (Node ffff8db5ce0db2f8), AE_NOT_FOUND (20160930/psparse-543) 710 May 21 11:22:13 coyote kernel: ata6.00: ATAPI: HL-DT-ST BD-RE BH14NS40, 1.00, max UDMA/100 711 May 21 11:22:13 coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 712 May 21 11:22:13 coyote kernel: ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT3._GTF] (Node ffff8db5ce0db528), AE_NOT_FOUND (20160930/psparse-543) 713 May 21 11:22:13 coyote kernel: ata4.00: ATAPI: PIONEER BD-RW BDR-208M, 1.10, max UDMA/100 714 May 21 11:22:13 coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 715 May 21 11:22:13 coyote kernel: ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT3._GTF] (Node ffff8db5ce0db528), AE_NOT_FOUND (20160930/psparse-543) 716 May 21 11:22:13 coyote kernel: ata4.00: configured for UDMA/100 717 May 21 11:22:13 coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 718 May 21 11:22:13 coyote kernel: ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT5._GTF] (Node ffff8db5ce0db2f8), AE_NOT_FOUND (20160930/psparse-543) 719 May 21 11:22:13 coyote kernel: ata6.00: configured for UDMA/100 720 May 21 11:22:13 coyote kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0
---------------
So yes, the problem is still there. (And now I know a way of getting to boot logs!)
Thank-you for you help so far. Bill.
On Mon, 22 May 2017 02:15:59 -0000 "William Mattison" mattison.computer@yahoo.com wrote:
- For several weeks, I've been seeing text fly by early during the
boot process, before the blue and white line grows left to right at the bottom of the screen. But the text scrolls by too fast and disappears too fast for me to catch more than an isolated word or two. I also had no idea how to access appropriate logs. Then came the boot failure. I did what the dracut shell said, and I recognized that the first set of lines that I posted in one of the boot failure postings quite possibly was the text I had been seeing during boots for the past several weeks. 2. Since the boot problem was fixed, I continue to see what I believe is the same text, the same way as before the boot failure problem. As you advised, I did the journalctl command. I routed the output to a text file, and then did a "cat -n" to another file so we would have line numbers. Here's the result, with line numbers and an extra couple lines at the beginning and end for context:
[snip]
So yes, the problem is still there. (And now I know a way of getting to boot logs!)
This appears to be a common problem. There is a bugzilla, and it doesn't have a solution, though some people report that later kernels don't have the issue for them. People also report that 4.8 kernels did not display these errors.
The general consensus is that these messages are warnings more than errors, that they occur because the linux kernel finds errors in BIOS code and reports them, and that they don't impact the operation of the computer. I am not an expert about this, so just take my observations as a data point.
I'm running a test 4.12 kernel locally compiled on F25, and I see only a single message about this in my logs. kernel: acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM and don't seem to observe any ill effects.
This is the bug report. https://bugzilla.redhat.com/show_bug.cgi?id=1413342
More information, not Fedora related, here. http://www.linuxquestions.org/questions/slackware-14/acpi-error-%5Bdssp%5D-n...
Good afternoon,
Based on Stan's most recent posting on this issue, I believe I can close this as being a non-issue.
Thank-you. Bill.
On 05/19/2017 06:09 PM, William wrote:
Good evening,
One of the problems reported in the log file "rdsosreport.txt" generated by the failed boots discussed in the "f24 boot fails; need help" topic was a set of "ACPI" errors. Here are the relevant lines (with added line numbers) from that log file (the first and last lines are just for context):
862 [ 1.218683] coyote kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) 863 [ 1.218927] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 864 [ 1.219196] coyote kernel: ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT1._GTF] (Node ffff92ef8e0db488), AE_NOT_FOUND (20160930/psparse-543) 865 [ 1.219856] coyote kernel: ata2.00: ATA-8: ST2000DM001-1CH164, CC24, max UDMA/133 866 [ 1.220017] coyote kernel: ata2.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA 867 [ 1.220812] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 868 [ 1.221100] coyote kernel: ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT1._GTF] (Node ffff92ef8e0db488), AE_NOT_FOUND (20160930/psparse-543) 869 [ 1.221620] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 870 [ 1.221909] coyote kernel: ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT5._GTF] (Node ffff92ef8e0dbac8), AE_NOT_FOUND (20160930/psparse-543) 871 [ 1.222200] coyote kernel: ata6.00: ATAPI: HL-DT-ST BD-RE BH14NS40, 1.00, max UDMA/100 872 [ 1.222374] coyote kernel: ata2.00: configured for UDMA/133 873 [ 1.222582] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 874 [ 1.222908] coyote kernel: ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT3._GTF] (Node ffff92ef8e0db348), AE_NOT_FOUND (20160930/psparse-543) 875 [ 1.222919] coyote kernel: scsi 1:0:0:0: Direct-Access ATA ST2000DM001-1CH1 CC24 PQ: 0 ANSI: 5 876 [ 1.223466] coyote kernel: ata4.00: ATAPI: PIONEER BD-RW BDR-208M, 1.10, max UDMA/100 877 [ 1.226360] coyote kernel: ata7: SATA link down (SStatus 0 SControl 300) 878 [ 1.226407] coyote kernel: ata9: SATA link down (SStatus 0 SControl 300) 879 [ 1.226501] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 880 [ 1.226507] coyote kernel: ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT5._GTF] (Node ffff92ef8e0dbac8), AE_NOT_FOUND (20160930/psparse-543) 881 [ 1.226519] coyote kernel: ata6.00: configured for UDMA/100 882 [ 1.227197] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 883 [ 1.227204] coyote kernel: ACPI Error: Method parse/execution failed [_SB.PCI0.SAT0.SPT3._GTF] (Node ffff92ef8e0db348), AE_NOT_FOUND (20160930/psparse-543) 884 [ 1.227217] coyote kernel: ata4.00: configured for UDMA/100
What is this all about? Is this a real problem or a false alarm? How do I fix it?
thanks, Bill.
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.
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.
(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.
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
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?
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
-
home user -
Patrick O'Callaghan -
stan -
William
-
William Mattison