<div dir="ltr"><div><div>Hi Yi,<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 26, 2014 at 11:06 AM, Yi Qingliang <span dir="ltr"><<a href="mailto:niqingliang2003@gmail.com" target="_blank">niqingliang2003@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
after update to the latest git version of poky, my image can't start<br>
the serial console, i.e. I can't login, I'm using systemd as the init<br>
manager. any idea?<br>
<br>
log:<br>
<br>
Freeing init memory: 132K<br>
systemd[1]: systemd 211 running in system mode. (-PAM +LIBWRAP -<br>
AUDIT -SELINUX +IMA +SYSVINIT -LIBCRYPTSETUP -GCRYPT +ACL +XZ -<br>
SECCOMP -APPARMOR)<br>
systemd[1]: Detected architecture 'arm'.<br>
<br>
Welcome to Linux!<br>
<br>
systemd[1]: Failed to insert module 'autofs4'<br>
systemd[1]: Failed to insert module 'ipv6'<br>
systemd[1]: Set hostname to <kl360>.<br>
systemd[1]: Initializing machine ID from random generator.<br>
systemd[1]: Starting Forward Password Requests to Wall Directory<br>
Watch.<br>
systemd[1]: Started Forward Password Requests to Wall Directory<br>
Watch.<br>
systemd[1]: Expecting device dev-ttySAC0.device...<br>
Expecting device dev-ttySAC0.device...<br>
systemd[1]: Starting Remote File Systems.<br>
[ OK ] Reached target Remote File Systems.<br>
systemd[1]: Reached target Remote File Systems.<br>
systemd[1]: Starting Dispatch Password Requests to Console Directory<br>
Watch.<br>
systemd[1]: Started Dispatch Password Requests to Console Directory<br>
Watch.<br>
systemd[1]: Starting Paths.<br>
[ OK ] Reached target Paths.<br>
systemd[1]: Reached target Paths.<br>
systemd[1]: Set up automount Arbitrary Executable File Formats File<br>
System Automount Point.<br>
systemd[1]: Starting Swap.<br>
[ OK ] Reached target Swap.<br>
systemd[1]: Reached target Swap.<br>
systemd[1]: Starting Root Slice.<br>
[ OK ] Created slice Root Slice.<br>
systemd[1]: Created slice Root Slice.<br>
systemd[1]: Starting Journal Socket.<br>
[ OK ] Listening on Journal Socket.<br>
systemd[1]: Listening on Journal Socket.<br>
systemd[1]: Starting udev Control Socket.<br>
[ OK ] Listening on udev Control Socket.<br>
systemd[1]: Listening on udev Control Socket.<br>
systemd[1]: Starting Delayed Shutdown Socket.<br>
[ OK ] Listening on Delayed Shutdown Socket.<br>
systemd[1]: Listening on Delayed Shutdown Socket.<br>
systemd[1]: Starting /dev/initctl Compatibility Named Pipe.<br>
[ OK ] Listening on /dev/initctl Compatibility Named Pipe.<br>
systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.<br>
systemd[1]: Starting udev Kernel Socket.<br>
[ OK ] Listening on udev Kernel Socket.<br>
systemd[1]: Listening on udev Kernel Socket.<br>
systemd[1]: Starting User and Session Slice.<br>
[ OK ] Created slice User and Session Slice.<br>
systemd[1]: Created slice User and Session Slice.<br>
systemd[1]: Starting System Slice.<br>
[ OK ] Created slice System Slice.<br>
systemd[1]: Created slice System Slice.<br>
systemd[1]: Started Set Up Additional Binary Formats.<br>
systemd[1]: Starting Journal Service...<br>
Starting Journal Service...<br>
[ OK ] Started Journal Service.<br>
systemd[1]: Started Journal Service.<br>
Starting Apply Kernel Variables...<br>
Mounting POSIX Message Queue File System...<br>
Starting Create list of required static device nodes...rrent<br>
kernel...<br>
Starting udev Coldplug all Devices...<br>
Mounting Temporary Directory...<br>
Starting Remount Root and Kernel File Systems...<br>
<span class=""><font color="#888888"><br></font></span></blockquote><div><br>I had a very similar problem on my Wandboard, using latest systemd 211.<br>The solution for me was to enable CONFIG_FHANDLE in the kernel configuration.<br>
</div><div>Maybe that could work for you aswell.<br></div><div>Which makes me wonder if there is any sort infrastructre for handling kernel config. deps.<br></div><div>/Jacob</div></div></div></div>