[systemd-devel] Problem when m->finish_timestamp is set before running manager_loop

Lennart Poettering lennart at poettering.net
Tue May 19 10:27:32 PDT 2015

On Tue, 19.05.15 14:45, cee1 (fykcee1 at gmail.com) wrote:

> Hi all,
> I found a "Startup finished in 155ms (userspace) = 155ms"(
>     which is of course incorrect) log on the board at hand, which is
> caused by something likes:
> "Job cache.mount/stop finished, result=canceled"
> Following the code, I find m->finish_timestamp is set in
> manager_check_finished(), which is in turn invoked in
> job_finish_and_invalidate() -- All these happens before the
> manager_loop running.

Hmm, can you provide a backtrace of the call chain when this happens,

I have now commited a patch to git, that might fix the issue, but I am
not entirely sure, given the little information I have:


Would be cool if you could check if this patch already fixes the issue
for you.



Lennart Poettering, Red Hat

More information about the systemd-devel mailing list