Summary: | sys-kernel/gentoo-sources-2.6.31/2.6.32 conflict ACPI drivers with ACPI region | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Oschtan <dawnstyle> |
Component: | [OLD] Unspecified | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | axiator |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
URL: | https://bugs.launchpad.net/ubuntu/+source/linux/+bug/440780 | ||
Whiteboard: | linux-2.6.31,linux-2.6.32 | ||
Package list: | Runtime testing required: | --- |
Description
Oschtan
2009-12-25 08:05:35 UTC
Is there a specific problem you are experiencing? Can you find out if there is a bios upgrade for your mb. All references I see report to use the acpi_enforce_resources=lax workaround that you claim is not working for you. Procedure "Bios upgrade" does not lead to solving the problem. Similar problem exists with the driver W83627EHF... Chipset Nvidia. What is the symptom that is being experienced besides the error message? me too , can't use lm_sensors(3.1.2) (gentoo-sources-2.6.32) # modprobe w83627ehf FATAL: Error inserting w83627ehf (/lib/modules/2.6.32-gentoovvgloo/kernel/drivers/hwmon/w83627ehf.ko): Device or resource busy -----dmesg--------- w83627ehf: Found W83627DHG-P chip at 0x228 ACPI: I/O resource w83627ehf [0x22d-0x22e] conflicts with ACPI region SEN1 [0x22d-0x22e] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver --------------------- (In reply to comment #6) > me too , can't use lm_sensors(3.1.2) (gentoo-sources-2.6.32) > > # modprobe w83627ehf > FATAL: Error inserting w83627ehf > (/lib/modules/2.6.32-gentoovvgloo/kernel/drivers/hwmon/w83627ehf.ko): Device or > resource busy > > -----dmesg--------- Does this kernel parameter work for you? acpi_enforce_resources=lax > w83627ehf: Found W83627DHG-P chip at 0x228 > ACPI: I/O resource w83627ehf [0x22d-0x22e] conflicts with ACPI region SEN1 > [0x22d-0x22e] > ACPI: If an ACPI driver is available for this device, you should use it instead > of the native driver > --------------------- > (In reply to comment #7)thank you for your reply Without acpi_enforce_resources=lax ===dmesg==== i2c /dev entries driver i801_smbus 0000:00:1f.3: PCI INT B -> GSI 19 (level, low) -> IRQ 19 w83627ehf: Found W83627DHG chip at 0x290 ACPI: I/O resource w83627ehf [0x295-0x296] conflicts with ACPI region HWRE [0x290-0x299] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver With acpi_enforce_resources=lax ===dmesg===== i2c /dev entries driver i801_smbus 0000:00:1f.3: PCI INT B -> GSI 19 (level, low) -> IRQ 19 w83627ehf: Found W83627DHG chip at 0x290 ACPI: I/O resource w83627ehf [0x295-0x296] conflicts with ACPI region HWRE [0x290-0x299] ACPI: This conflict may cause random problems and system instability ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver hwmon-vid: Unknown VRM version of your x86 CPU sys-kernel/gentoo-sources-2.6.33 ... i2c /dev entries driver i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18 ACPI: I/O resource 0000:00:1f.3 [0x400-0x41f] conflicts with ACPI region SMRG [0x400-0x40f] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver ... w83627ehf: Found W83627DHG chip at 0x290 ACPI: I/O resource w83627ehf [0x295-0x296] conflicts with ACPI region HWRE [0x290-0x299] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver gentoo-sources-2.6.33 ==================== i2c /dev entries driver i2c i2c-0: nForce2 SMBus adapter at 0x600 ACPI: I/O resource nForce2_smbus [0x700-0x73f] conflicts with ACPI region SM00 [0x700-0x73f] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver nForce2_smbus 0000:00:01.1: Error probing SMB2. it87: Found IT8712F chip at 0x290, revision 8 it87: VID is disabled (pins used for GPIO) 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: If an ACPI driver is available for this device, you should use it instead of the native driver First of all, let me say that switching acpi_enforce_resources to "lax" is not recommended (you can read many stuff about this on the net.). Also, let me say that for those who did not switch acpi_enforce_resources to "lax", this is normal behavior. It basically says that your driver checked to see if it's direct I/O area is claimed by ACPI, it indeed was claimed, and it stopped loading. Now, if you actually switched acpi_enforce_resources to "lax", then you should be okay. You _will_ still be getting a warning message in your kernel logs, but your driver _should_ be working. If anyone is using "lax" acpi_enforce_resources and his driver is still not *working*, he should post here why he thinks it's not *working*. Thanks, George. I believe this can be closed now. acpi_enforce_resources=lax is not set ============================ i2c /dev entries driver i2c i2c-0: nForce2 SMBus adapter at 0x600 ACPI: I/O resource nForce2_smbus [0x700-0x73f] conflicts with ACPI region SM00 [0x700-0x73f] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver nForce2_smbus 0000:00:01.1: Error probing SMB2. it87: Found IT8712F chip at 0x290, revision 8 it87: VID is disabled (pins used for GPIO) 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: If an ACPI driver is available for this device, you should use it instead of the native driver |