Bug 15361
Summary: | nForce2_smbus conflicts with ACPI region SM00 | ||
---|---|---|---|
Product: | ACPI | Reporter: | argos66 |
Component: | Config-Other | Assignee: | ykzhao (yakui.zhao) |
Status: | CLOSED DOCUMENTED | ||
Severity: | low | CC: | lenb, rui.zhang, yakui.zhao |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.32 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: | dmesg |
Description
argos66
2010-02-20 09:11:35 UTC
Created attachment 25129 [details]
dmesg
Hi, The corresponding I/O port(0x1C40-0x1c45) will be accessed by ACPI. If we still load the nforce2_smbus driver, they will access the same I/O port. As there is no synchronization between smbus driver and ACPI, maybe the system can't work well. So when the resource conflict is detected, we had better not load the corresponding nforce2_smbus driver. If you think that nforce2_smbus driver is very important, you can add the boot option of "acpi_enforce_resources=lax". Of course the warning message still exists. But it can be loaded. Thanks. The warning message does the right thing. It only reminds that the nforce2_smbus driver had better not be loaded as there exists the potential conflict between ACPI and SMbus driver. thanks. is there anything bad together with this message? for example, are there any devices that fail to work in 2,6,32, compared with 2.6.30/31? Thanks for your responses. This problem exists in 2.6.30 and 2.6.31. This message don't block the system or other, but it's for have a cleanup boot log. Thanks. |