Re: powerd rc script failing to start after fresh build

[Shawn Debnath]

On 04/26, Shawn Debnath wrote:
> Synced to r298678 this evening and after a reboot, powerd fails to start
> with the following error in messages:
> 
>   Apr 26 17:54:12 titan root: /etc/rc: WARNING: failed to start powerd
> 
> Manually trying to start it via service throws:
> 
>   $ sudo service powerd start
>   Starting powerd.
>   powerd: no cpufreq(4) support -- aborting: No such file or directory
>   /etc/rc.d/powerd: WARNING: failed to start powerd
> 
> dmesg shows:
> 
>   CPU: Intel(R) Xeon(R) CPU   X5670  @ 2.93GHz (2933.50-MHz K8-class
>   CPU)
> Origin="GenuineIntel"  Id=0x206c2  Family=0x6  Model=0x2c  Stepping=2
> 
> Features=0xbfebfbff
> 
> Features2=0x29ee3ff
> AMD Features=0x2c100800
> AMD Features2=0x1
> VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
> TSC: P-state invariant, performance statistics
>   real memory  = 68719476736 (65536 MB)
>   avail memory = 66696982528 (63607 MB)
>   Event timer "LAPIC" quality 600
>   ACPI APIC Table: 
>   FreeBSD/SMP: Multiprocessor System Detected: 24 CPUs
>   FreeBSD/SMP: 2 package(s) x 6 core(s) x 2 hardware threads
>   random: unblocking device.
>   ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aControlBlock: 32,
>   using default 16 (20150818/tbfadt-730)
>   ACPI BIOS Warning (bug): Invalid length for FADT/Pm2ControlBlock: 32,
>   using default 8 (20150818/tbfadt-730)
> 
> This wasn't the case till the update today, including the ACPI BIOS
> warning.


Forgot to add that I double checked, and cpufreq was enabled in the GENERIC 
kernel:

$ uname -a 
FreeBSD titan 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r298678: Tue Apr 26 17:29:01 
PDT 2016 sd@titan:/usr/home/sd/obj/usr/home/sd/src/sys/GENERIC  amd64
$ cat sys/amd64/conf/GENERIC | grep cpufreq
device  cpufreq


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: powerd rc script failing to start after fresh build

[Shawn Debnath]

On 04/26, Shawn Debnath wrote:

> > This wasn't the case till the update today, including the ACPI BIOS
> > warning.
> 
> 
> Forgot to add that I double checked, and cpufreq was enabled in the GENERIC 
> kernel:
> 
> $ uname -a 
> FreeBSD titan 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r298678: Tue Apr 26 
> 17:29:01 PDT 2016 sd@titan:/usr/home/sd/obj/usr/home/sd/src/sys/GENERIC  amd64
> $ cat sys/amd64/conf/GENERIC | grep cpufreq
> devicecpufreq
> 


Apologies, late night typing and mixed up systems that I rebuilt the world
+ kernel for. 

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

powerd rc script failing to start after fresh build

[Shawn Debnath]

Synced to r298678 this evening and after a reboot, powerd fails to start
with the following error in messages:

  Apr 26 17:54:12 titan root: /etc/rc: WARNING: failed to start powerd

Manually trying to start it via service throws:

  $ sudo service powerd start
  Starting powerd.
  powerd: no cpufreq(4) support -- aborting: No such file or directory
  /etc/rc.d/powerd: WARNING: failed to start powerd

dmesg shows:

  CPU: Intel(R) Xeon(R) CPU   X5670  @ 2.93GHz (2933.50-MHz K8-class
  CPU)
Origin="GenuineIntel"  Id=0x206c2  Family=0x6  Model=0x2c  Stepping=2

Features=0xbfebfbff

Features2=0x29ee3ff
AMD Features=0x2c100800
AMD Features2=0x1
VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
TSC: P-state invariant, performance statistics
  real memory  = 68719476736 (65536 MB)
  avail memory = 66696982528 (63607 MB)
  Event timer "LAPIC" quality 600
  ACPI APIC Table: 
  FreeBSD/SMP: Multiprocessor System Detected: 24 CPUs
  FreeBSD/SMP: 2 package(s) x 6 core(s) x 2 hardware threads
  random: unblocking device.
  ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aControlBlock: 32,
  using default 16 (20150818/tbfadt-730)
  ACPI BIOS Warning (bug): Invalid length for FADT/Pm2ControlBlock: 32,
  using default 8 (20150818/tbfadt-730)

This wasn't the case till the update today, including the ACPI BIOS
warning.

Any help appreciated or let me know what else I can provide to help find
the root cause.

Thanks,
Shawn
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"