* resource piix4_smbus conflicts with ACPI region SMRG @ 2010-05-31 22:12 Richard Tillmore 2010-05-31 23:42 ` Robert Hancock 0 siblings, 1 reply; 6+ messages in thread From: Richard Tillmore @ 2010-05-31 22:12 UTC (permalink / raw) To: linux-kernel Hi, I was running 2.6.30 until I had time to update. Being a long weekend I upgraded to 2.6.34-rc6 and noticed a few new messages in dmesg. I then installed 2.6.34 and the messages remain. PCI: Ignoring host bridge windows from ACPI; if necessary, use "pci=use_crs" and report a bug ACPI: PCI Root Bridge [PCI0] (0000:00) ACPI: resource piix4_smbus [io 0x0440-0x0447] conflicts with ACPI region SMRG [??? 0x00000440-0x0000044f flags 0x47] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver The system is a Tyan Tiger S1832 motherboard with a P3 850Mhz processor running the latest bios. Everything appears to work properly so I am unsure what the messages mean beyond the obvious. I did a little research and was wondering if this is related to the no bootmem patches. I have: CONFIG_NO_BOOTMEM=y in my .config I have the full dmesgs from 2.6.30, 2.6.34-rc6 and 2.6.34 if you need to see them. I can also post my config if requested. Thanks, Rich ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: resource piix4_smbus conflicts with ACPI region SMRG 2010-05-31 22:12 resource piix4_smbus conflicts with ACPI region SMRG Richard Tillmore @ 2010-05-31 23:42 ` Robert Hancock 2010-06-01 2:36 ` Richard Tillmore 0 siblings, 1 reply; 6+ messages in thread From: Robert Hancock @ 2010-05-31 23:42 UTC (permalink / raw) To: Richard Tillmore; +Cc: linux-kernel On 05/31/2010 04:12 PM, Richard Tillmore wrote: > Hi, > > I was running 2.6.30 until I had time to update. Being a long weekend > I upgraded to 2.6.34-rc6 and noticed a few new messages in dmesg. I > then installed 2.6.34 and the messages remain. > > PCI: Ignoring host bridge windows from ACPI; if necessary, use > "pci=use_crs" and report a bug > ACPI: PCI Root Bridge [PCI0] (0000:00) This is just an informational message. > > ACPI: resource piix4_smbus [io 0x0440-0x0447] conflicts with ACPI > region SMRG [??? 0x00000440-0x0000044f flags 0x47] > ACPI: If an ACPI driver is available for this device, you should use > it instead of the native driver > > The system is a Tyan Tiger S1832 motherboard with a P3 850Mhz > processor running the latest bios. Everything appears to work > properly so I am unsure what the messages mean beyond the obvious. I > did a little research and was wondering if this is related to the no > bootmem patches. I have: Unless you need to use anything on SMBus (hardware sensors, essentially) you don't have to worry about that one. It means that the kernel has detected that the BIOS may potentially access the SMBus controller which may conflict with usage of the controller from within the OS. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: resource piix4_smbus conflicts with ACPI region SMRG 2010-05-31 23:42 ` Robert Hancock @ 2010-06-01 2:36 ` Richard Tillmore 2010-06-01 3:13 ` Robert Hancock 0 siblings, 1 reply; 6+ messages in thread From: Richard Tillmore @ 2010-06-01 2:36 UTC (permalink / raw) To: Robert Hancock; +Cc: linux-kernel On Mon, May 31, 2010 at 6:42 PM, Robert Hancock wrote: > On 05/31/2010 04:12 PM, Richard wrote: >> >> I upgraded to 2.6.34-rc6 and noticed a few new messages in dmesg. I >> then installed 2.6.34 and the messages remain. >> >> PCI: Ignoring host bridge windows from ACPI; if necessary, use >> "pci=use_crs" and report a bug >> ACPI: PCI Root Bridge [PCI0] (0000:00) > > This is just an informational message. > >> >> ACPI: resource piix4_smbus [io 0x0440-0x0447] conflicts with ACPI >> region SMRG [??? 0x00000440-0x0000044f flags 0x47] >> ACPI: If an ACPI driver is available for this device, you should use >> it instead of the native driver >> >> The system is a Tyan Tiger S1832 motherboard with a P3 850Mhz >> processor running the latest bios. Everything appears to work >> properly so I am unsure what the messages mean beyond the obvious. I >> did a little research and was wondering if this is related to the no >> bootmem patches. I have: > > Unless you need to use anything on SMBus (hardware sensors, essentially) you > don't have to worry about that one. It means that the kernel has detected > that the BIOS may potentially access the SMBus controller which may conflict > with usage of the controller from within the OS. I do use the lm78 sensor driver: lm78: Found an LM79 chip at 0x290 and the Xsensors seem to work, the voltages and fan speeds change. But you are correct the lm75 driver isn't loading so I am not getting my cpu temperature. In 2.6.30.9 I have: Driver `lm78' Detects correctly: * Bus `SMBus PIIX4 adapter at 0440' Busdriver `i2c-piix4', I2C address 0x2d ISA bus, address 0x290 Chip `National Semiconductor LM79' (confidence: 6) Driver `lm75' Detects correctly: * Bus `SMBus PIIX4 adapter at 0440' Busdriver `i2c-piix4', I2C address 0x4c Chip `National Semiconductor LM75' (confidence: 6) * Bus `SMBus PIIX4 adapter at 0440' Busdriver `i2c-piix4', I2C address 0x4d Chip `National Semiconductor LM75' (confidence: 6) In 2.6.34 I get: Driver `lm78' Detects correctly: * ISA bus, address 0x290 Chip `National Semiconductor LM79' (confidence: 6) So this is a regression. Thanks, Rich ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: resource piix4_smbus conflicts with ACPI region SMRG 2010-06-01 2:36 ` Richard Tillmore @ 2010-06-01 3:13 ` Robert Hancock 2010-06-03 23:50 ` Richard Tillmore 0 siblings, 1 reply; 6+ messages in thread From: Robert Hancock @ 2010-06-01 3:13 UTC (permalink / raw) To: Richard Tillmore; +Cc: linux-kernel On Mon, May 31, 2010 at 8:36 PM, Richard Tillmore <rtillmore@gmail.com> wrote: > On Mon, May 31, 2010 at 6:42 PM, Robert Hancock wrote: >> On 05/31/2010 04:12 PM, Richard wrote: >>> >>> I upgraded to 2.6.34-rc6 and noticed a few new messages in dmesg. I >>> then installed 2.6.34 and the messages remain. >>> >>> PCI: Ignoring host bridge windows from ACPI; if necessary, use >>> "pci=use_crs" and report a bug >>> ACPI: PCI Root Bridge [PCI0] (0000:00) >> >> This is just an informational message. >> >>> >>> ACPI: resource piix4_smbus [io 0x0440-0x0447] conflicts with ACPI >>> region SMRG [??? 0x00000440-0x0000044f flags 0x47] >>> ACPI: If an ACPI driver is available for this device, you should use >>> it instead of the native driver >>> >>> The system is a Tyan Tiger S1832 motherboard with a P3 850Mhz >>> processor running the latest bios. Everything appears to work >>> properly so I am unsure what the messages mean beyond the obvious. I >>> did a little research and was wondering if this is related to the no >>> bootmem patches. I have: >> >> Unless you need to use anything on SMBus (hardware sensors, essentially) you >> don't have to worry about that one. It means that the kernel has detected >> that the BIOS may potentially access the SMBus controller which may conflict >> with usage of the controller from within the OS. > > I do use the lm78 sensor driver: > lm78: Found an LM79 chip at 0x290 > and the Xsensors seem to work, the voltages and fan speeds change. > > But you are correct the lm75 driver isn't loading so I am not getting > my cpu temperature. > > In 2.6.30.9 I have: > Driver `lm78' > Detects correctly: > * Bus `SMBus PIIX4 adapter at 0440' > Busdriver `i2c-piix4', I2C address 0x2d > ISA bus, address 0x290 > Chip `National Semiconductor LM79' (confidence: 6) > > Driver `lm75' > Detects correctly: > * Bus `SMBus PIIX4 adapter at 0440' > Busdriver `i2c-piix4', I2C address 0x4c > Chip `National Semiconductor LM75' (confidence: 6) > * Bus `SMBus PIIX4 adapter at 0440' > Busdriver `i2c-piix4', I2C address 0x4d > Chip `National Semiconductor LM75' (confidence: 6) > > In 2.6.34 I get: > Driver `lm78' > Detects correctly: > * ISA bus, address 0x290 > Chip `National Semiconductor LM79' (confidence: 6) > > So this is a regression. You should be able to use acpi_enforce_resources=lax on the kernel command line to allow the driver to load. The problem is that the kernel can't tell if it's safe to allow a driver to access that hardware since it may conflict with BIOS access (in some cases this can cause serious problems like system overheating or spurious thermal shutdowns if the BIOS also accesses the device to perform thermal management) and so the default is to not allow it. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: resource piix4_smbus conflicts with ACPI region SMRG 2010-06-01 3:13 ` Robert Hancock @ 2010-06-03 23:50 ` Richard Tillmore 2010-06-04 0:05 ` Matthew Garrett 0 siblings, 1 reply; 6+ messages in thread From: Richard Tillmore @ 2010-06-03 23:50 UTC (permalink / raw) To: Robert Hancock; +Cc: linux-kernel On Mon, May 31, 2010 at 10:13 PM, Robert Hancock wrote: > On Mon, May 31, 2010 at 8:36 PM, Richard wrote: >> On Mon, May 31, 2010 at 6:42 PM, Robert Hancock wrote: >>> On 05/31/2010 04:12 PM, Richard wrote: >>>> >>>> I upgraded to 2.6.34-rc6 and noticed a few new messages in dmesg. I >>>> then installed 2.6.34 and the messages remain. <snip> >>>> ACPI: resource piix4_smbus [io 0x0440-0x0447] conflicts with ACPI >>>> region SMRG [??? 0x00000440-0x0000044f flags 0x47] >>>> ACPI: If an ACPI driver is available for this device, you should use >>>> it instead of the native driver >>>> >>>> The system is a Tyan Tiger S1832 motherboard with a P3 850Mhz >>>> processor running the latest bios. Everything appears to work >>>> properly so I am unsure what the messages mean beyond the obvious. I >>>> did a little research and was wondering if this is related to the no >>>> bootmem patches. I have: >>> >>> Unless you need to use anything on SMBus (hardware sensors, essentially) you >>> don't have to worry about that one. It means that the kernel has detected >>> that the BIOS may potentially access the SMBus controller which may conflict >>> with usage of the controller from within the OS. >> >> I do use the lm78 sensor driver: >> lm78: Found an LM79 chip at 0x290 >> and the Xsensors seem to work, the voltages and fan speeds change. >> >> But you are correct the lm75 driver isn't loading so I am not getting >> my cpu temperature. >> >> In 2.6.30.9 I have: >> Driver `lm78' >> Detects correctly: >> * Bus `SMBus PIIX4 adapter at 0440' >> Busdriver `i2c-piix4', I2C address 0x2d >> ISA bus, address 0x290 >> Chip `National Semiconductor LM79' (confidence: 6) >> >> Driver `lm75' >> Detects correctly: >> * Bus `SMBus PIIX4 adapter at 0440' >> Busdriver `i2c-piix4', I2C address 0x4c >> Chip `National Semiconductor LM75' (confidence: 6) >> * Bus `SMBus PIIX4 adapter at 0440' >> Busdriver `i2c-piix4', I2C address 0x4d >> Chip `National Semiconductor LM75' (confidence: 6) >> >> In 2.6.34 I get: >> Driver `lm78' >> Detects correctly: >> * ISA bus, address 0x290 >> Chip `National Semiconductor LM79' (confidence: 6) >> >> So this is a regression. > > You should be able to use acpi_enforce_resources=lax on the kernel > command line to allow the driver to load. The problem is that the > kernel can't tell if it's safe to allow a driver to access that > hardware since it may conflict with BIOS access (in some cases this > can cause serious problems like system overheating or spurious thermal > shutdowns if the BIOS also accesses the device to perform thermal > management) and so the default is to not allow it. I booted with acpi_enforce_resources=lax and I now can get my CPU temperature. So is my having to add acpi_enforce_resources=lax an effect of ACPI changes or bootmem changes? Thanks, Rich ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: resource piix4_smbus conflicts with ACPI region SMRG 2010-06-03 23:50 ` Richard Tillmore @ 2010-06-04 0:05 ` Matthew Garrett 0 siblings, 0 replies; 6+ messages in thread From: Matthew Garrett @ 2010-06-04 0:05 UTC (permalink / raw) To: Richard Tillmore; +Cc: Robert Hancock, linux-kernel On Thu, Jun 03, 2010 at 06:50:44PM -0500, Richard Tillmore wrote: > On Mon, May 31, 2010 at 10:13 PM, Robert Hancock wrote: > > You should be able to use acpi_enforce_resources=lax on the kernel > > command line to allow the driver to load. The problem is that the > > kernel can't tell if it's safe to allow a driver to access that > > hardware since it may conflict with BIOS access (in some cases this > > can cause serious problems like system overheating or spurious thermal > > shutdowns if the BIOS also accesses the device to perform thermal > > management) and so the default is to not allow it. > > I booted with acpi_enforce_resources=lax and I now can get my CPU > temperature. So is my having to add acpi_enforce_resources=lax an > effect of ACPI changes or bootmem changes? ACPI changes. Your firmware indicates that ACPI makes use of the smbus controller - since many smbus transactions involve writing an address and then a value, and since we can't enforce locking between the kernel and the firmware, it's not possible to prove that it's safe to allow the kernel to touch these resources. Passing the kernel parameter disables this check in cases where you know it's safe. -- Matthew Garrett | mjg59@srcf.ucam.org ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2010-06-04 0:05 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2010-05-31 22:12 resource piix4_smbus conflicts with ACPI region SMRG Richard Tillmore 2010-05-31 23:42 ` Robert Hancock 2010-06-01 2:36 ` Richard Tillmore 2010-06-01 3:13 ` Robert Hancock 2010-06-03 23:50 ` Richard Tillmore 2010-06-04 0:05 ` Matthew Garrett
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox