On Tue, 23 Aug 2011 18:11:40 +0200 Lennart Poettering <lenn...@poettering.net> wrote:
> On Sat, 20.08.11 15:21, Mike Kazantsev (mk.frag...@gmail.com) wrote: > > > On Thu, 18 Aug 2011 16:20:20 +0200 > > Lennart Poettering <lenn...@poettering.net> wrote: > > > > > On Tue, 09.08.11 07:02, Mike Kazantsev (mk.frag...@gmail.com) wrote: > > > > > > > Good day, > > > > > > > > Updating to systemd-33 (with "include missing.h" patch) seem to give me > > > > the following errors on boot: > > > > > > > > [ 27.024525] systemd[1]: Cannot add dependency job for unit > > > > fossil_echo.service, ignoring: Unit fossil_echo.service failed to load: > > > > Cannot allocate memory. See system logs and 'systemctl status > > > > fossil_echo.service' for details. > > ... > > > > > > Any chance you can bisect this? > > > > > > > Reexec reacts on these units right before "Deserializing state..." msg, > > with the same messages. > > I'll check whether they go away on reexec to 32 and reappear in 33, and > > if that's the case, will have results shortly. > > Can you reproduce this issue when you run "systemd --test --system" as > normal user after boot? > Yes, seem 100% reproducable that way. Same units, same errors. Looks like it can be (relatively) easily debugged with stuff like gdb now, I'll see if I can come up with conditional breakpoint for failed mallocs. Haven't really used gdb for anything but crash backtraces though, so any suggestions are welcome. -- Mike Kazantsev // fraggod.net
signature.asc
Description: PGP signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
