Bug 86561

Summary: SystemIO range conflicts with OpRegion \_SB_.PCI0.SBUS.SMBI
Product: ACPI Reporter: Tigran Gabrielyan (tigrangab)
Component: BIOSAssignee: acpi_bios
Status: CLOSED DOCUMENTED    
Severity: normal CC: abandonedaccountubdprczb8hs, alan, benssonrob, hi-angel, rui.zhang, shawn.starr, tigrangab, upuldi
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 3.17.1 Subsystem:
Regression: No Bisected commit-id:
Attachments: dsdt.dsl
fwts results
dmesg
you can have my entire dmesg log just in case

Description Tigran Gabrielyan 2014-10-20 01:21:46 UTC
Created attachment 154201 [details]
dsdt.dsl

I get the following MCE when resuming from standby under Linux. As far as I can tell, it does not occur when resuming from standby under Windows.

I've tested the CPU and RAM and both function normally under load (no MCE generated, only happens when resuming from standby).

Can that conflict be the cause of the MCE?

I have attached the dsdt and the result of fwts. I will provide any other information that is needed.

Hardware event. This is not a software error.
MCE 0
CPU 0 BANK 5 
MISC 38a0000086 ADDR fef873c0 
TIME 1413760957 Sun Oct 19 16:22:37 2014
MCG status:
MCi status:
Uncorrected error
MCi_MISC register valid
MCi_ADDR register valid
Processor context corrupt
MCA: corrected filtering (some unreported errors in same region)
Generic CACHE Level-2 Generic Error
STATUS ae0000000040110a MCGSTATUS 0
MCGCAP c07 APICID 0 SOCKETID 0 
CPUID Vendor Intel Family 6 Model 69


lspci:
00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b)
00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4)
00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4)
00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)
02:00.0 Network controller: Intel Corporation Wireless 3160 (rev 93)
Comment 1 Tigran Gabrielyan 2014-10-20 01:22:25 UTC
Created attachment 154211 [details]
fwts results
Comment 2 Tigran Gabrielyan 2014-10-20 01:23:01 UTC
Created attachment 154221 [details]
dmesg
Comment 3 Alan 2014-10-23 13:50:12 UTC
Very hard to say from the trace. It could be an indication of some kind of problem with overlapping conflicting page types (cached/uncached) if it's only showing up in this precise situation.
Comment 4 Shawn Starr 2014-12-28 01:32:23 UTC
I see this on my Haswell (Dell M6800) laptop also:

[   10.637062] ACPI Warning: SystemIO range 0x000000000000f040-0x000000000000f05f conflicts with OpRegion 0x000000000000f040-0x000000000000f04f (\_SB_.PCI0.SBUS.SMBI) (20141107/utaddress-258)

However, no MCE happens on suspend/resume.
Comment 5 abandoned account 2015-01-18 13:12:54 UTC
Created attachment 163701 [details]
you can have my entire dmesg log just in case

I don't use suspend/resume and I haven't seen any MCEs. 
This just happens to me on boot:
...
[   11.188649] systemd[1]: Started udev Kernel Device Manager.
[   11.386071] bus: 'pci': add driver piix4_smbus
[   11.388157] bus: 'pci': driver_probe_device: matched device 0000:00:14.0 with driver piix4_smbus
[   11.388266] device class 'sound': registering
[   11.391344] bus: 'pci': add driver shpchp
[   11.394387] bus: 'pci': really_probe: probing driver piix4_smbus with device 0000:00:14.0
[   11.396472] ACPI Warning: SystemIO range 0x0000000000000b00-0x0000000000000b07 conflicts with OpRegion 0x0000000000000b00-0x0000000000000b0f (\_SB_.PCI0.SMB_.SMB0) (20141107/utaddress-258)
[   11.398637] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   11.400799] piix4_smbus: probe of 0000:00:14.0 rejects match -19
[   11.403412] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   11.408849] device: 'timer': device_add
[   11.438592] bus: 'pci': add driver snd_hda_intel
...
Linux version 3.19.0-rc5-gec6f34e


Same thing even with the earliest kernel that I could find in logs, 3.18.0-rc2-gcac7f24 :

