11105 2017-02-24 13:06:06 +0000 ALSA error in boot log 2017-05-18 05:01:04 +0000 1 1 6 Yocto Project Subprojects IoT Reference OS Kit intel-iot-refkit-multimedia unspecified x86 x86 RESOLVED WORKSFORME Low normal Future 1 simo.kuusela jaska.uimonen matti-pekka.sivosuo mikko.ylinen olev.kartau --- --- Don't know oldest_to_newest 70928 0 simo.kuusela 2017-02-24 13:06:06 +0000 Error: "/usr/sbin/alsactl: state_lock:125: file /var/lib/alsa/asound.state lock error: File exists" happens randomly when booting Refkit image. It seems to happen randomly under 2% of the time. It doesn't stop booting and doesn't seem to affect any of the tests used to validate Refkit. Related lines from one example case: Feb 16 09:06:09 intel-corei7-64 systemd[1]: Starting Save/Restore Sound Card State... Feb 16 09:06:09 intel-corei7-64 alsactl[584]: /usr/sbin/alsactl: state_lock:125: file /var/lib/alsa/asound.state lock error: File exists Feb 16 09:06:09 intel-corei7-64 alsactl[584]: /usr/sbin/alsactl: load_state:1683: Cannot open /var/lib/alsa/asound.state for reading: File exists Feb 16 09:06:09 intel-corei7-64 alsactl[584]: Found hardware: "HDA-Intel" "Intel Broxton HDMI" "HDA:8086280a,80860101,00100000" "0x8086" "0x7270" Feb 16 09:06:09 intel-corei7-64 alsactl[584]: Hardware is initialized using a generic method Feb 16 09:06:09 intel-corei7-64 systemd-udevd[554]: Process '/usr/sbin/alsactl restore 0' failed with exit code 99. Feb 16 09:06:09 intel-corei7-64 systemd[1]: Started Save/Restore Sound Card State. Feb 16 09:06:09 intel-corei7-64 systemd[1]: Reached target Sound Card. 73290 1 olev.kartau 2017-05-17 06:34:06 +0000 this error not mentioned in 500 most recent PR job logs (last 500 builds cover time starting Apr-3). Has cause been fixed by some other change? If not occurring, we can remove this entry from the whitelist. 73315 2 mikko.ylinen 2017-05-18 05:01:04 +0000 (In reply to comment #1) > this error not mentioned in 500 most recent PR job logs > (last 500 builds cover time starting Apr-3). > Closing based on this data.