Description of problem: it87 module loading fails, prevents sensors from being available on my machine. Version-Release number of selected component (if applicable): kernel-2.6.29.1-102.fc11.x86_64 How reproducible: Every time Steps to Reproduce: 1. modprobe it87 Actual results: FATAL: Error inserting it87 (/lib/modules/2.6.29.1-102.fc11.x86_64/kernel/drivers/hwmon/it87.ko): Device or resource busy Sensors not available Expected results: Module to load and CPU/MB temp etc sensors available. Additional info: From dmesg: it87: Found IT8712F chip at 0x290, revision 6 ACPI: I/O resource it87 [0x295-0x296] conflicts with ACPI region IP__ [0x295-0x296] ACPI: Device needs an ACPI driver
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Same issue here dmesg ..... 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] ACPI: Device needs an ACPI driver ..... modprobe it87 WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. FATAL: Error inserting it87 (/lib/modules/2.6.29.4-167.fc11.x86_64/kernel/drivers/hwmon/it87.ko): Device or resource busy uname -a Linux mn4 2.6.29.4-167.fc11.x86_64 #1 SMP Wed May 27 17:27:08 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
This is apparently an intentional error - it prevents it87 from using the same I2C bus as the acpi code. Two sets of code accessing the same bus is dangerous, I guess what is really needed is a common access point and a arbitrator. Having said that both machines I use this on have been fine with the clash for 4-5 years and no obvious problems before this check was added, and now I've disabled it they've been fine again for the last 6 weeks or so. You can disable this check by passing acpi_enforce_resources=lax on the kernel command line in grub, which solves the issue for me. (But be aware of potential undesired but unspecified consequences.)
I would much prefer kernel stability over some marginally useful functionality.
Another 'me too'. I happened to notice this when 'fancontrol' stopped working after upgrading from F11 to F12 (i686). FWIW, I've got an ASUS M2N-SLI DELUXE mobo.
Still same problem in F13 alpha.
same problem here my mobo is DFI nForce4 ultra-d, diagnostic chip it8712F [root@amd64 ~]# modprobe -v it87 insmod /lib/modules/2.6.33.4-95.fc13.x86_64/kernel/drivers/hwmon/it87.ko FATAL: Error inserting it87 (/lib/modules/2.6.33.4-95.fc13.x86_64/kernel/drivers/hwmon/it87.ko): Device or resource busy [root@amd64 ~]# lsmod | grep i2c i2c_nforce2 6566 0 i2c_algo_bit 4781 1 radeon i2c_core 24507 5 i2c_nforce2,radeon,drm_kms_helper,drm,i2c_algo_bit --- from boot.log Starting lm_sensors: loading module it87 [60G[[0;32m OK [0;39m] ... [root@amd64 ~]# uname -a Linux amd64 2.6.33.4-95.fc13.x86_64 #1 SMP Thu May 13 05:16:23 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
We can do much with that problem (however there is "dangerous" option to allow use sensors on your boards, see http://hansdegoede.livejournal.com/7932.html)
(In reply to comment #8) > We can We can not ... of course.