Oct 27 12:05:23 manji kernel: ACPI Warning: SystemIO range 0x0000000000000b00-0x0000000000000b07 conflicts wit
h OpRegion 0x0000000000000b00-0x0000000000000b0f (\_SB_.PCI0.SMB_.SMB0) (20140926/utaddress-258)
Comment 6 Rob 2015-01-24 22:35:26 UTC
I'm seeing something similar on a E6440 BIOS A05 on Ubuntu 14.04 during boot:


[   16.298893] ACPI Warning: 0x0000000000001828-0x000000000000182f SystemIO conflicts with Region \PMIO 1 (20131115/utaddress-251)
[   16.298899] ACPI Warning: 0x0000000000001828-0x000000000000182f SystemIO conflicts with Region \_SB_.PCI0.EHC2.E1PM 2 (20131115/utaddress-251)
[   16.298902] ACPI Warning: 0x0000000000001828-0x000000000000182f SystemIO conflicts with Region \_SB_.PCI0.EHC1.E1PM 3 (20131115/utaddress-251)
[   16.298907] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   16.298975] ACPI Warning: 0x0000000000001c30-0x0000000000001c3f SystemIO conflicts with Region \GPRL 1 (20131115/utaddress-251)
[   16.298978] ACPI Warning: 0x0000000000001c30-0x0000000000001c3f SystemIO conflicts with Region \GPR_ 2 (20131115/utaddress-251)
[   16.298981] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   16.298982] ACPI Warning: 0x0000000000001c00-0x0000000000001c2f SystemIO conflicts with Region \GPRL 1 (20131115/utaddress-251)
[   16.298985] ACPI Warning: 0x0000000000001c00-0x0000000000001c2f SystemIO conflicts with Region \GPR_ 2 (20131115/utaddress-251)
[   16.298988] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   16.298989] lpc_ich: Resource conflict(s) found affecting gpio_ich
Comment 7 Zhang Rui 2015-02-15 09:21:47 UTC
This error message is printed if the ACPI Operation Region conflicts with any native driver.
It just provides a clue if something bad really happens. So if there is no malfunction, you can ignore this message.

Bug closed as I don't see a real problem in this bug report.
Please feel free to reopen it if there is indeed something not working on your systems.
Comment 8 Zhang Rui 2015-02-15 09:23:22 UTC
For the MCE issue, I think you can open a new bug report and assign to the proper category instead of ACPI.
Comment 9 Upul Doluweera 2015-10-11 02:22:21 UTC
I am getting the same for 4.2.2-1-ARCH system.

[    2.544904] ACPI: Thermal Zone [TZ01] (30 C)
[    2.554493] ACPI Warning: SystemIO range 0x000000000000F040-0x000000000000F05F conflicts with OpRegion 0x000000000000F040-0x000000000000F04F (\SMB0) (20150619/utaddress-254)
[    2.554510] ACPI Warning: SystemIO range 0x000000000000F040-0x000000000000F05F conflicts with OpRegion 0x000000000000F040-0x000000000000F04F (\_SB_.PCI0.SBUS.SMBI) (20150619/utaddress-254)
[    2.554521] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Comment 10 Konstantin Kharlamov 2016-11-24 08:35:33 UTC
@Zhang Rui, for completeness, please, could you either elaborate a bit, or — even better — point out a link to docs/discussion/posts/anything about why is this happen? Like, why would the region conflict, is it a problem with BIOS or driver, why the driver takes away that region instead of choosing non-conflicting one, and why most of the time is it safe anyway…?
Comment 11 Zhang Rui 2016-11-25 01:50:14 UTC
(In reply to Constantine from comment #10)
> @Zhang Rui, for completeness, please, could you either elaborate a bit, or —
> even better — point out a link to docs/discussion/posts/anything about why
> is this happen?

you can check the description of acpi_enforce_resources boot option in Documentation/kernel-parameters.txt

> Like, why would the region conflict,

simple, both ACPI and native driver wants to access the same piece of resource.

> is it a problem with
> BIOS or driver,

Depends. We need to check if the conflict case by case and see if ACPI/driver should access it or not.

> why the driver takes away that region instead of choosing
> non-conflicting one, and why most of the time is it safe anyway…?

In most of cases, although both of them require the same piece of resource, only one of them is the actual resource consumer.