lpc_ich: Resource conflict(s) found affecting iTCO_wdt

Bug #1027370 reported by dino99
108
This bug affects 23 people
Affects Status Importance Assigned to Milestone
Linux
Fix Released
Medium
linux (Ubuntu)
Won't Fix
Medium
Colin Ian King

Bug Description

Still get these ACPI conflicts:

ACPI Warning: 0x00000830-0x00000833 SystemIO conflicts with Region \SMIE 1 (20120320/utaddress-251)
ACPI Warning: 0x00000830-0x00000833 SystemIO conflicts with Region \_SB_.PCI0.SBRG.SMIE 2 (20120320/utaddress-251)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

lpc_ich: Resource conflict(s) found affecting iTCO_wdt

ACPI Warning: 0x00000480-0x000004bf SystemIO conflicts with Region \_SB_.PCI0.SBRG.GPIO 1 (20120320/utaddress-251)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

lpc_ich: Resource conflict(s) found affecting gpio_ich

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-5-generic 3.5.0-5.5
ProcVersionSignature: Ubuntu 3.5.0-5.5-generic 3.5.0-rc7
Uname: Linux 3.5.0-5-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.4-0ubuntu4
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: oem 2725 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Sat Jul 21 10:39:42 2012
HibernationDevice: RESUME=UUID=f4216733-a2b7-4818-9852-9bb41d54d87c
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 eth1 no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-5-generic root=UUID=00c5de83-479c-4ab0-9b54-9af0a727175e ro rootdelay=5 quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-5-generic N/A
 linux-backports-modules-3.5.0-5-generic N/A
 linux-firmware 1.85
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3002
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5W DH Deluxe
dmi.product.version: System Version
dmi.sys.vendor: ASUSTEK COMPUTER INC

Revision history for this message
dino99 (9d9) wrote :
Revision history for this message
dino99 (9d9) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

Get the same issue with the latest kernel 3.5.0-6

Revision history for this message
dino99 (9d9) wrote :

dmesg3.5.0-6

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.5kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc7-quantal/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
dino99 (9d9) wrote :

The latest kernel show the same errors:
Linux version 3.6.0-999-generic (apw@gomeisa) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201208050405 SMP Sun Aug 5 08:12:48 UTC 2012

ACPI Warning: 0x00000830-0x00000833 SystemIO conflicts with Region \SMIE 1 (20120711/utaddress-251)
ACPI Warning: 0x00000830-0x00000833 SystemIO conflicts with Region \_SB_.PCI0.SBRG.SMIE 2 (20120711/utaddress-251)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
 lpc_ich: Resource conflict(s) found affecting iTCO_wdt
ACPI Warning: 0x00000480-0x000004bf SystemIO conflicts with Region \_SB_.PCI0.SBRG.GPIO 1 (20120711/utaddress-251)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
lpc_ich: Resource conflict(s) found affecting gpio_ich

tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
status: Confirmed → Triaged
Changed in linux:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
dino99 (9d9) wrote :

3.6 rc2 kernel output:

w83627ehf: Found W83627DHG chip at 0x290
ACPI Warning: 0x00000295-0x00000296 SystemIO conflicts with Region \_SB_.PCI0.SBRG.SIOR.HWRE 1 (20120711/utaddress-251)

ACPI Warning: 0x00000830-0x00000833 SystemIO conflicts with Region \SMIE 1 (20120711/utaddress-251)
ACPI Warning: 0x00000830-0x00000833 SystemIO conflicts with Region \_SB_.PCI0.SBRG.SMIE 2 (20120711/utaddress-251)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
lpc_ich: Resource conflict(s) found affecting iTCO_wdt

ACPI Warning: 0x00000480-0x000004bf SystemIO conflicts with Region \_SB_.PCI0.SBRG.GPIO 1 (20120711/utaddress-251)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
lpc_ich: Resource conflict(s) found affecting gpio_ich

Revision history for this message
dino99 (9d9) wrote :

Have installed the 3.6 rc5 kernel and still get the same errors reported here.

Revision history for this message
dino99 (9d9) wrote :

3.6-rc6 output:

ACPI Warning: 0x00000480-0x000004bf SystemIO conflicts with Region \_SB_.PCI0.SBRG.GPIO 1 (20120711/utaddress-251)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
lpc_ich: Resource conflict(s) found affecting gpio_ich

Revision history for this message
dino99 (9d9) wrote :

final 3.6 release output:

ACPI: Invalid Power Resource to register!

ACPI Warning: 0x00000295-0x00000296 SystemIO conflicts with Region \_SB_.PCI0.SBRG.SIOR.HWRE 1 (20120711/utaddress-251)

ACPI Warning: 0x00000480-0x000004bf SystemIO conflicts with Region \_SB_.PCI0.SBRG.GPIO 1 (20120711/utaddress-251)
lpc_ich: Resource conflict(s) found affecting gpio_ich

Revision history for this message
dino99 (9d9) wrote :

module-init-tools.log:

FATAL: Error inserting w83627ehf (/lib/modules/3.6.0-030600-generic/kernel/drivers/hwmon/w83627ehf.ko): Device or resource busy

Changed in linux:
status: Confirmed → Fix Released
Revision history for this message
dino99 (9d9) wrote :

Got fixed upstream, hopes to get that commit backported to 3.5 kernel and up.

