Bug 1080453 - ACPI Warning: SystemIO range errors
ACPI Warning: SystemIO range errors
Status: RESOLVED NORESPONSE
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Kernel
Current
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: E-mail List
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-02-11 04:03 UTC by John Shand
Modified: 2018-10-07 19:59 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
jslaby: needinfo? (jshand2013)


Attachments
dmesg with 4.16.12-3-default (63.71 KB, text/plain)
2018-06-16 20:20 UTC, John Shand
Details
hwinfo with 4.16.12-3-default (754.59 KB, text/plain)
2018-06-16 20:22 UTC, John Shand
Details
journalctl with 4.16.12-3-default (215.65 KB, text/plain)
2018-06-16 20:30 UTC, John Shand
Details

Note You need to log in before you can comment on or make changes to this bug.
Description John Shand 2018-02-11 04:03:01 UTC
ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20170831/utaddress-247)

ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20170831/utaddress-247)

ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20170831/utaddress-247)

ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20170831/utaddress-247)

ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

i'm not sure if these errors are serious or not.  someone said they are overlapping in some way
Comment 1 Jiri Slaby 2018-06-16 12:14:57 UTC
Does this still happen with 4.17?
Comment 2 John Shand 2018-06-16 20:20:27 UTC
Created attachment 774283 [details]
dmesg with 4.16.12-3-default
Comment 3 John Shand 2018-06-16 20:21:28 UTC
i am not using the 4.17 kernel yet, so it is still happening in some way or another
Comment 4 John Shand 2018-06-16 20:22:58 UTC
Created attachment 774284 [details]
hwinfo with 4.16.12-3-default
Comment 5 John Shand 2018-06-16 20:30:42 UTC
Created attachment 774285 [details]
journalctl with 4.16.12-3-default
Comment 6 John Shand 2018-10-07 19:59:56 UTC
This issue doesn't seem to cause any issues with the function of this wonderful os