kernel 2.6.31 bug with it87 module? [SOLVED]

graysky · 2009-10-10 13:56:24

I've been using both the coretemp and it87 modules with Arch for a long time now. I just updated and pacman brought down/install the 2.6.31 kernel. When I rebooted into it, I got an error regarding the it87 module.

# modprobe it87
FATAL: Error inserting it87 (/lib/modules/2.6.31-ARCH/kernel/drivers/hwmon/it87.ko): Device or resource busy

It gives the same error if I force it (w/ the -f switch). This is required for reading the temp sensors on my board. Any thoughts on why it's roached w/ the new kernel? I'll hold off on a new flyspray task on this until some people have a chance to comment.

Thanks!

Last edited by graysky (2009-10-10 14:04:52)

graysky · 2009-10-10 14:04:32

Ack... should've googled this first, it's no bug. See, http://bugzilla.kernel.org/show_bug.cgi?id=13967

Basically, you need to add a new kernel line in your menu.lst to fix this behavior.

acpi_enforce_resources=lax

thefatprecious · 2009-10-10 15:31:19

I have the same issue and my asus_atk0110 module is loaded automatically. If I'm reading them correctly, according to the lm_sensors faq and some of the mailing lists that should be all that is necessary.

It's been reported that adding acpi_enforce_resources=lax can be potentially dangerous. I've read a few articles but can't narrow down exactly what are the potential consequences. Can anyone else clarify what they are?

This is the error from dmesg post boot:

it87: Found IT8712F chip at 0x290, revision 8
it87: in3 is VCC (+5V)
it87: in7 is VCCH (+5V Stand-By)
ACPI: I/O resource it87 [0x295-0x296] conflicts with ACPI region ECRE [0x290-0x2af]
ACPI: Device needs an ACPI driver

EDIT: In my instance it87 was no longer necessary for lm_sensors to work and read the temps as it is correctly handled by the asus driver. I left my above comment however in case someone else shared the concern about that parameter mentioned in the OP....

Last edited by thefatprecious (2009-10-10 15:48:41)

new2arch · 2009-10-10 19:50:17

thefatprecious wrote:

I have the same issue and my asus_atk0110 module is loaded automatically. If I'm reading them correctly, according to the lm_sensors faq and some of the mailing lists that should be all that is necessary.
It's been reported that adding acpi_enforce_resources=lax can be potentially dangerous. I've read a few articles but can't narrow down exactly what are the potential consequences. Can anyone else clarify what they are?
This is the error from dmesg post boot:
it87: Found IT8712F chip at 0x290, revision 8
it87: in3 is VCC (+5V)
it87: in7 is VCCH (+5V Stand-By)
ACPI: I/O resource it87 [0x295-0x296] conflicts with ACPI region ECRE [0x290-0x2af]
ACPI: Device needs an ACPI driver
EDIT: In my instance it87 was no longer necessary for lm_sensors to work and read the temps as it is correctly handled by the asus driver. I left my above comment however in case someone else shared the concern about that parameter mentioned in the OP....

I have the same "problem", ever since the recent kernel upgrade, the it87 module isn't loaded anymore.
Dmesg output:

dmesg | grep it87
it87: Found IT8718F chip at 0x290, revision 2
it87: in3 is VCC (+5V)
it87: in7 is VCCH (+5V Stand-By)
ACPI: I/O resource it87 [0x295-0x296] conflicts with ACPI region IP__ [0x295-0x296]

sensors give me this:

acpitz-virtual-0
Adapter: Virtual device
temp1: +40.0°C (crit = +75.0°C)