A patch referencing this bug report has been merged in Linux v3.7-rc1:

commit 092369efbd6ef6b4a215741ce9f65446bf45beff
Author: Feng Tang <email address hidden>
Date: Thu Aug 16 15:50:10 2012 +0800

    mfd: lpc_ich: Fix a 3.5 kernel regression for iTCO_wdt driver

Revision history for this message
dino99 (9d9) wrote :

3.7-rc2 feedback:

well that issue is still not yet fixed, get this logged:

ACPI: Invalid Power Resource to register!
ACPI Warning: 0x000004b0-0x000004bf SystemIO conflicts with Region \_SB_.PCI0.SBRG.GPIO 1 (20120913/utaddress-251)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
ACPI Warning: 0x00000480-0x000004af SystemIO conflicts with Region \_SB_.PCI0.SBRG.GPIO 1 (20120913/utaddress-251)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
lpc_ich: Resource conflict(s) found affecting gpio_ich

Revision history for this message
n0PxN0p (n0pxn0p) wrote :

3.5.0-24-generic #37-Ubuntu SMP Thu Feb 7 01:50:30 UTC 2013 x86_64

[ 23.021632] ACPI Warning: 0x0000000000000460-0x000000000000047f SystemIO conflicts with Region \PMIO 1 (20120320/utaddress-251)
[ 23.021640] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 23.021642] lpc_ich: Resource conflict(s) found affecting iTCO_wdt
[ 23.021646] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20120320/utaddress-251)
[ 23.021650] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 23.021654] ACPI Warning: 0x0000000000000500-0x000000000000057f SystemIO conflicts with Region \GPIO 1 (20120320/utaddress-251)
[ 23.021658] ACPI Warning: 0x0000000000000500-0x000000000000057f SystemIO conflicts with Region \_SB_.PCI0.PEG0.PEGP.GPIO 2 (20120320/utaddress-251)
[ 23.021662] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 23.021664] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 23.024285] mei 0000:00:16.0: wd: failed to find the client

Revision history for this message
dino99 (9d9) wrote :

3.8.0-6 i386 also affected

 w83627ehf: Found W83627DHG chip at 0x290
ACPI Warning: 0x00000295-0x00000296 SystemIO conflicts with Region \_SB_.PCI0.SBRG.SIOR.HWRE 1 (20121018/utaddress-251)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
ACPI Warning: 0x000004b0-0x000004bf SystemIO conflicts with Region \_SB_.PCI0.SBRG.GPIO 1 (20121018/utaddress-251)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
ACPI Warning: 0x00000480-0x000004af SystemIO conflicts with Region \_SB_.PCI0.SBRG.GPIO 1 (20121018/utaddress-251)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
lpc_ich: Resource conflict(s) found affecting gpio_ich
EDAC MC: Ver: 3.0.0

Revision history for this message
Mehdi (mehdi-ti) wrote :

3.8.0-19-generic x86_64 ubuntu 13.04 also affected:

lp: driver loaded but no devices found
ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20121018/utaddress-251)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
ACPI Warning: 0x0000000000000540-0x000000000000054f SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
lpc_ich: Resource conflict(s) found affecting gpio_ich

Revision history for this message
Ivars Strazdiņš (ivars-strazdins) wrote :

Same for kernel version 3.8.0-22-generic x86_64 on ubuntu 13.04

[ 6.067190] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 6.067389] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20121018/utaddress-251)
[ 6.067394] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 6.067397] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251)
[ 6.067400] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 6.067402] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251)
[ 6.067405] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 6.067406] lpc_ich: Resource conflict(s) found affecting gpio_ich

Changed in linux (Ubuntu):
status: Triaged → In Progress
assignee: nobody → Colin King (colin-king)
Revision history for this message
Colin Ian King (colin-king) wrote :

Warning: "lpc_ich: Resource conflict(s) found affecting iTCO_wdt"

ACPI OpRegions are conflicting with the same I/O region used by the lpc_ich driver for the Intel TCO (Total Cost of Ownership) timer (iTCO_wdt, this is a watchdog timer that will reboot the machine after its second expiration).

According to Intel Controller Hub (ICH) specifications, the TCO watchdog has a 32 bytes I/O space resource. ACPI OpRegions in the DSDT frequently reserve this TCO I/O space because they require access to bit 9 (DMISCI_STS) of the TCO1_STS register of the TCO. I believe that this bit is not used and is never used by the lpc_ich TCO driver, so the risk of conflict is zero.

The warning occurs because ACPI has reserved this I/O region and the lpc_ich driver also wants to access the TCO registers but detects these are already reserved. However, I believe that there is no real conflict to worry about.

Revision history for this message
Colin Ian King (colin-king) wrote :

Warning: "lpc_ich: Resource conflict(s) found affecting gpio_ich"

This again is because ACPI OpRegions conflict with the same I/O region used by the lpc_ich driver, this time for the GPIO region. Again, I don't believe this is an issue to worry about.

Revision history for this message
Colin Ian King (colin-king) wrote :

I don't think this are bugs per-se. The lpc_ich driver uses these I/O regions that are already reserved by ACPI OpRegions and they seem to co-exist OK without any issues. The warnings are alarming, but can be ignored. There's nothing to fix.

Changed in linux (Ubuntu):
status: In Progress → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.