[Qa-jenkins-dev] failed service on odxu4b

[Vagrant Cascadian]

On 2018-04-07, Mattia Rizzolo wrote:
> today I added a check on the health_check jobs for failed systemd
> services.

Good idea.


> odxu4b has a failed cpufrequtils.service:
> ● cpufrequtils.service - LSB: set CPUFreq kernel parameters
>    Loaded: loaded (/etc/init.d/cpufrequtils; generated; vendor preset: enabled)
>    Active: failed (Result: timeout) since Sat 2018-04-07 18:57:34 UTC; 3min 4s ago
>      Docs: man:systemd-sysv-generator(8)
>   Process: 13774 ExecStart=/etc/init.d/cpufrequtils start (code=killed, signal=TERM)
>     Tasks: 2 (limit: 4915)
>    CGroup: /system.slice/cpufrequtils.service
>            ├─  646 grep -q \<ondemand\> /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
>            └─13780 grep -q \<ondemand\> /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
>
> Apr 07 18:52:34 odxu4b systemd[1]: Starting LSB: set CPUFreq kernel parameters...
> Apr 07 18:57:34 odxu4b systemd[1]: cpufrequtils.service: Start operation timed out. Terminating.
> Apr 07 18:57:34 odxu4b systemd[1]: Failed to start LSB: set CPUFreq kernel parameters.
> Apr 07 18:57:34 odxu4b systemd[1]: cpufrequtils.service: Unit entered failed state.
> Apr 07 18:57:34 odxu4b systemd[1]: cpufrequtils.service: Failed with result 'timeout'.
>
>
> Trying to restart it just timeouts like that.  Could you please have a
> look?

There appears to be a linux kernel bug with 4.15 causing issues with
cpufreq on Odroid-XU4 boards:

  https://bugs.debian.org/895490


It doesn't appear to happen on 4.14.x, so I downgraded odxu4b to the
4.14 kernel currently in stretch-backports. Could also downgrade back to
4.9 from stretch.


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/qa-jenkins-dev/attachments/20180411/3992a78f/attachment.sig>