5336 2013-10-10 14:40:54 +0000 'init' command does not work as intended 2015-03-23 16:13:57 +0000 1 1 11 Runtime General Runtime General Runtime 1.5 x86 Multiple RESOLVED FIXED Medium normal 1.8 M4 1 corneliux.stoicescu anibal.limon anibal.limon dvhart Qi.Chen --- --- No (bug/feature does not impact docs) oldest_to_newest 37812 0 corneliux.stoicescu 2013-10-10 14:40:54 +0000 When in runlevel X and issuing command 'init Y', the system should cleanly migrate to runlevel Y. This behaviour does not happen in most cases using Yocto images. Some examples of bad behavior: 1) In any image(testes core-image-sato, core-image-lsb-sdk) issuing command 'init 1' will result in a technical hang 2) In core-image-lsb-sdk images, from the default runlevel 5, issuing the sequence of commands: 'init 3' 'init 5' 'init 3' 'init 5' will result in an oprofile-server:1054 error(could not bind to the server. Address already in use). 3) In core-image-sato-sdk images issuing 'init 3' command from the GUI terminal is completely ignored. NOTE: 'init 0' and 'init 6' commands correctlr shutdown and restart the system(during my tests) 43265 1 sgw 2014-05-12 17:49:30 +0000 Is this still an issue and if so, can you verify if it's just a real HW (which machines) and/or Qemu? 43596 2 corneliux.stoicescu 2014-05-27 07:15:34 +0000 We will test this on meta-intel HW targets today. Core BSPs will be tested in the next few days as well and QEMU targets on the first weekly test. I will get as much feedback and post the results here. 43758 3 corneliux.stoicescu 2014-06-04 09:40:56 +0000 Verified on meta-intel 1.6 release candidates and issues happen as described. 44063 4 sjolley.yp.pm 2014-06-18 17:24:03 +0000 Info Supplied, moved back out of NEEDINFO per RP. 44506 5 corneliux.stoicescu 2014-07-16 10:08:43 +0000 Also tested qemux86-64 with poky master:a5531a2b8983318b99c119a87b78a92cf84160bb and the issue is the same. 46748 6 anibal.limon 2014-11-04 20:51:39 +0000 Stoicescu, I'm doing some debugging with qemux86-64/core-image-sato using master branch, i have some concerns. 1) core-image-sato init 1, i reproduce this but it seems that not hang only didn't display shell in the monitor output, i used serial and vm it's running. $ runqemu qemux86-64 core-image-sato serial This is the issue? 2) core-image-lsb sdk init 3 - init 5, i can't reproduce the problem do you have another information? 3) core-image-sato-sdk init 3, gives me the same problem that 1). 46914 7 corneliux.stoicescu 2014-11-11 08:34:44 +0000 Lucian, can you please help investigate the current status of the issues presented in this bug? Try to reproduce steps 1, 2, 3 from the first post. 47599 8 georgex.l.musat 2014-12-17 11:48:44 +0000 Tried to reproduce this on 1.8 M1 (b813bdebb36501500e86fea5f7e15b4b15ea0902) Lenovo X220 laptop genericx86-64 and this is what happened: 1. Core-image-sato-sdk image hangs on init 1, 3 and 5. Works for init 0 and 6. 2. Core-image-lsb-sdk ignores init 3 and 5. Actually it tries the first time but fails with: "INIT: Switching to runlevel 3 cups: started scheduler umount: /mnt/.psplash: not mounted" and returns to console. After that init 3 and 5 are ignored. Init 1 hangs at "INIT: no more processes left in this runlevel" Init 0 and 6 works. 49661 9 anibal.limon 2015-03-23 16:13:57 +0000 Merge at, http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=3e9476e6929926a4645b32356dbcc5af040af2fd http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=94f5ce05e868b2d875880802ae8582b675537f64