SystemIO conflicts are not firmware bugs
Many people misinterpret ACPI warnings like 'SystemIO range conflicts with OpRegion' as firmware bugs. In reality, these warnings occur when a native driver tries to access IO ports already claimed by an ACPI operation region, potentially causing race conditions. The kernel blocks the driver to prevent damage, and the correct solution is to use an ACPI driver instead. The firmware is not at fault; overriding the warning could lead to intermittent system hangs or worse.
The firmware did absolutely nothing wrong here, but trying to load the native driver will generate an error and the internet will tell you that PC firmware developers are incompetent and you should pass a kernel argument that overrides this behaviour and it never did them any harm, and it probably won’t do you any harm either but it might and you might never know why your system occasionally wedges or catches fire.
- dataflow
Two questions:
1. How does the kernel detect the conflict?
> you can certainly boot with acpi=off if you want to and no ACPI code will be executed at runtime
2. How does the kernel prevent the firmware from running anything?
- eqvinox
> the internet will tell you that PC firmware developers are incompetent³
> ³ I’m not going to present an opinion on that here, merely say that this provides no supporting evidence for that assertion
If anything, isn't this evidence the vendor should've paid someone to write an ACPI driver for Linux? :-)