atk0110-acpi-0
Adapter: ACPI interface
Vcore Voltage: +1.02 V (min = +1.45 V, max = +1.75 V)
+3.3 Voltage: +3.23 V (min = +3.00 V, max = +3.60 V)
+5.0 Voltage: +4.76 V (min = +4.50 V, max = +5.50 V)
+12.0 Voltage: +12.16 V (min = +11.20 V, max = +13.20 V)
CPU FAN Speed: 842 RPM (min = 0 RPM)
CHASSIS FAN Speed: 532 RPM (min = 0 RPM)
CHASSIS2 FAN Speed: 0 RPM (min = 0 RPM)
CPU Temperature: +32.0°C (high = +90.0°C, crit = +125.0°C)
MB Temperature: +38.0°C (high = +70.0°C, crit = +125.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Core 0: +38.0°C (high = +74.0°C, crit = +100.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1: +44.0°C (high = +74.0°C, crit = +100.0°C)

I believe I get the correct values as I did with it87.

BlueSkyNis · 2009-10-12 18:55:06

I too have the same "problem", but I switched to asus_atk0110 driver for sensors and it works. For now I have no need for it87.

it87: Found IT8720F chip at 0x290, revision 2
it87: in3 is VCC (+5V)
it87: in7 is VCCH (+5V Stand-By)
ACPI: I/O resource it87 [0x295-0x296] conflicts with ACPI region ECRE [0x290-0x2af]
it87: Found IT8720F chip at 0x290, revision 2
it87: in3 is VCC (+5V)
it87: in7 is VCCH (+5V Stand-By)
ACPI: I/O resource it87 [0x295-0x296] conflicts with ACPI region ECRE [0x290-0x2af]

killajoe · 2009-10-27 07:19:05

Same for me on a Acer/MSI MCP73 Board (Nforce 630i/Geforce 7100)

Blacklist it87 seems not to do anything with and without i got the same output:

coretemp coretemp.0: Using relative temperature scale!
coretemp coretemp.1: Using relative temperature scale!
it87: Found IT8718F chip at 0xa10, revision 4
it87: in3 is VCC (+5V)
it87: in7 is VCCH (+5V Stand-By)
ACPI: I/O resource it87 [0xa15-0xa16] conflicts with ACPI region HHHD [0xa15-0xa16]
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

Any idea of where i can find what other driver i can use?

sensors after put the hack to Grub Kernelline:

killajoe:~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:       +25.0°C  (crit = +125.0°C)                  

coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +45.0°C  (high = +86.0°C, crit = +100.0°C)  

coretemp-isa-0001
Adapter: ISA adapter
Core 1:      +45.0°C  (high = +86.0°C, crit = +100.0°C)  

it8718-isa-0a10
Adapter: ISA adapter
in0:         +1.17 V  (min =  +0.00 V, max =  +4.08 V)   
in1:         +1.34 V  (min =  +0.00 V, max =  +4.08 V)   
in2:         +1.87 V  (min =  +0.00 V, max =  +4.08 V)   
in3:         +2.98 V  (min =  +0.00 V, max =  +4.08 V)   
in4:         +2.96 V  (min =  +0.00 V, max =  +4.08 V)   
in5:         +3.34 V  (min =  +0.00 V, max =  +4.08 V)   
in6:         +0.10 V  (min =  +0.00 V, max =  +4.08 V)   
in7:         +2.98 V  (min =  +0.00 V, max =  +4.08 V)   
Vbat:        +3.15 V
fan1:       1142 RPM  (min =    0 RPM)
fan2:          0 RPM  (min =    0 RPM)
fan3:          0 RPM  (min =    0 RPM)
temp1:       +28.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermal diode
temp2:       +41.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp3:       -49.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = disabled
cpu0_vid:   +0.000 V

Thats HOT:

temp1: +28.0°C (low = +127.0°C, high = +127.0°C) sensor = thermal diode
temp2: +41.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
temp3: -49.0°C (low = +127.0°C, high = +127.0°C) sensor = disabled

Last edited by killajoe (2009-10-27 07:30:54)

luuuciano · 2010-09-17 00:14:53

from here: http://www.lm-sensors.org/wiki/FAQ/Chap … rnel2.6.31

With previous kernels hwmon drivers used to drive IO ranges which were potentially used by the ACPI code in your BIOS (which is active not only during but also after boot), we now explicitly check for this and if the ACPI code claims the IO-ports used by the hwmon chip, we no longer allow the hwmon driver to load.
Banging IO-ports of a chip from 2 different drivers, the Linux hwmon driver and the ACPI code is a really bad idea and can cause all sort of issues (including things like changing CPU / RAM voltage or clock speed). So the old behaviour was a really bad idea.
So even though this change in behaviour makes some people unhappy as to old behaviour happened to work without problems in their case (by sheer luck really), this change is really for the best!

I have the same issue, no more temp, and it87 not recognized... do not understand wich is the best way to solve it

killajoe · 2010-09-17 00:24:59

Better open a new issue.
This one is old and marked as solved...

And nopaste what gives you:

dmesg | grep it87

sensors

lsmod | grep it87

...

Last edited by killajoe (2010-09-17 00:32:11)

luuuciano · 2010-09-17 00:58:01

well... I have found new information to this issue, that is why I post it here, so thefatprecious, and others that find the thread later, see it
and because that "solved" maybe is not the best one

the dmesg cat is pretty much the same as thefatprecious one

it87: Found IT8712F chip at 0x290, revision 8
it87: VID is disabled (pins used for GPIO)
it87: in7 is VCCH (+5V Stand-By)
ACPI: resource it87 [io 0x0295-0x0296] conflicts with ACPI region ECRE [??? 0x00000290-0x000002af flags 0x45]
it87: Found IT8712F chip at 0x290, revision 8
it87: VID is disabled (pins used for GPIO)
it87: in7 is VCCH (+5V Stand-By)
ACPI: resource it87 [io 0x0295-0x0296] conflicts with ACPI region ECRE [??? 0x00000290-0x000002af flags 0x45]

no lsmod information, as the module is never loaded at bootup (it shows an error as stated by graysky)
FATAL: Error inserting it87 (/lib/modules/2.6.35-ARCH/kernel/drivers/hwmon/it87.ko): Device or resource busy

edit: but, nevermid... I can sleep at night with this working or not... that is another reason because I posted it several months later 2.6.31 was released

Last edited by luuuciano (2010-09-17 01:03:04)

ummakynes · 2010-12-20 08:01:51

Has anyone found a fix or workaround for this? I have grub2, would the acpi thing in menu.lst work?

Arch Linux

#1 2009-10-10 13:56:24

kernel 2.6.31 bug with it87 module? [SOLVED]

#2 2009-10-10 14:04:32

Re: kernel 2.6.31 bug with it87 module? [SOLVED]

#3 2009-10-10 15:31:19

Re: kernel 2.6.31 bug with it87 module? [SOLVED]

#4 2009-10-10 19:50:17

Re: kernel 2.6.31 bug with it87 module? [SOLVED]

#5 2009-10-12 18:55:06

Re: kernel 2.6.31 bug with it87 module? [SOLVED]

#6 2009-10-27 07:19:05

Re: kernel 2.6.31 bug with it87 module? [SOLVED]

#7 2010-09-17 00:14:53

Re: kernel 2.6.31 bug with it87 module? [SOLVED]

#8 2010-09-17 00:24:59

Re: kernel 2.6.31 bug with it87 module? [SOLVED]

#9 2010-09-17 00:58:01

Re: kernel 2.6.31 bug with it87 module? [SOLVED]

#10 2010-12-20 08:01:51

Re: kernel 2.6.31 bug with it87 module? [SOLVED]

Board footer