linux-next: ACPI I/O resource conflicts warning
Hi all ,
I've noticed on linux-next from today the following ACPI warning:
...
[4294023.308622] ACPI: PCI Interrupt 0000:00:1f.3[C] -> GSI 18 (level, low) -> IRQ 18 [4294023.308622] ACPI: I/O resource [0x400-0x41f] conflicts with ACPI region SMRG [0x400-0x40f] [4294023.316478] ACPI: Device needs an ACPI driver
...
dsdt.dsl from my motherboard can be found there:
http://frugalware.org/~crazy/ASUS_P5E-VM_DO/dsdt.dsl
full dmesg:
http://frugalware.org/~crazy/dmesg/DMAR/dmesg
Please let me know if you need more infos.
Best Regards,
Gabriel C
Quoted 9 lines · Gabriel C
Hi all ,
I've noticed on linux-next from today the following ACPI warning:
...
[4294023.308622] ACPI: PCI Interrupt 0000:00:1f.3[C] -> GSI 18 (level, low) -> IRQ 18 [4294023.308622] ACPI: I/O resource [0x400-0x41f] conflicts with ACPI region SMRG [0x400-0x40f] [4294023.316478] ACPI: Device needs an ACPI driver
You use libsensors and the sensor you use is also declared and possibly used via ACPI.
Quoted 9 lines
dsdt.dsl from my motherboard can be found there:
http://frugalware.org/~crazy/ASUS_P5E-VM_DO/dsdt.dsl
full dmesg:
http://frugalware.org/~crazy/dmesg/DMAR/dmesg
Please let me know if you need more infos.
Maybe you could open a bug report on bugzilla.kernel.org and post acpidump and dmi output (not only dsdt) there. Then we could collect affected BIOSes at one central place for further evaluation and discussion.
Thanks,
Thomas
Quoted 5 lines · Thomas Renninger
Quoted 4 lines · Gabriel C
Hi all ,
I've noticed on linux-next from today the following ACPI warning:
Quoted 8 lines
Quoted 5 lines
...
[4294023.308622] ACPI: PCI Interrupt 0000:00:1f.3[C] -> GSI 18 (level, low) -> IRQ 18 [4294023.308622] ACPI: I/O resource [0x400-0x41f] conflicts with ACPI region SMRG [0x400-0x40f] [4294023.316478] ACPI: Device needs an ACPI driverYou use libsensors and the sensor you use is also declared and possibly used via ACPI.
Not really , lsmsensors was not running and no modules loaded for my sensors but yeah when I start it another warning pops up ( this one I've reported to lm-sensors mailing list )
w83627ehf: Found W83627DHG chip at 0x290
ACPI: I/O resource w83627ehf [0x295-0x296] conflicts with ACPI region HWRE [0x290-0x299]
ACPI: Device needs an ACPI driver
Quoted 7 lines
Quoted 7 lines
dsdt.dsl from my motherboard can be found there:
http://frugalware.org/~crazy/ASUS_P5E-VM_DO/dsdt.dsl
full dmesg:
Quoted 8 lines
Quoted 3 lines
http://frugalware.org/~crazy/dmesg/DMAR/dmesg
Please let me know if you need more infos.
Maybe you could open a bug report on bugzilla.kernel.org and post acpidump and dmi output (not only dsdt) there. Then we could collect affected BIOSes at one central place for further evaluation and discussion.
Sure I will open an task about soon.
Quoted 4 lines
Thanks,
Thomas
Gabriel
Quoted 12 lines · Gabriel C
Quoted 11 lines · Thomas Renninger
Quoted 9 lines · Gabriel C
Hi all ,
I've noticed on linux-next from today the following ACPI warning:
...
[4294023.308622] ACPI: PCI Interrupt 0000:00:1f.3[C] -> GSI 18 (level, low) -> IRQ 18 [4294023.308622] ACPI: I/O resource [0x400-0x41f] conflicts with ACPI region SMRG [0x400-0x40f] [4294023.316478] ACPI: Device needs an ACPI driver
Quoted 5 lines
Quoted 2 lines
You use libsensors and the sensor you use is also declared and possibly used via ACPI.
Not really , lsmsensors was not running and no modules loaded for my sensors but yeah when I start it another warning pops up ( this one I've reported to lm-sensors mailing list )
Could be your SMBus controller then, we have these checks in both hwmon drivers and i2c bus drivers... Check what appears at 0x400 in /proc/iports.
Quoted 13 lines
w83627ehf: Found W83627DHG chip at
0x290
ACPI: I/O resource w83627ehf [0x295-0x296] conflicts with ACPI region HWRE [0x290-0x299]
ACPI: Device needs an ACPI driverQuoted 9 lines
Quoted 9 lines
dsdt.dsl from my motherboard can be found there:
http://frugalware.org/~crazy/ASUS_P5E-VM_DO/dsdt.dsl
full dmesg:
Quoted 8 lines
Quoted 6 lines
Quoted 1 line
Please let me know if you need more infos.
Maybe you could open a bug report on bugzilla.kernel.org and post acpidump and dmi output (not only dsdt) there. Then we could collect affected BIOSes at one central place for further evaluation and discussion.
Sure I will open an task about soon.
When you do, please add me to Cc, thanks.
Signature · 1 line
Jean Delvare
Quoted 12 lines · Jean Delvare
Quoted 11 lines · Gabriel C
Quoted 10 lines · Thomas Renninger
Quoted 9 lines · Gabriel C
Hi all ,
I've noticed on linux-next from today the following ACPI warning:
...
[4294023.308622] ACPI: PCI Interrupt 0000:00:1f.3[C] -> GSI 18 (level, low) -> IRQ 18 [4294023.308622] ACPI: I/O resource [0x400-0x41f] conflicts with ACPI region SMRG [0x400-0x40f] [4294023.316478] ACPI: Device needs an ACPI driver
Quoted 8 lines
Quoted 4 lines
Quoted 2 lines
You use libsensors and the sensor you use is also declared and possibly used via ACPI.
Not really , lsmsensors was not running and no modules loaded for my sensors but yeah when I start it another warning pops up ( this one I've reported to lm-sensors mailing list )
Could be your SMBus controller then, we have these checks in both hwmon drivers and i2c bus drivers... Check what appears at
0x400in/proc/iports.
Ahh, you are right.
0400-041f : 0000:00:1f.3
0400-041f : i801_smbus
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02)
Quoted 13 lines
Quoted 13 lines
w83627ehf: Found W83627DHG chip at
0x290
ACPI: I/O resource w83627ehf [0x295-0x296] conflicts with ACPI region HWRE [0x290-0x299]
ACPI: Device needs an ACPI driverQuoted 8 lines
Quoted 8 lines
dsdt.dsl from my motherboard can be found there:
http://frugalware.org/~crazy/ASUS_P5E-VM_DO/dsdt.dsl
full dmesg:
Quoted 9 lines
Quoted 6 lines
Quoted 5 lines
Quoted 1 line
Please let me know if you need more infos.
Maybe you could open a bug report on bugzilla.kernel.org and post acpidump and dmi output (not only dsdt) there. Then we could collect affected BIOSes at one central place for further evaluation and discussion.
Sure I will open an task about soon.
When you do, please add me to Cc, thanks.
Sure I will