Bug 43055 - FATAL: Error inserting w83627ehf (/lib/modules/3.4.0-999-generic-pae/kernel/drivers/hwmon/w83627ehf.ko): Device or resource busy
Summary: FATAL: Error inserting w83627ehf (/lib/modules/3.4.0-999-generic-pae/kernel/d...
Status: RESOLVED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: Hardware Monitoring (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Jean Delvare
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-06 08:09 UTC by dino99
Modified: 2012-04-06 08:24 UTC (History)
0 users

See Also:
Kernel Version: 3.4
Tree: Mainline
Regression: No


Attachments
lspci -vvnn (34.04 KB, text/plain)
2012-04-06 08:09 UTC, dino99
Details

Description dino99 2012-04-06 08:09:31 UTC
Created attachment 72828 [details]
lspci -vvnn

Ubuntu Precise i386

always had this issue, and it still exist with 3.4 kernel

From kern.log:

 w83627ehf: Found W83627DHG chip at 0x290
 ACPI Warning: 0x00000295-0x00000296 SystemIO conflicts with Region \_SB_.PCI0.SBRG.SIOR.HWRE 1 (20120320/utaddress-251)
 ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

Also found this logged into /var/log/upstart/module-init-tools.log

Already reported on Launchpad:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969941
Comment 1 Jean Delvare 2012-04-06 08:24:56 UTC
This is a BIOS issue, nothing we can do. Your BIOS requested the I/O ports of your monitoring device for its own use, the Linux kernel is locked out.

This is all documented in the lm-sensors FAQ:
http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31

Note You need to log in before you can comment on or make changes to this bug.