3719 2013-01-14 23:29:40 +0000 fsl-image-gui image for imx6qsabreauto machine does not reboot 2015-10-21 15:44:47 +0000 1 1 7 Build System, Metadata & Runtime BSPs bsps-meta-fsl-arm 1.3 Other arm RESOLVED WORKSFORME Low normal Future 1 disabled.leonardo.sandoval angolini otavio rjohnweber sgw --- --- No (bug/feature does not impact docs) oldest_to_newest 28824 0 disabled.leonardo.sandoval 2013-01-14 23:29:40 +0000 when the reboot command is type on the console, the system hangs after showing some log and never reboots. This has only been tested for the fsl-image-gui on a imx6qsabreauto machine. 28825 1 disabled.leonardo.sandoval 2013-01-14 23:46:19 +0000 Log before the system stops rebooting root@imx6qsabreauto:~# reboot The system is going down for reboot NOW!to (ttymxc3) (Mon Jan 14 22:26:40 201 INIT: Switching to runlevel: 6 INIT: Sending processes the TERM signalroot@imx6qsabreauto:~# INIT: Sending processes the KILL signaStopping XServer Stopping Dropbear SSH server: stopped /usr/sbin/dropbear (pid 550) dropbear. * Stopping Avahi mDNS/DNS-SD Daemon: avahi-daemon ** (oprofile-server:614): WARNING **: Avahi error: Daemon connection failed ...done. Stopping advanced power management daemon: stopped /usr/sbin/apmd (pid 553) apmd. Stopping system message bus: stopping statd: done stopping mountd: done stopping nfsd: done Stopping OProfileUI server Stopping syslogd/klogd: stopped syslogd (pid 585) stopped klogd (pid 587) done Stopping tcf-agent: OK Stopping Connection Manager Stopping Telephony daemon ALSA: Storing mixer settings... 29655 2 disabled.leonardo.sandoval 2013-02-07 23:38:14 +0000 This bug is not present on core-minimal-image image. I will test it the image it was reported (fsl-image-gui) Leo 29693 3 disabled.leonardo.sandoval 2013-02-08 21:08:21 +0000 (In reply to comment #2) > This bug is not present on core-minimal-image image. I will test it the > image it was reported (fsl-image-gui) > > Leo Bug is present on core-image-base, so this is the image to work on this issue. 29713 4 otavio 2013-02-11 16:22:07 +0000 The issue seems related to the audio driver. 29937 5 disabled.leonardo.sandoval 2013-02-18 19:38:35 +0000 I had to stop working on this issue. As mentioned in a previous comments, issue is reproducibled with the core-image-base image. The problem happens when the /etc/init.d/alsa-state script runs the command: /usr/sbin/alsactl -f /var/lib/alsa/asound.state store which tries to store **all** sound cards configurations. The problem comes when storing the card number 1, which is imxsddif: # cat /proc/asound/cards 0 [cs42888audio ]: cs42888-audio - cs42888-audio cs42888-audio 1 [imxspdif ]: imx-spdif - imx-spdif imx-spdif so, the halting task is in fact /usr/sbin/alsactl -f /var/lib/alsa/asound.state store 1 My impression is that the alsactl store is halting on a imxspdif's function call (ioctl ?) but right now I have to time to further debugging it. Also, alsacrl restore and alsactr init works as expected, no halt at all. Leo 31605 6 rjohnweber 2013-04-05 14:01:05 +0000 I'm seeing this same exact issue on Wandboard Dual. The sound cards are cat /proc/asound/cards 0 [sgtl5000audio ]: sgtl5000-audio - sgtl5000-audio sgtl5000-audio 1 [imxspdif ]: imx-spdif - imx-spdif imx-spdif 2 [imxhdmisoc ]: imx-hdmi-soc - imx-hdmi-soc imx-hdmi-soc The halting command is the one that stores state for card 1 (imx-spdif) /usr/sbin/alsactl -f /var/lib/alsa/asound.state store 1 31614 7 rjohnweber 2013-04-05 14:53:07 +0000 To elaborate on that last comment with build information: Built using Yocto snapshot from 2013-04-03. The image is fsl-image-test. I've seen this problem for a while, with both the kernels from 1.1.0 and the 'official' wandboard kernel for which support was recently included in meta-fsl-arm-extra. Looking through the boards, there are only a few with SPDIF ports: mx6sl-evk sabereauto wandboard arm2 I only have Wandboard, but it would be interesting to know if this problem exists on the arm2 and sl-evk. John 55567 8 angolini 2015-10-21 15:44:47 +0000 I just tested it using imx6qsabreauto and kernel 3.14.28 (from fido) and I was not able to reproduce the error any more. I think it can be closed and, if needed, reopened in future in case of positive reproduction (with description on environment needed to reproduce)