powerd stopped working after update from 8.4 to 9.2
John Baldwin
jhb at freebsd.org
Tue Jun 24 20:24:44 UTC 2014
On Tuesday, June 24, 2014 1:36:41 pm Hilko Meyer wrote:
> On Tue, 24 Jun 2014 10:26:52 -0400, you wrote:
> >On Monday, June 23, 2014 7:12:23 pm Hilko Meyer wrote:
> >> John Baldwin wrote:
> >> >On Sunday, June 22, 2014 9:27:08 pm Hilko Meyer wrote:
> >> >>
> >> >> powerd doesn't work anymore after the update from 8.4 to 9.2. The system
> >> >> has an old (more than 10 years) mainboard with Via KT133 chipset.
> >> >>
> >> >> I made a verbose boot with both, 8.4 and 9.2:
> >> >> 8.4: http://pastebin.com/iiZXRXgK
> >> >> 9.2: http://pastebin.com/sHcd3MHv
> >> >> The relevant part of the diff seem to be these parts:
> >> >>
> >> >> viapropm0: SMBus I/O base at 0x5000
> >> >> viapropm0: SMBus I/O base at 0x5000
> >> >> viapropm0: <VIA VT82C686A Power Management Unit> port 0x5000-0x500f at
> >> >> device 7.4 on pci0
> >> >> -viapropm0: SMBus revision code 0x40
> >> >> -smbus0: <System Management Bus> on viapropm0
> >> >> -smb0: <SMBus generic I/O> on smbus0
> >> >> +viapropm0: could not allocate bus space
> >> >> +device_attach: viapropm0 attach returned 6
> >> >> [
]
> >> >> acpi_throttle0: <ACPI CPU Throttling> on cpu0
> >> >> -acpi_throttle0: P_CNT from P_BLK 0x4010
> >> >> +acpi_throttle0: failed to attach P_CNT
> >> >> +device_attach: acpi_throttle0 attach returned 6
> >> >>
> >> >> Any ideas what I can do?
> >> >
> >> >acpi_timer0 also failed to probe due to a resource issue. Can you get the
> >> >output of 'devinfo -rv' and 'devinfo -u' from the both kernels?
> >>
> >> Yes, no problem.
> >> devinfo -rv:
> >> 8.4: http://pastebin.com/6xm1tBrU
> >> 9.2: http://pastebin.com/whXk32Ab
> >>
> >> devinfo -u:
> >> 8.4: http://pastebin.com/47U7HZb3
> >> 9.2: http://pastebin.com/U85HTw0C
> >>
> >> thanks for your help,
> >> Hilko
> >
> >Can you provide your acpidump? This box seems confusing.
>
> Well, its quite old. An Epox 8kta3 from around 2002. I was not sure which output
> you need so I attached acpidump -d and acpidump -dt.
Ok, try this:
Index: sys/dev/acpica/acpi.c
===================================================================
--- acpi.c (revision 267784)
+++ acpi.c (working copy)
@@ -1196,15 +1196,24 @@ acpi_set_resource(device_t dev, device_t child, in
return (0);
/*
- * Ignore memory resources for PCI root bridges. Some BIOSes
+ * Ignore most resources for PCI root bridges. Some BIOSes
* incorrectly enumerate the memory ranges they decode as plain
- * memory resources instead of as a ResourceProducer range.
+ * memory resources instead of as ResourceProducer ranges. Other
+ * BIOSes incorrectly list system resource entries for I/O ranges
+ * under the PCI bridge. Do allow the one known-correct case on
+ * x86 of a PCI bridge claiming the I/O ports used for PCI config
+ * access.
*/
- if (type == SYS_RES_MEMORY) {
+ if (type == SYS_RES_MEMORY || type == SYS_RES_IOPORT) {
if (ACPI_SUCCESS(AcpiGetObjectInfo(ad->ad_handle, &devinfo))) {
if ((devinfo->Flags & ACPI_PCI_ROOT_BRIDGE) != 0) {
- AcpiOsFree(devinfo);
- return (0);
+#if defined(__i386__) || defined(__amd64__)
+ if (!(type == SYS_RES_IOPORT && start == CONF1_ADDR_PORT))
+#endif
+ {
+ AcpiOsFree(devinfo);
+ return (0);
+ }
}
AcpiOsFree(devinfo);
}
--
John Baldwin
More information about the freebsd-acpi
mailing list