freebsd stable - Jun 2014 - powerd stopped working after update from 8.4 to 9.2

Hi,

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?

regards,
Hilko
PS: Maybe acpi related so I cced acpi@

On Sunday, June 22, 2014 9:27:08 pm Hilko Meyer wrote:
> Hi,
> 
> 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?

-- 
John Baldwin