2015-05-22 3:36 GMT+08:00 Lennart Poettering :
>
> Should be fixed in git. Please verify!
Confirmed, thanks!
--
Regards,
- cee1
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-
On Wed, 20.05.15 11:16, cee1 (fykc...@gmail.com) wrote:
> 2015-05-20 1:27 GMT+08:00 Lennart Poettering :
> > Hmm, can you provide a backtrace of the call chain when this happens,
> > please?
>
> The call chain is:
> 0xb6df1acc : 0xe1a07000
> 0xb6e9f744 : 0xe3a0
> 0xb6df4bb0 : 0xe59a0004
> 0xb
2015-05-20 1:27 GMT+08:00 Lennart Poettering :
> Hmm, can you provide a backtrace of the call chain when this happens,
> please?
The call chain is:
0xb6df1acc : 0xe1a07000
0xb6e9f744 : 0xe3a0
0xb6df4bb0 : 0xe59a0004
0xb6ded8e8 : 0xe2509000
0xb6de6080 : 0xe371
Related logs:
"""
Job mnt-dat
On Tue, 19.05.15 14:45, cee1 (fykc...@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
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(), w
