[systemd-devel] systemd hang on booting after mount

[Gustavo Sverzut Barbieri]

On Wed, Jan 19, 2011 at 1:21 PM, Lennart Poettering
<lennart at poettering.net> wrote:
> On Wed, 19.01.11 20:20, Chanwoo Choi (cwchoi00 at gmail.com) wrote:
>
>>
>> Kay Sievers wrote:
>> > On Tue, Jan 18, 2011 at 10:48, Lennart Poettering
>> > <lennart at poettering.net> wrote:
>> >
>> >> One other guess is that your kernel is too old, you need the
>> >> /sys/fs/cgroup mount point which is only available in recent kernels...
>> >
>> > That should be in 2.6.36, which is mentioned earlier in the thread. To
>> > check, it's this commit:
>> >   http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=676db4af043014e852f67ba0349dae0071bd11f3
>> >
>> > Kay
>> >
>>
>> I solved this error. The cause of error is that my system don't open directory
>> with flag(O_NOCTTY, O_NONBLOCK, O_DIRECTORY) in manager_setup_cgroup(). (in src/cgroup.c)
>> I will find the reason of it on my system.
>
> Hmm, this is very weird. What's the error code returned by this?
>
>> Then, I faced another error which prints following debug message :
>>
>> Starting Apply System Clock UTC Offset...
>> [    5.128666] systemd[1]: About to execute: /sbin/hwclock --systz
>> [    5.158289] systemd[1]: Forked /sbin/hwclock as 1370
>> [    5.162304] systemd[1]: hwclock-load.service changed dead -> start
>> [    5.168205] systemd[1]: Running GC...
>> [    5.172719] systemd[1]: event type=116
>> [    5.175364] systemd[1]: Code should not be reached 'Unknown epoll event type.' at src/manager.c:2279, function proce
>> ss_event(). Aborting.
>> [    5.219936] systemd[1]: Caught <ABRT>, dumped core as pid 1373.
>
> Hmm this is really weird, indication of some memory corruption. 116 is
> not a valid event type here. Really weird.
>
>> Why happen this aborting error?
>
> I have no idea at all tbh. Something is really weird on your machine.
>
>> [    3.662137] systemd[1]: /etc/mtab is not a symlink or not pointing to /proc/self/mounts. This is not supported anymo
>> re. Please make sure to replace this file by a symlink to avoid
>> incorrect or misleading mount(8) output.
>
> This has nothing to do with the problem you are encountering but you
> should make /etc/mtab a symlink to /proc/self/mounts.
>
>> [    4.886990] tmpfs: Bad value 'lock' for mount option 'gid'
>
> You should create a group called "lock". But this too doesn't
> have anything to do with your problem.
>
> To be frank, I am really puzzled be the problems you are encountering,
> no clue. The open() issue above is really suspicious that something
> bigger is wrong with your system.

Likely you're doing it for a company. If so and you need some
consulting or even to outsource systemd-related development, let me
know.

-- 
Gustavo Sverzut Barbieri
http://profusion.mobi embedded systems
--------------------------------------
MSN: barbieri at gmail.com
Skype: gsbarbieri
Mobile: +55 (19) 9225-2202