Bug 1589561 - ACPI Errors thrown on boot
Summary: ACPI Errors thrown on boot
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-10 19:57 UTC by morgan read
Modified: 2019-02-21 21:10 UTC (History)
21 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-02-21 21:10:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
$ journalctl -b --no-pager > /tmp/boot-log.txt (550.02 KB, text/plain)
2018-06-10 19:57 UTC, morgan read
no flags Details
logs for acpi problem.. (81.95 KB, text/plain)
2018-08-11 16:40 UTC, Brad Walker
no flags Details

Description morgan read 2018-06-10 19:57:13 UTC
Created attachment 1449770 [details]
$ journalctl -b --no-pager > /tmp/boot-log.txt

Description of problem:
Boot and ACPI throws errors every time


Version-Release number of selected component (if applicable):
$ acpi -v
acpi 1.7

(But I'm not sure that's the right component from the Component Description above...)


How reproducible:
Always


Steps to Reproduce:
1. boot
2.
3.

Actual results:
Errors

Expected results:
No errors

Additional info:
Following the relevant details from GNOME Logs (but, that doesn't seem to provide much context so also attached output from $ journalctl -b --no-pager > /tmp/boot-log.txt):
...
 7:35:16 PM kernel: ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180105/psparse-550)
 7:35:16 PM kernel: ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180105/psparse-550)
 7:35:16 PM kernel: ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180105/psparse-550)
 7:35:16 PM kernel: ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180105/dsopcode-235)
 7:35:16 PM kernel: ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180105/psparse-550)
 7:35:16 PM kernel: ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180105/psparse-550)
 7:35:16 PM kernel: ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180105/dsopcode-235)
 7:35:16 PM kernel: ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180105/psparse-550)
 7:35:16 PM kernel: ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180105/psparse-550)
 7:35:16 PM kernel: ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180105/dsopcode-235)
 7:35:16 PM kernel: ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180105/psparse-550)
 7:35:16 PM kernel: ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180105/psparse-550)
 7:35:16 PM kernel: ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180105/dsopcode-235)
 7:35:16 PM kernel: ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180105/psparse-550)
 7:35:16 PM kernel: ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180105/psparse-550)
 7:35:16 PM kernel: ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180105/dsopcode-235)
...

Comment 1 Justin M. Forbes 2018-07-23 14:56:51 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs.

Fedora 28 has now been rebased to 4.17.7-200.fc28.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 2 Brad Walker 2018-08-11 16:40:01 UTC
Created attachment 1475230 [details]
logs for acpi problem..

I continue to see this problem. Even after doing the Fedora lastest update.

I've attached logs..

Comment 3 Laura Abbott 2018-10-01 21:15:14 UTC
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs.
 
Fedora 28 has now been rebased to 4.18.10-300.fc28.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29.
 
If you experience different issues, please open a new bug report for those.

Comment 4 morgan read 2018-10-02 16:15:12 UTC
Yes, this is still a bug

$ sudo dnf update
[sudo] password for readlegal: 
Last metadata expiration check: 0:58:09 ago on Tue 02 Oct 2018 16:15:31 BST.
Dependencies resolved.
Nothing to do.
Complete!
$ uname -r
4.18.10-200.fc28.x86_64
$

Comment 5 Justin M. Forbes 2019-01-29 16:24:24 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs.

Fedora 28 has now been rebased to 4.20.5-100.fc28.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29.

If you experience different issues, please open a new bug report for those.

Comment 6 Justin M. Forbes 2019-02-21 21:10:56 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


Note You need to log in before you can comment on or make changes to this bug.