[OE-core] serial console problem

Jacob Kroon jacob.kroon at gmail.com
Wed Mar 26 10:16:44 UTC 2014


Hi Yi,

On Wed, Mar 26, 2014 at 11:06 AM, Yi Qingliang <niqingliang2003 at gmail.com>wrote:

> Hi,
>         after update to the latest git version of poky, my image can't
> start
> the serial console,  i.e. I can't login, I'm using systemd as the init
> manager. any idea?
>
> log:
>
> Freeing init memory: 132K
> systemd[1]: systemd 211 running in system mode. (-PAM +LIBWRAP -
> AUDIT -SELINUX +IMA +SYSVINIT -LIBCRYPTSETUP -GCRYPT +ACL +XZ -
> SECCOMP -APPARMOR)
> systemd[1]: Detected architecture 'arm'.
>
> Welcome to Linux!
>
> systemd[1]: Failed to insert module 'autofs4'
> systemd[1]: Failed to insert module 'ipv6'
> systemd[1]: Set hostname to <kl360>.
> systemd[1]: Initializing machine ID from random generator.
> systemd[1]: Starting Forward Password Requests to Wall Directory
> Watch.
> systemd[1]: Started Forward Password Requests to Wall Directory
> Watch.
> systemd[1]: Expecting device dev-ttySAC0.device...
>          Expecting device dev-ttySAC0.device...
> systemd[1]: Starting Remote File Systems.
> [  OK  ] Reached target Remote File Systems.
> systemd[1]: Reached target Remote File Systems.
> systemd[1]: Starting Dispatch Password Requests to Console Directory
> Watch.
> systemd[1]: Started Dispatch Password Requests to Console Directory
> Watch.
> systemd[1]: Starting Paths.
> [  OK  ] Reached target Paths.
> systemd[1]: Reached target Paths.
> systemd[1]: Set up automount Arbitrary Executable File Formats File
> System Automount Point.
> systemd[1]: Starting Swap.
> [  OK  ] Reached target Swap.
> systemd[1]: Reached target Swap.
> systemd[1]: Starting Root Slice.
> [  OK  ] Created slice Root Slice.
> systemd[1]: Created slice Root Slice.
> systemd[1]: Starting Journal Socket.
> [  OK  ] Listening on Journal Socket.
> systemd[1]: Listening on Journal Socket.
> systemd[1]: Starting udev Control Socket.
> [  OK  ] Listening on udev Control Socket.
> systemd[1]: Listening on udev Control Socket.
> systemd[1]: Starting Delayed Shutdown Socket.
> [  OK  ] Listening on Delayed Shutdown Socket.
> systemd[1]: Listening on Delayed Shutdown Socket.
> systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
> [  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
> systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
> systemd[1]: Starting udev Kernel Socket.
> [  OK  ] Listening on udev Kernel Socket.
> systemd[1]: Listening on udev Kernel Socket.
> systemd[1]: Starting User and Session Slice.
> [  OK  ] Created slice User and Session Slice.
> systemd[1]: Created slice User and Session Slice.
> systemd[1]: Starting System Slice.
> [  OK  ] Created slice System Slice.
> systemd[1]: Created slice System Slice.
> systemd[1]: Started Set Up Additional Binary Formats.
> systemd[1]: Starting Journal Service...
>          Starting Journal Service...
> [  OK  ] Started Journal Service.
> systemd[1]: Started Journal Service.
>          Starting Apply Kernel Variables...
>          Mounting POSIX Message Queue File System...
>          Starting Create list of required static device nodes...rrent
> kernel...
>          Starting udev Coldplug all Devices...
>          Mounting Temporary Directory...
>          Starting Remount Root and Kernel File Systems...
>
>
I had a very similar problem on my Wandboard, using latest systemd 211.
The solution for me was to enable CONFIG_FHANDLE in the kernel
configuration.
Maybe that could work for you aswell.
Which makes me wonder if there is any sort infrastructre for handling
kernel config. deps.
/Jacob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20140326/7e63aa60/attachment-0002.html>


More information about the Openembedded-core mailing list