Bug 11105

Summary: ALSA error in boot log
Product: [Yocto Project Subprojects] IoT Reference OS Kit Reporter: Simo Kuusela <simo.kuusela>
Component: intel-iot-refkit-multimediaAssignee: Jaska Uimonen <jaska.uimonen>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: Low CC: matti-pekka.sivosuo, mikko.ylinen, olev.kartau
Version: unspecified   
Target Milestone: Future   
Hardware: x86   
OS: x86   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know

Description Simo Kuusela 2017-02-24 13:06:06 UTC 
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.
Comment 1 Olev Kartau 2017-05-17 06:34:06 UTC 
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.
Comment 2 Mikko Ylinen 2017-05-18 05:01:04 UTC 
(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.